I have the following problem:
Project A has a specfic NLog.config file.
TestProject B references Project A.
Project B has a different NLog.config file.
For project B 'Copy Referenced Assemblies To Workspace' is selected.
The workspace folder of project B now contains the NLog.config file from project A.
With the normal build system from Visual Studio it would contain the NLog.config file from project B.
Is it possible to fix this?
Regards
Wilhelm
Build/Test Issues
Issue with 'Copy Referenced Assemblies To Workspace'
Started by wilhelmmedetz on 6,254 views
Remco NCrunch Developer
#7488
17 Jul 2015 23:47 UTC
Hi Wilhelm,
Thanks for reporting this. I've done some quick tests and confirmed that this issue is caused by NCrunch overwriting existing files when copying referenced resource files across projects - something that MSBuild/VS doesn't normally do.
Do you mind if I include a fix for this in the next release?
Cheers,
Remco
Thanks for reporting this. I've done some quick tests and confirmed that this issue is caused by NCrunch overwriting existing files when copying referenced resource files across projects - something that MSBuild/VS doesn't normally do.
Do you mind if I include a fix for this in the next release?
Cheers,
Remco
Would be fine if it is fixed in the next release.
The current workaround is to use assembly specific config files, which have different names, and to include the NLog.config info in these config files.
Greetings
Wilhelm
The current workaround is to use assembly specific config files, which have different names, and to include the NLog.config info in these config files.
Greetings
Wilhelm
Post a reply
Log in to reply.