Skip to content
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

[Bug] #2167 breaks building WPF applications #2181

Closed
batzen opened this issue Mar 15, 2020 · 6 comments
Closed

[Bug] #2167 breaks building WPF applications #2181

batzen opened this issue Mar 15, 2020 · 6 comments
Labels

Comments

@batzen
Copy link
Contributor

batzen commented Mar 15, 2020

Describe the bug
The fixes made for #2167 seem to break building WPF applications because version attributes are added as duplicates.

Expected Behavior

Build should work and assembly info should not have duplicate attributes.

Actual Behavior

Assemblyinfo has duplicate version attributes.

Possible Fix

MarkupCompilePass1DependsOn should not be modified to contain UpdateAssemblyInfo.

Steps to Reproduce

Context

Tried to compile with the latest gitversiontask version.
Version 5.2.2 works fine. Only 5.2.3 shows this issue.

Your Environment

.NET Core SDK (reflecting any global.json):
Version: 3.1.101
Commit: b377529961

Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.101\

Host (useful for support):
Version: 3.1.2
Commit: 916b5cba26

@batzen batzen added the bug label Mar 15, 2020
@arturcic
Copy link
Member

@tpaxatb can you check this bug?

@tpaxatb
Copy link
Contributor

tpaxatb commented Mar 16, 2020

Yeah I realized after the fact that netcore apps seem to build slightly different (i didn't have netcore 3 sdk until friday). I think maybe on the .net core that the UpdateAssemblyInfo should be turned off in the props file or something. I'll see about taking a look later if/when I get a chance, as our office is in the process of transforming to mandatory work at home due to government directives yesterday and today.

@arturcic
Copy link
Member

Sure, take your time, any help is welcomed

@bording
Copy link
Contributor

bording commented Mar 16, 2020

Looks like the PR I just opened should fix this: #2183

@arturcic
Copy link
Member

@bording, ok then, after we merge your PR we will validate it here

@arturcic
Copy link
Member

closing, please reopen if still reproduces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants