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

Issue with ColorCode Build #28

Closed
michael-hawker opened this issue Sep 30, 2022 · 5 comments · Fixed by #31
Closed

Issue with ColorCode Build #28

michael-hawker opened this issue Sep 30, 2022 · 5 comments · Fixed by #31
Assignees
Milestone

Comments

@michael-hawker
Copy link
Member

michael-hawker commented Sep 30, 2022

C:\hostedtoolcache\windows\dotnet\sdk\6.0.400\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(358,5): error NETSDK1127: The targeting pack Microsoft.NETCore.App is not installed. Please restore and try again. [D:\a\1\s\ColorCode.WinUI\ColorCode.WinUI.csproj]

Something happened in the last couple of weeks and now something is wrong in the build environment.

@Arlodotexe mind taking a look?

@michael-hawker michael-hawker added this to the 7.1.3 milestone Sep 30, 2022
@Arlodotexe Arlodotexe moved this to In Progress in Windows Community Toolkit Oct 4, 2022
@Arlodotexe Arlodotexe moved this from In Progress to Todo in Windows Community Toolkit Oct 4, 2022
@Arlodotexe Arlodotexe self-assigned this Oct 4, 2022
@Arlodotexe Arlodotexe moved this to In Progress in Windows Community Toolkit Oct 5, 2022
@michael-hawker michael-hawker changed the title Issue with Build Issue with ColorCode Build Oct 6, 2022
@michael-hawker
Copy link
Member Author

Not sure if this is related: dotnet/core#3868

@michael-hawker
Copy link
Member Author

Oh, I just noticed that this PR was done from the root of someone's fork (instead of a branch): #15 😡 It could be something bled over with the merge done here 697c527 (deleted file, etc...) that's disrupted the build config?

Will see if I can compare before and after that PR was merged.

@michael-hawker
Copy link
Member Author

Going back even another LNG commit, I don't see anything out of the ordinary in the comparison:

040e6ba...main

So, not sure what else may be going on here. We'll have to see if we can repro locally I guess? And then maybe see if reverting back changes anything or if this is an environmental thing, since we know the VMs were updated recently with the issue we saw in Labs.

@michael-hawker
Copy link
Member Author

Asked in the C# discord here as well: https://discord.com/channels/143867839282020352/1029140553155219496

@michael-hawker
Copy link
Member Author

michael-hawker commented Oct 19, 2022

@Arlodotexe on your most recent run of #29 it gave a slightly different error:

"D:\a\1\s\ColorCode.WinUI\ColorCode.WinUI.csproj" (Pack target) (4) ->
       (ResolveRuntimePackAssets target) -> 
         C:\hostedtoolcache\windows\dotnet\sdk\6.0.400\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(430,5): error NETSDK1112: The runtime pack for Microsoft.Windows.SDK.NET.Ref was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'any'. [D:\a\1\s\ColorCode.WinUI\ColorCode.WinUI.csproj]

Seems similar to discussion here? microsoft/WindowsAppSDK#1237 (comment)

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

Successfully merging a pull request may close this issue.

2 participants