VS on Windows

[Look]

Does Visual Studio 2013 Ultimate Update 3 work on Windows 10 Enterprise?

[Look]

Does Visual Studio 2013 Ultimate Update 3 work on Windows 10 Enterprise?

Forgot to add: Both 64bit.

[velmarin]

It works perfect.
But the direct installation of the service pack 5 (the last) will not install directly.
You must first install the original program and then apply the service pack.
Also I have installed Visual Studio 2015 comunity and both work.

[Look]

It works perfect.
But the direct installation of the service pack 5 (the last) will not install directly.
You must first install the original program and then apply the service pack.
Also I have installed Visual Studio 2015 comunity and both work.

Next question:
Will Console/Graphical projects compiled by Visual Studio 2013 Ultimate Update 3 in Windows 10 Enterprise work in Windows 7 Ultimate SP1?

(All 64bit).

[velmarin]

I have not tested yet.

Another tool that works perfect in Visual Studio is the Clang compiler that fits perfect.
http://llvm.org/builds/

[Look]

Next question:
Will Console/Graphical projects compiled by Visual Studio 2013 Ultimate Update 3 in Windows 10 Enterprise work in Windows 7 Ultimate SP1?

(All 64bit).

This seems to be called "binary compatibility".

[jdart]

You can't assume either backwards or forwards compatibility. Microsoft adds function calls, so newer builds may not work on old OSs. And they have even been known to alter the behavior of existing function calls, so old code may not execute on newer systems. Mostly it is ok. But you need to test.

--Jon

[Look]

You can't assume either backwards or forwards compatibility. Microsoft adds function calls, so newer builds may not work on old OSs. And they have even been known to alter the behavior of existing function calls, so old code may not execute on newer systems. Mostly it is ok. But you need to test.

--Jon

Is that exclusive to Windows specific code, or it happens to standard C/C++ code too?

[Joost Buijs]

You can't assume either backwards or forwards compatibility. Microsoft adds function calls, so newer builds may not work on old OSs. And they have even been known to alter the behavior of existing function calls, so old code may not execute on newer systems. Mostly it is ok. But you need to test.

--Jon

Is that exclusive to Windows specific code, or it happens to standard C/C++ code too?

You can specify in your source which Windows version you want to target.

#define WINVER xxx
#define _WIN32_WINNT xxx

By defining these the proper library code will get selected for Windows specific code.