Since Code :: Blocks is your preference, and you want to use remote debugging, and you have experience working with the VC compiler, that way may be the easiest and smoothest solution. As suggested by @ user1610015, upgrade to VS2015 Community Edition , which certainly contains a standalone compiler (cl) and linker (link) . Of course, the CL will call the linker on your behalf, unless you specify otherwise .
Here is a comparison chart (select "expand all") of VS releases.
As a bonus, you will receive amazing updates compared to modern C ++ (11 and 14), the best remote debugging, the best generation of code, countless optimizations, improved reports and error analysis and others.
However, with respect to __ asm (on VS2013), you will be limited to x86 . When x64 is required, some choose to port this to intrinics , but many simply transfer the assembler to a separate .asm and a slight configuration change so that VS compiles the file:
- Select a project (not. Sln)
- From the menu, choose Project → Build Custizations ...
- Check the box next to masm
If you intend to target x86 , no changes will be required. You did not specify a migration change with reference to VS2008, but, transferring a few large old projects from earlier VS compilers, I found that this experience would be pretty painless.
If your compiler code is not overwhelming, consider Clang and gcc (MinGW). I like to use CLion and use gcc to compile the same projects (CMake) for which I have a project and VS2015 solution. Sometimes I am surprised by some necessary corrections. I have not tried Code :: Blocks , but I suspect this is a similar exercise.
Good luck. I am sure you will crush him.