I've noticed that in VS 2010 Professional(in university) you can step into stl and stdlib functions and debug the actual insides, tried to do the same in VS 2017 Community but it didn't work, it even refuses to disassemble them, same goes for VS 2013 Ultimate(i assumed it's a professional version feature).
Now i'm wondering if there is a way to make this work in 2017 community or 2013 ultimate, am i doing anything wrong? I know you can probably find all the source codes on the internet, but i want to make it work in visual studio, so that i can actually debug it.
Related
I would like to know if I can somehow compile c++ code in visual studio express 2010 with a 2019/2022 compiler. I only want to use express 2010 as an editor. I get no results on google regarding this topic.
Edit: I can change from platform toolset V100 to V90 but I'd like V143 like VS 2022. Is it possible though?
It is possible, but why on earth would you want to continue using Visual Studio Express 2010 as your IDE? VS2022 is so full of goodies and the community edition is free to use.
That being said: The VS2019/VS2022 compilers are just cl.exe, link.exe etc... You can use these compilers instead of the VS2010 cl.exe, link.exe etc... The VS2010 integrated build system will not automatically find them, so you'll either have to fiddle around with paths, get in to trouble with compiler switches etc...
You could switch to makefiles (or CMake) to use the compilers and keep the IDE. VS2010 is then no more than a fancy editor.
Tip: Try compiling your code from the command line (cmd.exe) to get started. Or download VS2022 community edition.
I would like to know how I can tune Visual Studio 2019 to have a fully featured modern Fortran IDE for gfortran.
This would include:
one click compilation
debuging
auto-completion
If you also known any other interesting feature I would be interested.
Many thanks.
Can I use Roslyn and all its tooling in Visual Studio 2015 Community edition?
I am about to download the community edition and it's a big decision for me given that I have a single piece of hardware, my laptop, which I use for everything, and the only reason I am going to download 2015 is because I want to practice coding Roslyn, which is not available in the VS 2013 or earlier expression editions.
"Roslyn" is just the compiler platform in Visual Studio 2015. So yes, the Community edition has Roslyn.
We've been referring to it by its code name for so long that it's not really clear, but "Roslyn" is simply a rewrite of the C# and VB .NET compilers in managed code. On top of the compiler platform, you can write extensions to interact with code and the IDE as it's parsed in the form of quickfixes and refactorings.
The Visual Studio Community editions are nearly functionally identical to Visual Studio Professional, albeit under different license terms. This includes extension support.
The Roslyn GitHub page has awesome documentation to help you get your head wrapped around it.
We just switched over to VS 2013 and I heard that you're supposed to be able to
generate code maps for your entire application. Awesome feature indeed, that could
get new developers on our project up to speed.
Watched a couple of tutorials, but when I tried to just right click on a method
in the application, the 'Show on Code Map' context menu is missing. In fact, I
can't find anything in VS that has anything to do with Code Maps.
My version:
Visual Studio Premium 2013
I tried installing Modeling SDK for Microsoft Visual Studio 2013, but that didn't do anything.
Anyone got any ideas?
You need Visual Studio ULTIMATE to create Code Maps.
http://msdn.microsoft.com/en-us/library/jj739835.aspx
This has changed for Visual Studio 2015 and Visual Studio 2017:
The Enterprise Edition allows creating code maps.
The Community and Professional Editions can open diagrams generated in other Visual Studio editions in read-only mode.
When I am reading docs about sos.dll #MSDN, encounter a note says
If you are using Visual Studio 2013, SOS.dll is supported in the Windows Debugger within Visual Studio
I know how to use sos.dll in the immediate window in Visual Studio 2012. But how to use sos.dll with visual studio 2013 debugger?
From MSDN documentation of What’s New for the Debugger in Visual Studio 2013 (Excerpt from the part Debug With Debugging Tools for Windows)
The SOS.dll (SOS Debugging Extension) that helps you debug managed
programs in WinDbg, is not available from the Visual Studio IDE. See
Debugging Managed Code Using the Windows Debugger
Looks like you may need to load them separately as being said Here
I couldn't get sos.dll to load in Visual Studio 2013 no matter what I tried.
I've resorted to good old WinDbg instead. I know it's not an ideal answer, but it appears to be the only possible solution to debugging with sos.dll. I'd really like to use sos.dll in Visual Studio 2013, but WinDbg isn't so bad once you learn its basics. It's actually very powerful, even if you know very little about the unmanaged world (like me).
How to load SOS in WinDbg
Yes you can use SOS from VS 2017. But you will need to install windows driver kit (WDK). Here is a screenshot of me debugging a process with command line debugger within VS 2017.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-user-mode-debugging-in-visual-studio