question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Project Properties UI showing doubled input controls for Microsoft.VisualStudio.ProjectSystem.Managed.VS

See original GitHub issue

Visual Studio Version: main

Summary:

The UI shows doubled edit controls for selected properties.

Steps to Reproduce:

  1. Open ProjectSystem.sln
  2. Enable the preview flag for the new UI
  3. Show the project properties for project Microsoft.VisualStudio.ProjectSystem.Managed.VS
  4. 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

image

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
tmeschtercommented, Apr 12, 2021

Observations:

On my local system, msbuild /p:Configuration=Debug /pp Microsoft.VisualStudio.ProjectSystem.Managed.VS.csproj and msbuild /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. Running msbuild /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.

0reactions
davkeancommented, Sep 20, 2021

@drewnoakes @tmeschter Despite living in a configuration-independent location, The assets file is configuration-dependent, hence why we restore when the configuration changes.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found