Sup foxies. I present to you NoPipeline – a thing which makes you forget Pipeline Tool ever existed. It’s a free addon to Pipeline Tool, which automatically updates .mgcb config. Now all you have to do to add a new resource – is to just place it into a resource folder. No more hassle, no more UI bugs. It integrates into build process, so you don’t have to manually launch anything at all.
It’s also fully compatible with default Pipeline Tool. You can add or remove NoPipeline at any stage of development.
Is it possible to use Nopipeline in a shared project? When creating a Monogame Shared Library Project it has a Content.mgcb file that gets built when building the main project.
I tried putting a npl file in the shared project and it didn’t seem to do anything.
In theory, it should have the same mechanisms as mgcb, check the project files themselves and see what’s the differences are. In practice, I highly recommend just using several mgcb and npl configs in each platform-specific project. I’ve done this in Monofoxe:
With Nopipeline this approach becomes actually feasible, less painless and requires a lot less magic.
The immediate difference I’m noticing is that I’m using shared projects (.shproj files). I don’t see any of those in your repo.
Should every project with .npl files reference Nopipeline? I don’t know all the details about how shared projects work, but as far as I can tell they don’t have references of their own, but are treated as having the same references as the project that they’re referenced by.
