Project Properties UI showing doubled input controls for Microsoft.VisualStudio.ProjectSystem.Managed.VS
See original GitHub issueVisual Studio Version: main
Summary:
The UI shows doubled edit controls for selected properties.
Steps to Reproduce:
- Open
ProjectSystem.sln
- Enable the preview flag for the new UI
- Show the project properties for project
Microsoft.VisualStudio.ProjectSystem.Managed.VS
- Navigate to Build | Errors and warnings
Expected Behavior:
Single edit control when value does not vary by configuration.
Actual Behavior:
Doubled edit controls, despite there being no need for doubles
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Exception when trying to open project properties
When using Visual Studio 2022 17.1 Preview 1, trying to open project properties ... Microsoft.VisualStudio.ProjectSystem.VS.Implementation.PropertyPages.
Read more >Revamped Project Properties UI - Visual Studio Blog
We revamped the Visual Studio Project Properties UI. Check out the changes in our newest update, available in Visual Studio 2022.
Read more >Manage project and solution properties - Visual Studio ...
You access project properties by right-clicking the project node in Solution Explorer and selecting Properties, or by typing properties into the ...
Read more >MSBuild reference for .NET SDK projects
The UseAppHost property controls whether or not a native executable is created for a deployment. A native executable is required for self- ...
Read more >Build Page, Project Designer (C#) - Visual Studio (Windows)
Learn how to use the Build page of the Project Designer in Visual Studio to specify the project's build configuration properties.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Observations:
On my local system,
msbuild /p:Configuration=Debug /pp Microsoft.VisualStudio.ProjectSystem.Managed.VS.csproj
andmsbuild /p:Configuration=Release /pp Microsoft.VisualStudio.ProjectSystem.Managed.VS.csproj
produced different results. MSBuild couldn’t find the NuGet-generated .props and .targets files because they didn’t exist for the Release configuration. Runningmsbuild /t:restore /p:Configuration=Release Microsoft.VisualStudio.ProjectSystem.Managed.VS.csproj
caused those files to be generated, at which point the preprocessed output was the same (other than the paths to the .props and .targets generated by NuGet), and subsequently opening the property pages no longer showed the duplicated controls.My guess at the moment is that the missing .props/.targets somehow affects our ability to get the unevaluated value, but not the evaluated value. I will need to investigate further.
@drewnoakes @tmeschter Despite living in a configuration-independent location, The assets file is configuration-dependent, hence why we restore when the configuration changes.