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

PowerToysSetup build with VS2022 and .NET SDK 6 installed #14463

Closed
1 task
davidegiacometti opened this issue Nov 15, 2021 · 7 comments
Closed
1 task

PowerToysSetup build with VS2022 and .NET SDK 6 installed #14463

davidegiacometti opened this issue Nov 15, 2021 · 7 comments
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Bug Something isn't working

Comments

@davidegiacometti
Copy link
Collaborator

Microsoft PowerToys version

0.0.1

Running as admin

  • Yes

Area(s) with issue?

Installer

Steps to reproduce

Build PowerToysSetup.sln from VS2019 with VS2022 and .NET SDK 6 installed.

4>C:\Program Files\dotnet\sdk\6.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.ConflictResolution.targets(112,5): error NETSDK1152: Found multiple publish output files with the same relative path: C:\Users\david\.nuget\packages\colorcode.core\2.0.6\lib\netstandard1.4\ColorCode.Core.dll, C:\Users\david\source\repos\PowerToys\x64\Release\SettingsUI\ColorCode.Core.dll,

Build.log

✔️ Expected Behavior

Build succeed

❌ Actual Behavior

Build fail

Other Software

VS2022
.NET SDK 6

@davidegiacometti davidegiacometti added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Area-Build Issues pertaining to the build system, CI, infrastructure, meta labels Nov 15, 2021
@crutkas
Copy link
Member

crutkas commented Nov 17, 2021

do you have .net core 3.1 sdk?

@crutkas
Copy link
Member

crutkas commented Nov 17, 2021

#12285 would kinda solve this since we would upgrade to .net 6 :)

@crutkas crutkas removed the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Nov 17, 2021
@davidegiacometti
Copy link
Collaborator Author

Yes, I still have 3.1 SDK.
Thank you.
I think you can close this since I have been able to build the setup launching manually publish.cmd.

@crutkas
Copy link
Member

crutkas commented Nov 19, 2021

i think that isn't a great out of box experience. I don't like us not being F5 ready

@franky920920
Copy link
Contributor

franky920920 commented Nov 19, 2021

#12285 would kinda solve this since we would upgrade to .net 6 :)

@crutkas #12285 is talking about .NET 5, not .NET 6 😕

@crutkas
Copy link
Member

crutkas commented Nov 19, 2021

99% sure we’ll pick 6. When I wrote that issue 6 wasn’t out yet.

@davidegiacometti
Copy link
Collaborator Author

Working as expected with changes introduced for the new pipeline 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants