St_W wrote:That's true, but it's not hard to make your .NET application compatible with both 2.0-3.5 and 4.0 runtimes - especially if it's such a simple application like the one request by the thread's author.
Source compatible, or generate compatible .EXE's ?
And features also differ between different versions of the Win32-API or other APIs.
Much less, it is possible to craft highly compatible EXEs. More importantly, by dynloading winapi dlls one can actually load the few differences dynamically, increasing compatibility.
Currently we support XP+ without much trouble, and XP is not even supported anymore (came with .NET 1.x originally)