1
Vote

make merging configurable

description

First of all, this package is awesome. Thank you.
One question: can you add an option to activate/deactivate merge in the ILMerge.props file or a different configuration file?
When working on a new feature, I code and test continuously. Only when all is implemented and tested I will merge assemblies in the end for easier distribution.
When the package is installed, my build wouldn't able to trigger unit/integration tests.
My current workaround is to install/uninstall the package to enable merge/enable tests.

comments

archnae wrote Mar 17, 2016 at 12:48 PM

I don't like the idea of having something that builds very differently in Debug vs Release configurations - some very unpleasant errors can surface in Release build precisely because of the merge step (think about internalized classes, namespace conflicts with 3rd parties, assembly names used in reflection API etc). It's better to catch them at the debug/testing stage, imho :)

In your case I'd recommend putting the merge step into a separate project containing only assembly properties and a dummy class and excluding this project from the Debug build.