I was getting these errors while running our application on Win2K3 64-bit. The reason behind that is we added a new function and it was asking for .Net Framework. After installing .Net framework, the error got resolved. But since many of QA team dont have .Net framework installed on their machines, we dont want them to install it. Instead if framework is not installed, is there any way to skip the execution of that newly added function which requires .Net framework and continue with execution of the rest of application? And if .Net framework is installed, the new function will be executed.
The newer .Net versions are not simply a superset of the old ones, therefore an app built for a newer .Net platform will not run on an older version. The potential solution is to actually build 2 versions of the library containing the function in question (one for the current .Net runtime and one against the older one) then decide at runtime - you can check the registry for the installed version - which library to use.
Marked as answer bySangram PawarTuesday, October 25, 2011 3:40 PM
Friday, October 31, 2008 12:20 AM
Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.