My Visual Studio 2017 stopped showing project properties properly.
It's empty in both the Application and Compilation sections:
As such, I can't change the application icon or the project type, neither add .xml documentation.
How do I fix this?
Related
I have Visual Studio 2017 Community 15.7.2 installed. The build configuration drop down options disappear. I have been having Problems with the build configuration disappearing on my work machine (Visual Studio 2017 Enterprise 15.8.2) as well.
If I create a new project File -> New Project -> Web -> ASP.Net Web Application (.Net Framework).
The build configuration option shows up. Then if I click on a controller class e.g. HomeController.cs. The option clears out.
The option will show up again after changing "Show output from" under the Output window. If I bring up a .cs file again. The build option disappears:
Is this now a normal behavior in Visual Studio? I suspect a bug in Visual Studio and have been updating more often than usual in attempt to fix it.
The latest update to Visual Studio Community 2017 (15.8.4) did not fix the problem.
Go through each of the Tools -> Extensions and Updates and disable an extension and then restart Visual Studio. Start with ones that aren't created by Microsoft.
Repeat this until you have tried all the extensions.
Today I updated my Visual Studio 2017 to the current version 15.3.3.
Afterwards code errors are not highlighted in the code editor anymore.
What I've tried so far:
Resetting user settings
Deleting the .vs folder from my solution
Deleting the visual studio folder from my AppData folder
Repairing VS with the Visual Studio Installer
Clean installation of Visual Studio (so no VS extensions or plugins installed)
In new created projects IntelliSense and the error highlighting is working as expected. I have this issue only in my existing ASP.NET 4.5 projects.
So this is obviously connected with some project settings. Then again my colleagues are working with the same project and same VS version with no issues.
Any ideas?
I recently did some cleaning of my drives. I decided to install visual studio 2017 after cleaning the drives up. I have been trying to continue work on my old UE4 project using the engine pulled from GitHub. I tried rebuilding the project with VS2017 which I know is not fully supported yet. I did run into quite a few problems, including the missing corecrt.h files. I reinstalled the Windows SDK to fix this.
The current problem is a new missing file called windows.h, and I believe it is missing due to the build tools looking for the wrong version of the SDK. I was wondering, has anyone else successfully integrated Visual Studio 2017 with their UE4 project after running into similar problems?
-- Edited due to poor grammar.
As I know Version 4.15 supports both Visual Studio 2015 (default) and Visual Studio 2017. If you are building the Engine from source code, you would want to open a command prompt after running Setup.bat and run the command GenerateProjectFiles.bat -2017. This will give you a Visual Studio 2017 solution for the Engine.
To use Visual Studio 2017 for projects, you can set your preference for which version projects use by going to Edit -> Editor Preferences -> General -> Source Code and choosing Visual Studio 2017 in the Source Code Editor setting.
If regenerating the Engine's VS project files doesn't help. Try regenerating your own UE4 project's VS project files.
With Visual Studio and UE4 closed, find the .uproject file, right click and select Generate Visual Studio project files.
Open the solution, make sure your UE4 game (e.g. MyProject) under the Games folder is set as the StartUp project (right click, Set as StartUp project), then try a compile.
Where I work, we are stuck on VS2008 and will be for quite some time as converting the projects/solutions and integrating them back into our build process would take significant time; we're planning on moving to 2013 at some point though. However, I use VS2012 at home and love a lot of the features in the IDE that are missing in 2008.
I've read that you can use 2012 as an IDE and build with the 2008 compiler, but I can't find details on how this is accomplished. Any ideas? If I open one of the masterbuild files in 2012, it inevitably asks to convert them to the 2012 format, which I really don't want to do.
Thoughts? Thanks!
Yes it is possible as can be found on the Visual Studio site. However, I believe it will only give you options of the versions you have currently installed on the machine in question.
Here are the steps as laid out in the link, provided here to ensure the information link does not get broken:
(authored and published by Microsoft)
To change the target Framework
In Visual Studio, in Solution Explorer, open the shortcut menu for your project and then choose Unload project. This unloads the project (.vcxproj) file for your project.
Note: A C++ project cannot be loaded while the project file is being modified in Visual Studio. However, you can use another editor such as Notepad to modify the project file while the project is loaded in Visual Studio. Visual Studio will detect that the project file has changed and prompt you to reload the project.
On the menu bar, select File, Open, File. In the Open File dialog box, navigate to your project folder, and then open the project (.vcxproj) file.
In the project file, locate the entry for the target Framework version. For example, if your project is designed to use the .NET Framework 4.5, locate v4.5 in the element of the element. If the element isn't present, your project doesn't use the .NET Framework and no change is required.
Change the value to the Framework version you want.
Save the changes and close the editor.
In Solution Explorer, open the shortcut menu for your project and then choose Reload Project.
In Solution Explorer, open the shortcut menu for your project and then choose Properties. In the Property Pages dialog box, in the left pane, expand Common Properties and then select Framework and References. Verify that Targeted framework shows the new Framework version.
To change the project toolset
In Visual Studio, in Solution Explorer, open the shortcut menu for your project and then choose Properties.
In the Property Pages dialog box, open the Configuration drop-down list and then select All Configurations.
In the left pane of the dialog box, expand Configuration Properties and then select General.
In the right pane, select Platform Toolset and then select the toolset you want from the drop-down list. For example, if you want to compile with the Visual Studio 2010 toolset, select Visual Studio 2010 (v100).
Choose the OK button.
Try to use CMake. It could manage out of source build. You could create a VS2012 for edit and another VS2008 based for compiling. The source will be common.
From Visual Studio 2012 Compatibility page on MSDN
Some solutions, projects, files, and other assets that you created in
Visual Studio 2010 Service Pack 1 (SP1) will run without modification
in Visual Studio 2012, but others have to be upgraded.
If your original project is 2008 then you won't be able to use it in 2012, sorry.
I had a command line build which was working fine with Visual Studio 2010.
I am now trying the same solution with Visual Studio 2012.
When I build it via the command line:
devenv MediaPlayer.sln /build "Release|Any CPU"
I get a pile of errors with the website:
37>------ Build started: Project: C:...\Web\, Configuration: Debug
Any CPU ------
37>Cannot update project reference ''. Source project
not available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Cannot update project reference ''. Source project not
available.Validating Web Site
But then I open the SAME solution in Visual Studio 2012, and build it. It builds.
I then run this same build via the command line, and it builds.
So I check it in, and let the build process fetch it into the build directory, and I get THE SAME ERRORS.
At this point, I'm stumped as to what to do next. Any pointers?
When the Visual Studio 2012 build output says
Cannot update project reference
It's actually saying
Something went wrong, and you know what?
I'm not going to tell you what it is!
BWAHAHAHAHAHAHAHAHAHAHAHAHA
After a full days search, it came down to a third party library (Castle.Windsor.dll) not being in the .bin directory. I don't know why this problem showed up with Visual Studio 2012 and not Visual Studio 2010. My guess is that in Visual Studio 2010, this was automatically copied over because it was a dependency of another project the website was dependent on.
I manually created a .refresh file for Castle.Windsor.dll and Castle.Core.dll, and now it builds.
I also experienced this same error when trying to build a solution in VS 2012.
I had a solution that I upgraded from VS 2010 to VS 2012 and then started removing some long dead projects. VS 2012 became "confused" with this removal and deemed that a website project in the solution needed a reference to '', which was not available.
To resolve this, I undid the above mentioned changes to the solution, opened it up in VS 2010, removed the long dead projects and built successfully and then closed VS 2010. I was then able to open/update the solution in VS 2012 and work without issue.