Importing a folder into Visual Studio 2017 - c++

I am a college student and often I am given project folders for courses with multiple C++ header files, source files, and a makefile usually. I am using Visual Studio 2017 for reference.
Visual studio is my favorite IDE for debugging but I do not know how to integrate one of these folders into Visual Studio so I might debug from the application and not from a terminal. I am wondering if someones knows a way for me to open this folder in VS, and run/debug it like a normal console application? I realize the makefile might add an additional layer of complexity.
This is an image of the contents of a folder I want to be able to run/debug/execute normally in visual studio
I can open this folder in visual studio by right clicking -> open in visual studio.
However when in visual studio, I cannot build, run, debug or anything. Visual studio is acting more like a text editor than an actual IDE. I would like to be able to build/make my program through visual studio so I can launch/debug it in visual studio.

Related

Working with Visual Studio C++ project in Visual Studio Code

I have a C++ project in Visual Studio and I much prefer Visual Studio Code for editing source files.
Is there a way to work with Visual Studio C++ projects in Visual Studio Code? Like getting include paths from ".sln" file or maybe even running MSBuild.
Open Developer Command Prompt/PowerShell for VS 2019. This will set necessary environment variables such as include paths.
Navigate to the directory of your project.
Type code . to start VS Code in your current directory.
Now, you will be able to use commands like cl, msbuild etc in the integrated terminal.
Happy coding.

Using UE4 with Visual Studio 2017

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.

Open a vdproj file with VS Community 2017?

I retrieved a C++ VS project from 2011 and it has a Install-win32.vdproj I guess it has to be the file I need to open in order to build the project.
Unfortunately Visual Studio 2017 seems not to recognize this kind of file. Is there any ways to interpret it or convert it?
For VS2017, use the Microsoft Visual Studio Installer Projects. Download link is below. Be sure to close Visual Studio before running the installer:
https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects

New to C++, Visual Studios Professional 2013 can't run projects made in Visual Studios C++ Express 2010

And now, the projects that I tried to open and run (very basic projects - little more than learning programs like hello world type programs) in VS 2013 can't be opened and run in VS Express 2010 either. Everything is licensed properly.
In fact, when I open my program in VS Express 2010 now, it underlines basic things in the header like "iostream" in red, and doesn't recognize them.
If I build a new project in either, it's just fine. But I can't get projects to work across one from the other, and if I do try, it does some rebuild, and then those projects won't work in either.
What is going on?
Actually, that happened with me when I tried to use a project of gmap.net (winforms) that I made with Visual Studio 2013 into the new version of VS 2015.
Into my case, I could see all the code I had made in C#, but I couldn't change the design of the project and I think that it will be impossible so I have been working with both.
But in your case, if you want just open the code, you should find the file with .csproj or something similar to this and do not open the project by the .sln if you know what I mean.
Doing this it will work just fine. And of course, don't forget that you should import all extensions to your new VS.
PS:
I found a nice explation of your problem here at the Visual Studio website. And this was the answer:
If you allow Visual Studio to update the project automatically, you can open it in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1.

Visual Studio Express 2013 freezes when opening project properties

Main Problem
When I try to access the properties of a project in Visual Studio Express 2013 for Windows Desktop through Project -> ProjectName Properties, Visual Studio freezes completely without an error and I must end it through the Windows Task Manager.
I ran Visual Studio with /safemode enabled. This did provide some information by saying that "The 'Visual Studio Component Model Host Package' package did not load correctly."
It also produced a log file with some errors and warnings. Errors and warning entries in the log can be searched for with <type>Error</type> and <type>Warning</type> respectively. Additionally, opening the file in Internet Explorer seems to apply some styles to the file and makes it more readable.
Errors only - http://pastebin.com/295sX8kH
Full log - http://pastebin.com/KGspUgGs
The errors in the log seem to center around this Visual Studio Component Model Host Package. I tried searching for errors related to that, but did not find anything I thought was applicable to my situation.
The dll Microsoft.VisualStudio.ComponentModelHost.Implementation.dll is present in C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies\
The dll Microsoft.Data.Entity.Design.DataSourceWizardExtension.dll is indeed missing from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\DataDesign
Extra Info
I am using version 12.0.30723.00 Update 3 of Visual Studio and I am running Windows 7 Professional 64-bit 6.1 build 7601.
I have tried re-installing Visual Studio in order to to clear out any bad settings, but that did not seem to work.
I tried running Visual Studio with /resetskipkgs and /resetsettings, and neither of those worked.
Trying to open project properties in safe mode still froze Visual Studio.
Backstory
I am ultimately trying to setup an environment in which to develop OpenGL applications. I have some experience with it through following the Arc Synthesis tutorials, but I do not know how to operate outside of the specialized environment the tutorials provided.
Following the OpenGL Book setup instructions, I am told development will go more smoothly if I use the GLEW and freeGLUT libraries. In order to do so, I need to be able to link in extra files to a project. In Visual Studio, this is done through the project properties dialog, but I cannot access it due to the freezing problem.
I am not very familiar with the development process in C++, so I am wary of venturing outside of the IDE provided by Visual Studio, but I might just have to do that if this problem persists.