1,105,594 Community Members

Visual Studio 2005 and 64 bit OS/Processor

Member Avatar
GaidinDaishan
Newbie Poster
3 posts since Apr 2011
Reputation Points: 0 [?]
Q&As Helped to Solve: 0 [?]
Skill Endorsements: 0 [?]
 
0
 

I am just starting MS Visual Studio 2005. My laptop has a 64 bit Intel microprocessor and the OS installed is 64 bit Windows 7. I created a DLL in VC++ 2005 using a Export Definitions File (.def) and then created an application on VB to test it.

The entire procedure was completed as instructed by my teacher and every thing was fine until I tried to run the application. The error returned was a BadImageFormat Exception (0x8007000B) and I have completely no idea what went wrong.

I have read the posts in these forums and I think it might be that VC++ 2005 creates a 32 bit (x86) version of DLL. Also I tried changing the format so that it produces a 64 bit (x64) version of DLL but it returned a different error on compilation. The machine module and the target module were incompatible.

Please help. I'm running out of time on this project.

Member Avatar
Ancient Dragon
Achieved Level 70
27,645 posts since Aug 2005
Reputation Points: 5,232 [?]
Q&As Helped to Solve: 3,038 [?]
Skill Endorsements: 115 [?]
Team Colleague
Featured
Sponsor
 
0
 

Yes, it is true that the compiler produces 32-bit code, but that should not have been the problem. I also have 64-bit Windows 7 and never have a problem using 32-bit DLLs.

What version of VB are you tring to use?

Member Avatar
GaidinDaishan
Newbie Poster
3 posts since Apr 2011
Reputation Points: 0 [?]
Q&As Helped to Solve: 0 [?]
Skill Endorsements: 0 [?]
 
0
 

What version of VB are you tring to use?

I'm using the Visual Studio 2005 developer itself. I've also tried using Visual Basic 6 under Visual Studio 98 but it hangs in the middle due to an incompatibility problem.

Member Avatar
Ancient Dragon
Achieved Level 70
27,645 posts since Aug 2005
Reputation Points: 5,232 [?]
Q&As Helped to Solve: 3,038 [?]
Skill Endorsements: 115 [?]
Team Colleague
Featured
Sponsor
 
1
 

Visual Studio 98??? That is almost as ancient as I am. Upgrade your version of VB to a more recent one. Start out with the free VB 2010 Express to see if that resolves your problem or not.

You
This article has been dead for over three months: Start a new discussion instead
Post:
Start New Discussion
View similar articles that have also been tagged: