PDA

Click to See Complete Forum and Search --> : .NET Framework version compatibility

ajbharani
February 17th, 2009, 08:34 AM
I have an application (exe) file created in .Net framework 2.0.5238. In my machine I have the following versions installed

Microsoft .NET Framework 1.1 1.1.4322
Microsoft .NET Framework 2.0 Service Pack 1 2.1.21022
Microsoft .NET Framework 3.0 Service Pack 1 3.1.21022
Microsoft .NET Framework 3.5 3.5.21022
Microsoft .NET Framework 3.5

When I execute that application, it crashes at some point. How can I resolve this issue? I cannot remove the existing framework since some other dependent applications are running. Neither can I install 2.0 because of this (http://support.microsoft.com/KB/906894)

Thanks.
Shuja Ali
February 17th, 2009, 12:35 PM
When it crashes, what message does it show? Maybe framework is not an issue, maybe there is something else that is causing the application to crash.
ajbharani
February 17th, 2009, 10:23 PM
I have attached the crash info. Also, the application runs perfectly in some machines.
Shuja Ali
February 18th, 2009, 01:05 AM
Well look slike something is wrong with OsInfo.dll file. You may want to check what version of file is installed on the system that is giving the problem and the ones that don't.
ajbharani
February 18th, 2009, 01:12 AM
Yes, I noticed that in the crash information. Actually it is a dll along the application. But the same application with the same dll runs fine in some other machines. The application not only crashes in my machine. Also in some other machines.
Shuja Ali
February 18th, 2009, 01:39 AM
I am very much sure that the problem is not with the framework versions. It may be something else that is causing the application to crash.
ajbharani
February 18th, 2009, 02:09 AM
OK. Let me analyze on this. Thanks!
boudino
February 18th, 2009, 02:14 AM
OsInfo.dll is not part of .NET framework, so the cause is not in it. I also think that the bad is somewhere else, most probably the OsInfo.dll rely on other component, which is not installed, or corrupted. What about try to use Dependency Walker (depends.exe) to check out what does the OsInfo.dll require?

Also, there may be a bug in class constructor, e.g. attempt to write to forbiden path. Such a kind of errors is hard to recognize, because they are "consumed" by class loader and are propagated strange.