onovotny;10026 wrote:I really don't like the idea of putting tool specific information in my project file like that. It would be much cleaner if NCrunch could read the TFM list and then use a /p:TargetFrameworks=foo parameter as it builds and can filter out only the TFM's it supports (net and netcoreapp). Then projects don't have to adapt to a tool.
As the situation stands, support for this feature has been around for just 5 days, so this is still a very immature feature. You may need to make some compromises here for the time being.
NCrunch actually does read the TFM list, and injects the individual target frameworks into the build in a similar manner to what you've described. This is how it is able to build the project targets independently. The problem is that there is currently no way to specify which target frameworks should be built by NCrunch vs the default. It isn't safe for NCrunch to assume which TFMs it supports and which it doesn't, as we need to factor in forward compatibility for new frameworks that MS release. The ideal solution to this would be to have NCrunch's configuration system factor in the TFM when it generates the configuration file for each project. In this way, we could have a separate config file for each TFM for each project, allowing you to turn on the 'Ignore this component completely' setting on frameworks that you want NCrunch to leave alone.
onovotny;10026 wrote:
For AppDomains, I tried the items on that page, setting "copy referenced assemblies to works pace" but that didn't work. The referenced assemblies were NOT in the workspace directory and that's the problem.
Make sure you turn on this setting for all projects in the dependency chain, as using it on only a top level project may still result in some assemblies not being copied to the output directory (dependencies of dependencies).