Is Buildalyzer overwriting existing build artefacts (e.g. "*.exe.config" files, when "create binding redirects" is enabled in project file)? · Issue #320 · Buildalyzer/Buildalyzer · GitHub
Skip to content

Is Buildalyzer overwriting existing build artefacts (e.g. "*.exe.config" files, when "create binding redirects" is enabled in project file)? #320

Open

Description

@mcreek

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions