Craigory Coppola

Why should these not be part of the module boundaries checks? If these are adding one or the other references to the project, than they _should_ be part of the...

Ah, that makes more sense! I'll relabel it.

First, some things that we **_are_** planning to do in nx-dotnet: - run-tool executor - msbuild task executor The run-tool executor would allow you to configure Nx's targetDependencies to get...

> Wouldn't adding prebuild and postbuild tasks just shift the problem onto MSBuild instead of Nx? Yeah, it kind of would. This is ideal though for **_most_** pre/post build tasks...

@EelcoLos looking at the paths in the error message, it appears that your project doesn't send build outputs to `{workspaceRoot}/dist/...`. Is this correct? Can you paste the `project.json` and `.csproj`...

Thats interesting, looking at it now you may need to add "{projectRoot}/obj" to the build tasks outputs array. Can you try that and see if it fixes it? If so,...

The dll should already be present, does your nx.json have targetDefaults / dependsOn setup for build? The reason we pass `noDependencies` is to let Nx orchestrate the build of dependencies...

SCSS imports are unfortunately not grabbed by NRWL's dependency graph, even the ones in the styles array. That would be a good issue for upstream, but I am sure they...

If acceptable I might put some time into working on this. I'm not sure how much would need to be changed, and it will be a while before I have...

One option if there are major breaking changes (I've not done a lot of investigation yet), might be to include both .dlls and let the script authors decide which version...