This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: BadImageFormatException
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 24, 2013
08:35 AM
BadImageFormatException
Hello Folks,
I've run into a strange problem with this error where we are only seeing it on windows XP systems. I have checked the .Net Framework File locations on the build machine and it is pointing to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 and C:\Windows\Microsoft.NET\Framework64\v2.0.50727 respectively. When we install our product on OS's greater then Vista we have no issues. When we go to install it on a Windows XP system it appears to be trying to use .Net Framework 1.1 rather then 2.0, I have seen in the isconfig.xml for the component on the target machine it actually contains both .net versions not just the 2.0.50727 version. Does anyone know what would provoke this behavior or how to stop it from happening?
I've run into a strange problem with this error where we are only seeing it on windows XP systems. I have checked the .Net Framework File locations on the build machine and it is pointing to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 and C:\Windows\Microsoft.NET\Framework64\v2.0.50727 respectively. When we install our product on OS's greater then Vista we have no issues. When we go to install it on a Windows XP system it appears to be trying to use .Net Framework 1.1 rather then 2.0, I have seen in the isconfig.xml for the component on the target machine it actually contains both .net versions not just the 2.0.50727 version. Does anyone know what would provoke this behavior or how to stop it from happening?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 29, 2013
09:43 AM
Turns out this was due to the _isconfig.xml having both supported version elements in it. Even though the .net framework version was selected to be 2.0 because the _isconfig.xml contained v1.0 it was still trying to use that.