-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buildalyze removes alias information in result since v 7 #291
Comments
Can you provide an example project that reproduces this issue, so that we can start from there? |
Here is a solution where the test project refers to the production project via an alias (aliased project reference) and uses xunit attributes via an alias (aliased package reference). |
do you need anything else ? |
A PR would also be fine. @phmonte did not respond yet, which worries me a bit. I've some PR's open as well, and as he is the (new) owner of the repo, I can not release nor merge anything without his interference. :( |
Assembly aliases were available in previous Buildalyzer's versions. Alias information are no longer available since V7.
In early version, aliased assemblies appeared as
alias=assembly
references. Since V7, thealias=
part has disappeared.This impacts Stryker as it is no longer able to build project using assembly aliases.
We did implement a workaround using
Packages
information, but this works only when AssemblyName==PackageName and it does not support project reference aliases at all.I do not think reverting to previous behavior is a good idea, I propose aliases information to be available as map matching assembly pathname to their alias(es).
I am willing to work on a PR to implement this.
The text was updated successfully, but these errors were encountered: