Menu
When I go to edit a properties page in Visual Studio 2015 with C++, I'm always getting the error, "There are no property pages for the selection." This usually happens when I'm switching from one Platform to another (e.g. x64 -> Win32).
Usually it will work if I switch the platform from the main window, but if I try to switch it in the Property Pages, I always get that error.
Thanks for the help.
449
The project properties where no longer accessible and gave the "There are no property pages [...]" error. The cause was that VS2010 was installed as german version, while VS2015 was set to english. Changing VS2015 to german fixed the problem, changing both to english fixes the problem.
Applies to: Visual Studio Visual Studio for Mac Visual Studio Code Users can view and change project configuration-dependent and -independent properties using property pages. A Property Pages button is enabled in the Properties window or on Solution Explorer toolbar for objects that provide a property page view of the selected object.
In the first, for Visual Basic projects, for example, the property pages are displayed using a field format, as shown in the following screenshot. In the second, shown later in this section, the property page hosts a properties grid similar to that found in the Properties Window.
Locate project file (.csproj) and click Open. In the Solution Explorer, the project will still have (unavailable) message besides it. We still need to carry out one more step. Right-click on the project to open context menu. Select Reload Project as shown below: Reloading the unloaded project in the solution explorer. Build solution.
I think this is a bug that has been in Visual Studio since forever. Through experimentation I have discovered that you only hit this bug if you open the project properties by going to the Project menu and selecting <ProjectName> Properties.... Instead, if you open the Solution Explorer toolbar, and then right-click on the project and select Properties from the context menu, you will not hit this issue.
117
This problem seems to be linked between MSBuild tools and environment paths. On visual studio 2017 v15, after I had downloaded MSBuild tools it updated the VCTarget path to
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
where it should actually point to
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin
In my case changing the environment path wasn't working and eventually I had to manually update the VCTargets path from regedit: HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions
also make sure the priority of path you define in environment variable is correct.
34
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
