Aug 1, 2015 03:22 AM
(This post was last modified: Aug 1, 2015 04:00 AM by YunoLawliet.)
Since the release of newer versions of windows,
It's default .NET Framework is v4.0/4.5 (Windows 8 and newer).
Your .NET 2.0 pre-existing apps won't work directly with v4.0/4.5 you must specify the runtime version needed in order for it to work.
In a freshly installed Win10, a .NET 2.0 app will prompt an install of .NET 3.5 framework :
Spoiler (Click to View)
The install is redundant, if your .NET apps doesn't contain obsolete attributes (which probably mostly not) the chances are, it will work on .NET 4+
(See the links below for obsolete attributes)
In order for .NET 2.0 apps to work in .NET 4+ FW, we must export or make an app.exe.config file with the executable we are using.
Example:
My application is called "BytePump.exe"
In order for it to work in .NET v4.0+, I need to make a file called : "BytePump.exe.config".
You can make an app.config file using notepad and pasting this code :
And then save it as AppName.exe.config (change AppName to your executable's name, in this case, BytePump)
![[Image: Capture.PNG]](https://dl.dropboxusercontent.com/s/3r6wklkdxac332h/Capture.PNG)
The app and the .config file must always be in package in order to maximize its compatibility.
You can just ZIP it with the exe, or use RAR as is it better (as it exports all of its content in temp).
And always remember that you must never upload your .exe solely as .exe you must always .zip .rar them whether they are native or .NET.
(spreading is a different thing tho, this focuses on more legal norm.).
For the noobs' sake here's an example :
https://dl.dropboxusercontent.com/s/7np1...xample.rar
VT Scan : https://www.virustotal.com/en/file/06b11.../analysis/
Spoiler (Click to View)
References:
https://msdn.microsoft.com/en-us/library...10%29.aspx
https://msdn.microsoft.com/en-us/library...s.85).aspx
https://msdn.microsoft.com/en-us/library....110).aspx
It's default .NET Framework is v4.0/4.5 (Windows 8 and newer).
Your .NET 2.0 pre-existing apps won't work directly with v4.0/4.5 you must specify the runtime version needed in order for it to work.
In a freshly installed Win10, a .NET 2.0 app will prompt an install of .NET 3.5 framework :
Spoiler (Click to View)
The install is redundant, if your .NET apps doesn't contain obsolete attributes (which probably mostly not) the chances are, it will work on .NET 4+
(See the links below for obsolete attributes)
In order for .NET 2.0 apps to work in .NET 4+ FW, we must export or make an app.exe.config file with the executable we are using.
Example:
My application is called "BytePump.exe"
In order for it to work in .NET v4.0+, I need to make a file called : "BytePump.exe.config".
You can make an app.config file using notepad and pasting this code :
Code
<configuration>
<startup>
<supportedRuntime version="v2.0.50727"/>
<supportedRuntime version="v4.0" />
</startup>
</configuration>And then save it as AppName.exe.config (change AppName to your executable's name, in this case, BytePump)
The app and the .config file must always be in package in order to maximize its compatibility.
You can just ZIP it with the exe, or use RAR as is it better (as it exports all of its content in temp).
And always remember that you must never upload your .exe solely as .exe you must always .zip .rar them whether they are native or .NET.
(spreading is a different thing tho, this focuses on more legal norm.).
For the noobs' sake here's an example :
https://dl.dropboxusercontent.com/s/7np1...xample.rar
VT Scan : https://www.virustotal.com/en/file/06b11.../analysis/
Spoiler (Click to View)
References:
https://msdn.microsoft.com/en-us/library...10%29.aspx
https://msdn.microsoft.com/en-us/library...s.85).aspx
https://msdn.microsoft.com/en-us/library....110).aspx


![[Image: IC556828.png]](https://i-msdn.sec.s-msft.com/dynimg/IC556828.png)


![[Image: 1zL3pDG.jpg]](https://i.imgur.com/1zL3pDG.jpg)