Unable to run my debug code on my Windows7 Professional machine

Question

0.00/5 (No votes)

See more:

Hi there,

i am facing a problem since i have changed my OS to windows 7 professional.
i am able to run my release code exe but i am unable to run my Debug code exe.
When i try to debug my application in Visual studio it gives the following error.

An unhandled exception of type 'System.IO.FileLoadException' occurred in Unknown Module.

Additional information: Could not load file or assembly 'Windowmaker.Interop.WMD.dll' or one of its dependencies. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)

i tried every possible thing but am unable to resolve this problem.
The dll that it says it cant load is present in the code and i checked all its dependencies they are also present.
i have complete .Net4.0 installed.
i did search on google as well but did not fnd any satisfactory answer.
Please help..

Posted 29-Apr-12 20:51pm

Saurabh.abhyankar

Updated 29-Apr-12 21:00pm

Mehdi Gholam

v2

Add a Solution

Comments

Lakamraju Raghuram 30-Apr-12 2:56am

Are you using any mangged C++ dlls in your solution ?

Code-o-mat 30-Apr-12 4:36am

Can it be that the DLL or any of its dependencies have an "incorrect" path "wired into" the code? I mean, e.g. it tries to load that DLL from "c:\windows\system32\" while in win7 it is now located under "c:\windows\system32\interop\" (the paths io just made up). So you see the DLL's are present they are just not where your app looks for them?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Saurabh.abhyankar · Accepted Answer · 2012-04-30T01:05:00

Solution 1

Solved the problem. Actually one of my dll's was refering to VC90 instead of VC100 as it should do for new Visual studio 2010. i deleted and recomplied this dll. Now its working fine. thanks for the support.

Posted 30-Apr-12 1:05am

Saurabh.abhyankar

Comments

Albert Holguin 1-May-12 11:01am

Thanks for posting your solution... although some may frown on posting solutions to your own questions... some of us think it's a great idea since it might help anyone else with the same problem down the road.

Saurabh.abhyankar 3-May-12 0:27am

Yup thats the reason why i posted the answer here.. coz i myself did search on the net .. i found such kind of Questions but no answers to it.. The reason might be that people themselves had solved the problem but no one posted thier ans back.. :)