You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Is Buildalyzer overwriting existing build artefacts (e.g. "*.exe.config" files, when "create binding redirects" is enabled in project file)? #320
I have C# project solution to analyze ("*.sln"), containing three projects:
MyLib.Services
MyLib.Services.Contracts
MyLib.Services.Test
The "MyLib.Services.Test" project has setting "automatically create binding redirects" enabled.
Building the solution within Visual Studio generates all binaries and also the file "MyLib.Services.Text.exe.config".
These "*.config" file contains all generated binding redirects.
If I then analyze the solution with Buildalyzer (calling "build") all binaries from the previous build are overwritten and also the "MyLib.Services.Test.exe.config" file ist overwritten.
But this new "MyLib.Services.Test.config" file has NO binding redirect entries anymore.
As result the execution of the unit tests project is failing after analyzing with buildalyzer because of missing binding rediects.
I thought that Buildalyzer does not create real physical files. I'm wrong or is there a way to not overwrite existing files?
Activity