When comparing Microsoft Visual Studio vs Code::Blocks, the Slant community recommends Code::Blocks for most people. In the question“What are the best IDEs for C++ on Linux?” Code::Blocks is ranked 6th while Microsoft Visual Studio is ranked 18th.
Ranked in these QuestionsQuestion Ranking
Pro Free Community Edition
The Community Edition of Visual Studios and the Unity add-on can be downloaded and used free of charge.
IntelliSense is the general term for a number of features: List Members, Parameter Info, Quick Info, and Complete Word. These features help you to learn more about the code you are using, keep track of the parameters you are typing, and add calls to properties and methods with only a few keystrokes.
Pro One of the few bearable C++ debuggers available
Pro There's a huge library of plugins
Visual Studio has a massive library of plugins to choose from.
Pro Modern language support
The recently released 15.7 branch provides competitive modern language support.
Pro Product backlog
In agile development teams, one really needs features such as product backlogs where you can assign features to team mates and track their progress on them. VS provides a web based interface for you to track your team's complete progress on the project.
Pro GitHub integration
Makes production faster especially if git is used. One can see changed files at the go and commit (with push possibility) when ever one so desires.
Pro More modular installer
Visual Studio 2017 supports a much more modern and modular installer. You no longer have to install many gigabytes of stuff you don't need. Everything is broken down into much smaller pieces and it's much more apparent which pieces you need.
Pro Embedded cloud storage
Your Visual Studio Online account gives you a place to store your code, backlog, and other project data with no servers to deploy, configure, or manage.
Pro Friendly UI
Pro Comes with a Windows framework
Pro Easy to use
Pro Simple Library import
Horribly slow on low-end machines due to bulky size, they should modularize it instead of trying to do everything.
Con It's very large
The most basic Visual Studio installation will take up 5GB of disk space.
Con Non native window frame
IDE main window lacks standard window frame (titlebar/borders) - a custom solution is in use where custom titlebar contains numerous application-specific controls. This results in inconsistent UX and can also be problematic when you're using shell replacements or other various window-management software (such as bbLean).
Con Hard to set up
Con Not very feature rich
By default it's not much more than "What if Gedit had a compiler and a terminal built in?" (or: "What if Notepad had colour coding, auto indents, file structure, a compiler and a terminal built in?")
There are far more professional IDEs out there. This one is much too basic for any efficient use.
Con Slow navigation using mouse
In most IDE's, you can "goto declaration"/"implementation" by holding CTRL and left-clicking on an identifier or include directory. This does not work in Code::Blocks no matter what settings you have. Right-clicking will bring-up a menu that includes these "goto" options, but it's not instant and you'll be slowed down immensely depending on how often you have to do it.
Con Can get quite slow and doesn't look all that good
Con Setting up dark theme requires using system's own gui toolkit
Con Lots of functionality is encountered only in plugins
You can't change keyboard shortcuts, neither share themes with vanilla codeblocks, for example.