Visual Studio very slow with C++ - visual-c++

I am new to C++ programming and have been setting up Unreal Engine 4 with Visual Studio 2019.
The problem I am facing is that VS seems very slow to recognize my code in C++.
For example, it can take more than 10 seconds to recognize that I wrote a method declaration and apply the proper color and give me intellisense (intellicode?) or show me any error. Same problem with variables and such. Code completion is pretty much never happening.
It's unusable right now and I would appreciate if somebody have an idea of what's going on.
I never have this problem in C#.
I tried activate / deactivate extensions (just got a couple of them). I have ran a VS repair.
I have a recent computer (i7 9k, 16gb RAM) running windows 10.
Thanks in advance.

Related

How to manage developing former Visual Studio solution in Linux?

sigh
In my third try to introducing Linux to my everyday life I'm still bouncing hard on programming.
I have solution for my major thesis' program created in Visual Studio (five projects in one solution; 4 static libs, one executable), and managed with it since it's beginning. It's posted on Git, so I thought, that I'll try changing it and compiling on my laptop with Ubuntu 18.4. While changing it was no-effort task (Linux text editors are neat; as opposed to almost non-existent IDEs), compiling in the other hand was the point I doubted in all my skills.
First problem I've encountered is that I have no idea how to manage multiple projects outside VS. I mean, there are .vcxproj files with data, but not very useful for what I saw.
Second problem are references - I have no idea how to link #include directories to specific point in files without going ../MainFolder/subfolder/file.h which is extremely unesthetic.
I expect, that those are just iceberg's peaks, and I will encounter massive amount of problems in future, but as for now - can anybody give me idea of how to manage such project in Linux?

Jump Start My VS 2015 Community Experience

My last experience with visual programming was with VB 6.0. So it's been awhile. Now I need a C code developement environment to interface with another tool. It would be nice to work in a visual programming and event driven IDE similar to my VB experience. The other tool vendor suggested installing the free VS 2015 Community package. What is the best way to download, install and get me up and running in this C code environment?
Download Visual Studio Community 2017 here:
https://www.visualstudio.com/vs/community
You don't need to install the full blown thing anymore, just pick the blocks your want to use. If you need more later on you can simply add more blocks.
It is free, and there are boatloads of samples around (check https://learn.microsoft.com/en-us/cpp/ for instance) to get you started.
Probably "microsoft official site" but i'd not recommended "comunity edition" just for one reason : [it's a bit overloaded], i know it may feels good to have space for growing up, but in fact (probably) you'll barely try a quarter stuffs they present for you. Before you become a "GURU" they will be just spotted your eyes and (a bit) slow down progress.
If you'll want do your codding on Windows 7 or earlier, you'd better try a (minimalistic) "Visual studio express 2013" (Same stuff, but more strict functionality). And... if you would try Visual studio express, it better to choose a version "x86", i cant say that does matters on "C", but if you'll start programming openGL, it's saves you a lot of nerves (64x has a several big errors)

Migrating FORTRAN95 and VC++6 code causes NaNs

I am working on a project that was written in FORTRAN95 (using the FTN95 compiler) and VC++6 that was moved to Intel Parallel Studio 15 and Visual Studio 2012 respectively. Since the migration, other features were added, but it was now discovered that an older feature generates NaN values at run-time in the FORTRAN code.
After several hours of debugging the program I am quite sure that the new features are not to blame, mainly because I only found causes of the bug in code which is the same as in the latest working version of the program (compiled with FTN95 & VC++6). Therefore I tend to believe that the issue was caused by the migration itself. Now the problem is that the program compiles without errors. Therefore I'm asking for any ideas on how I could solve this issue.
I know the description is vague at best and I cannot give many details about the bug since it stretches thousands of lines of code (the application is used for scientific calculations). Any ideas would be highly appreciated.
EDIT: Some general details about the bug
The program gets user input from the GUI and initializes corresponding variables in FORTRAN. This stage works as expected and values are passed correctly. After all the desired options have been chosen, the FORTRAN code runs it's calculations and outputs it's results (the NaN values) to a file.

Visual Studio 2013 creates larger exe's - no MFC

I'm a little late with this question, but better late than never. I've been using Visual Studio 6.0 since it came out, but recently switched to VS 2013 on a new PC.
I've gotten my projects to build under 2013, but the resulting executables it produces are consistently bigger than VS6.0 produced. I've seen a similar thread on here about that happening in the transition from VS2008 to VS2010, and the comments and suggestions there all seem to attribute the change to changes in MFC libraries that are statically linked in. But my projects are straight C code. No C++, let alone MFC. And the 'Use of MFC' option on my project is set to "Use Standard Windows Libraries" (presumably set by the import tool that generated the 2013-compatible project). The only non-stadard library it uses is wsock32.lib.
The extra size isn't a killer, but it's a significant relative to the size of the whole app. My biggest .exe goes from 980Kb to 1.3Mb - about a 35% increase in size to an app whose small size was a selling point (i.e. install this tiny app and you have access to all of our goodies). That's without debugging info - the increase on the debug version is even more - but I don't really care about that.
Any ideas how to strip out the new cruft - or even to know what it is?
This is a good manual how to make your binaries smaller.
Basic ideas are the following:
Don't forget about Release mode
Declare #define WIN32_LEAN_AND_MEAN
Dynamically link to the C++ runtime
Compile the executable without debugging information
Compile with /O1, an 'optimize for size' flag
Remove iostream and fstream headers, use low level instead if possible
Typically you generate a MAP file on both systems, and figure out the sections that cause the largest contributions.
Anton's answer reminds me: first check if they are both linked the same way (both static or both dynamic, otherwise it is apples and oranges)

C++ coverage tool that WORKS?

Been searching for a good coverage tool for a while now.
I'm with VC++ 2008.
Tried already:
NCover, PureCoverage, PartCover and a few others I can't remember their names.
None works!
Not even with a very basic console application that does almost nothing.
Tried to get an evaluation copy from BullsEye and few more others - not only that they require you to ask for it (no automatic process), they don't even answer after you request AND after you ask what's going on, through the support mail.
So the question is: Is there any tool, which I can immediately download an evaluation for it, that actually works on VC 2008 projects? Something that will get me going within 10 minutes? It's funny but it seems to be a very non-trivial request in the area of this kind of software.
Well, you have to ask for it... but it does work:
SD C++ Test Coverage
EDIT May 2011: Downloads available for since late 2010.

Resources