Ok, I see. But I'm not sure why .Net should disallow calling a program portable. I use .Net 2.0 for my apps. This is installed on most all PCs today, and it is part of Windows since Vista.
I think that .NET dependency doesn't keep a program from being portable (unless the program depends on a too recent version; 2.0 is definitely OK in my opinion). However, many TPFC members disagree with me.
Many applications require c++ runtime files too. Are they banned too?
No, because C++ runtime files can be put into the program directory (and are often bundled, as in my game
). That can't be done with .NET.
You have already listed another of my apps, called Hot Spot Studio, with a note that it depends on VB6 runtime files.
How about DirectX "latest version" that you need to install separately?
You are too defensive here.
In some cases, we have decided that a program is simply unique enough to be included regardless of its portability shortcomings. We have an entire category
of .NET programs as well.