<< DotNetNuke function FindControlRecursive -not clear name. | Home | Using Web Application Project(WAP) for development of DotNetNuke modules with Edit and Continue Support >>

Setup of new version using .Net 2.0 causes System.BadImageFormatException

I had a .Net 1.1 application with Setup project and RemovePreviousVersions=true.

After I converted it to .Net 2.0, I've tried to install it on machine where previous version was installed.

It caused System.BadImageFormatException exception. I believe that new .Net 2.0 Setup failed to uninstall .Net 1.1 application due to .Net framework versions mismatch.

I've desided to change UpgradeCode, that will be considered as new application, and it allowed me to install new version.

Alternatively user can manually uninstall previous version prior to install new one(not tested yet).
I've reported the issue toMicrosoft.

  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
posted @ Monday, April 10, 2006 8:12 AM
Print

Comments on this entry:

# It's only partly due to different .NET Framework versions

Left by Bob Quinn at 12/28/2006 5:07 AM
Gravatar
Microsoft support reported this problem 2-1/2 years ago with Visual Studio and there is still no fix - even though they updated Visual Studio to 2005! Apparently, if an upgrade setup has custom actions, the calls are made to the PREVIOUS version of the product already installed rather than the NEW upgrade version! So, in this case, what's happening is that your 2.0 .NET Framework upgrade setup is trying to make a call to the previous earlier .NET Framework version, expecting a 2.0 .NET Framework assembly but finding that it isn't 2.0!

Your comment:



(not displayed)


 
 
 
 
 

Live Comment Preview:

 
«February»
SunMonTueWedThuFriSat
2930311234
567891011
12131415161718
19202122232425
26272829123
45678910

About
Article Categories
Archives
Post Categories
Links
Syndication:

RSS ATOM