I would check to make sure that I had Installed Visual Studio 2008 SP1. Not to be confused with the .Net Framework 3.5 SP1. Greg _____
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Busch Sent: Monday, December 20, 2010 8:43 AM To: [email protected] Subject: [DotNetDevelopment] debugging problem - wrong acccess .NETframework ?? Hi Guys. Hopefully you can help me again this time. I have serious problems with my projects in Visual Studio 2008. Last week I got a new PC with Windows 7 64bit, before I was working with XP 32bit. Visual Studio 2008 and SQL Server 2005 is still the same on both PCs and the project was developed in VS2008. So I copy everything over to the new 64bit PC. No problems. I installed all patches, Service Packs, so the Win7 PC has the latest software on it. I also checked every reference in my project, everything seems to be fine. Compiling my large projects is working, even it is running fine on every 32bit PC (target system for the software is XP embedded 32bit). I tested this multiple times. BUT: I got serious problems if I try to run the compiled software on my Win7 PC or even to debug it in Visual Studio. I think debugging the project while developing is essential and this is not working anymore. This is absolutely not working , neither under "any CPU" nor under "x86" settings. I also checked the framework settings (I am using NetFramwork 2.0 and 3.5). looks ok. While debugging at the beginning it shows the error message. Error message: System.BadImageFormatException occurred Message=Could not load file or assembly 'file:///C:\projects\TRUNK\project1\bin\Debug\startingproject.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. Source=mscorlib FileName=file:///C:\projects\TRUNK\project1\bin\Debug\startingproject.dll FusionLog==== Pre-bind state information === Calling assembly : (Unknown). Same error message if I try to start the application on the W7 PC. I click the exe-file = same error message. If I change the corflags to 32bit+ in the assembly themself and start it then, it is also working on my 64bit System. But (of course) this has no effect on the debug mode of VS. The dependency Walker shows my two missing dlls, which is bogus , cause the dlls doesnt belong to my projects (gpsvc.dll and one from the internet explorer). Why he is showing this files looks like a mysterie. I found severell threads in the internet about this topic. Does anybody have any idea to check which assembly or dependency could be fault for the error? Any suggestions how to check the dependencies or what to take core of in my case changing to work with a 64bit system? Thanks a lot in advance. Michael
