starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

MSBuild issues warning on CascadiaPackage in VS 16.8 #11459

New Issue
Closed
opened 2026-01-31 02:48:14 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 02:48:14 +00:00
Owner
Copy Link

Originally created by @skyline75489 on GitHub (Nov 17, 2020).

The project 'CascadiaPackage' ran into a problem during the last operation: The value of the 'TargetFrameworkMoniker' and 'NuGetTargetMoniker' properties in the 'Release|x64' configuration are both empty. This configuration will not contribute to NuGet restore, which may result in restore and build errors. You may need to reload the solution after fixing the problem.

Is it just me? It keeps showing when I launch the project using VS 16.8

Originally created by @skyline75489 on GitHub (Nov 17, 2020). > The project 'CascadiaPackage' ran into a problem during the last operation: The value of the 'TargetFrameworkMoniker' and 'NuGetTargetMoniker' properties in the 'Release|x64' configuration are both empty. This configuration will not contribute to NuGet restore, which may result in restore and build errors. You may need to reload the solution after fixing the problem. Is it just me? It keeps showing when I launch the project using VS 16.8
claunia commented 2026-01-31 02:48:15 +00:00
Author
Owner
Copy Link

@Don-Vito commented on GitHub (Nov 17, 2020):

@skyline75489 - I have the same error as well.

@Don-Vito commented on GitHub (Nov 17, 2020): @skyline75489 - I have the same error as well.
claunia commented 2026-01-31 02:48:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 17, 2020):

This would not be the first time the WAP Packaging Project has spontaneously and aggressively broken our project. Does it still deploy?

@DHowett commented on GitHub (Nov 17, 2020): This would not be the first time the WAP Packaging Project has spontaneously and aggressively broken our project. Does it still deploy?
claunia commented 2026-01-31 02:48:16 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Nov 17, 2020):

Deployment seems fine. Only the warning keeps poping up.

获取 Outlook for Androidhttps://aka.ms/ghei36

@skyline75489 commented on GitHub (Nov 17, 2020): Deployment seems fine. Only the warning keeps poping up. 获取 Outlook for Android<https://aka.ms/ghei36>
claunia commented 2026-01-31 02:48:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 20, 2020):

Marked help wanted & backlog but it's not on fire so I don't mind it. 😄

@DHowett commented on GitHub (Nov 20, 2020): Marked help wanted & backlog but it's not on fire so I don't mind it. :smile:
claunia commented 2026-01-31 02:48:16 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Dec 3, 2020):

One thing that bothers me is that the warning somehow interferes with the font setting. When I open the OpenConsole solution, the font used by Visual Studio will fallback to system default, instead of the "good-looking" one I chose. However this does not happen with other solutions. So I suspect it's because of the warning.

@skyline75489 commented on GitHub (Dec 3, 2020): One thing that bothers me is that the warning somehow interferes with the font setting. When I open the OpenConsole solution, the font used by Visual Studio will fallback to system default, instead of the "good-looking" one I chose. However this does not happen with other solutions. So I suspect it's because of the warning.
claunia commented 2026-01-31 02:48:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 6, 2021):

Guh, I got the 16.8 flight over the holidays. Boy, InfoBars with warnings that are totally irrelevant sure are annoying 😅

I think the fix is just

diff --git a/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj b/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj
index 3d918935a..dd88eb674 100644
--- a/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj
+++ b/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj
@@ -5,6 +5,7 @@
   <PropertyGroup Label="Configuration">
     <!-- This is necessary so the build system doesn't think we're a .NET project... -->
     <TargetRuntime>Native</TargetRuntime>
+    <NuGetTargetMoniker>win</NuGetTargetMoniker>
     <TargetPlatformVersion>10.0.18362.0</TargetPlatformVersion>
     <TargetPlatformMinVersion>10.0.18362.0</TargetPlatformMinVersion>
     <!--

I have no idea if that's the real fix or not. I bet this is because VS thinks that a wapproj is technically a C# project, when really it's not. So it thinks it needs to find this property. I'll ping our internal contact to see if he knows about this.

@zadjii-msft commented on GitHub (Jan 6, 2021): Guh, I got the 16.8 flight over the holidays. Boy, InfoBars with warnings that are totally irrelevant sure are annoying 😅 I _think_ the fix is just ```diff diff --git a/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj b/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj index 3d918935a..dd88eb674 100644 --- a/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj +++ b/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj @@ -5,6 +5,7 @@ <PropertyGroup Label="Configuration"> <!-- This is necessary so the build system doesn't think we're a .NET project... --> <TargetRuntime>Native</TargetRuntime> + <NuGetTargetMoniker>win</NuGetTargetMoniker> <TargetPlatformVersion>10.0.18362.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.18362.0</TargetPlatformMinVersion> <!-- ``` I have _no idea_ if that's the real fix or not. I bet this is because VS _thinks_ that a `wapproj` is technically a C# project, when really it's not. So it thinks it needs to find this property. I'll ping our internal contact to see if he knows about this.
claunia commented 2026-01-31 02:48:17 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jan 6, 2021):

Am I the only one getting the infobar that says “1ES want you to upgrade VS for security reasons” then listened? Yeah then I got this infobar. One bar for another.

@skyline75489 commented on GitHub (Jan 6, 2021): Am I the only one getting the infobar that says “1ES want you to upgrade VS for security reasons” then listened? Yeah then I got this infobar. One bar for another.
claunia commented 2026-01-31 02:48:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 6, 2021):

LOL Yea, I just usually let someone else on the team bite the bullet first, considering how frequently VS updates break our project

@zadjii-msft commented on GitHub (Jan 6, 2021): LOL Yea, I just usually let someone else on the team bite the bullet first, considering how frequently VS updates break our project
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Build Help Wanted Issue-Bug Product-Meta Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11459
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?