Nov 12, 2011 at 1:13 AM
Edited Nov 12, 2011 at 1:14 AM
Thanks, that is what I figured. I have run into this problem several times with other packages too such as NLog, where config adjustments are needed in the app project but logging is handled in another project.
In some cases adding the package to both projects works out okay, it really depends on what the package does. Usually though it results in an unneeded reference in one project and sometimes file additions that are unwanted.
One solution could be having some sort of "package installation options" where we could still install the package in multiple projects but in one project we might just want a web or app config update and in another references and file additions etc. Otherwise
it seems it might require some sort of solution level option with selective project picking. Either way it would require some user input as something as simple as a config update cannot be assumed as there could be multiple startup projects and multiple config
Well hopefully there will be something added at some point to address this and I'm open to suggestions for that as well as any suggestions until then. Thanks