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

version conflict WindowsAppSDK 1.3 unpackaged #3591

Closed
PetrAltman opened this issue Apr 21, 2023 · 6 comments
Closed

version conflict WindowsAppSDK 1.3 unpackaged #3591

PetrAltman opened this issue Apr 21, 2023 · 6 comments
Labels
area-Deployment Issues related to packaging, installation, runtime (e.g., SelfContained, Unpackaged) bug Something isn't working Status: Fixed internally The issue has been fixed but has not yet shipped in a release.
Milestone

Comments

@PetrAltman
Copy link

Describe the bug

After upgrading WindowsAppSDK to version 1.3 there are 3 build warnings about version conflict when using unpackaged application (None).

C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\include\MddBootstrapAutoInitializer.cs(34,38,34,77): warning CS0436: The type 'Release' in 'C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\buildTransitive..\include\WindowsAppSDK-VersionInfo.cs' conflicts with the imported type 'Release' in 'Microsoft.WindowsAppRuntime.Release.Net, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\buildTransitive..\include\WindowsAppSDK-VersionInfo.cs'.
C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\include\MddBootstrapAutoInitializer.cs(35,33,35,72): warning CS0436: The type 'Release' in 'C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\buildTransitive..\include\WindowsAppSDK-VersionInfo.cs' conflicts with the imported type 'Release' in 'Microsoft.WindowsAppRuntime.Release.Net, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\buildTransitive..\include\WindowsAppSDK-VersionInfo.cs'.
C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\include\MddBootstrapAutoInitializer.cs(36,49,36,96): warning CS0436: The type 'Version' in 'C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\buildTransitive..\include\WindowsAppSDK-VersionInfo.cs' conflicts with the imported type 'Version' in 'Microsoft.WindowsAppRuntime.Release.Net, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'C:\Users\x.nuget\packages\microsoft.windowsappsdk\1.3.230331000\buildTransitive..\include\WindowsAppSDK-VersionInfo.cs'.

Without None there are not any warnings.

Steps to reproduce the bug

Create empty WinUI application, upgrade WinAppSDK to 1.3 and add None.

Version conflicts warnings appears.

Expected behavior

There should be no build warnings.

Screenshots

No response

NuGet package version

Windows App SDK 1.3.0: 1.3.230331000

Packaging type

Unpackaged

Windows version

Windows 10 version 22H2 (19045, 2022 Update)

IDE

Visual Studio 2022

Additional context

No response

@bpulliam bpulliam added the area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration label Apr 27, 2023
@ajkennedy-HEC
Copy link

Our team is affected by the same exact issue after updating from 1.2.4 to 1.3 (unpackaged). No amount of restarting VS or rebuilding the solution fixes it.

@salmelo
Copy link

salmelo commented May 3, 2023

I just upgraded a new project and am getting the same issue.

@nickrandolph
Copy link

Seeing this issue as well!

@evelynwu-msft
Copy link
Contributor

https://task.ms/44532535

@evelynwu-msft evelynwu-msft added area-Deployment Issues related to packaging, installation, runtime (e.g., SelfContained, Unpackaged) Status: Fixed internally The issue has been fixed but has not yet shipped in a release. and removed area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration labels May 27, 2023
@majaeger
Copy link

Is there any workaround possible to get past this?

@evelynwu-msft evelynwu-msft added the bug Something isn't working label Jun 17, 2023
@codendone codendone added this to the 1.4 milestone Nov 16, 2023
@codendone
Copy link
Contributor

Closing as fixed in 1.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Deployment Issues related to packaging, installation, runtime (e.g., SelfContained, Unpackaged) bug Something isn't working Status: Fixed internally The issue has been fixed but has not yet shipped in a release.
Projects
None yet
Development

No branches or pull requests

8 participants