At my day time job I decided we should try out Visual Studio 2015 (from Visual Studio 2013).
Here are my experiences from it.
The installation is easy. Just log in to MSDN and download the VS2015 installer (or ISO-image). When doing C++ work, make sure to install the C++ compiler and toolset.
Just remember to select the C++ toolchain. The toolchain for Windows XP is optional and probably not needed.
Some of the removed (and deprecated methods) in the C++11 standard is completely removed from Visual C++ 2015. One of those is
gets. This is a very good thing.
// Deprecated and dangerous char instring; gets(instring); // Replacement, completely safe std::string instr; std::cin >> instr;
When using a .NET C++ DLL in a .NET C# project, this error may occur.
<br /> 1>C:Program Files (x86)/MSBuild/14.0/bin/Microsoft.Common.CurrentVersion.targets(1819,5): warning MSB3274: The primary reference nnn could not be resolved because it was built against the ".NETFramework,Version=v4.5.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.5".<br />
Bump the .NET project up to framework version
It’s been moved from Property pages to a References filter/folder along with the files in the project, just like it’s with C# projects.
main.obj : error LNK2019: unresolved external symbol "void __cdecl libraryMethod(void)" (?libraryMethod@@YAXXZ) referenced in function _main
Right click on references to add a new reference project.
Select the dependent project.
It will not link.
The error list is very confusing. It doesn’t always clear the errors and it’s not possible to sort by error order (as they appear in the output window). As it appears now it’s next to useless. I expect Microsoft will fix this very soon.
The highlighted item is actually the first error coming from the Header.h file.