.exe No debugger found

[bwalke]

I developed and windows application with Visual Studio.NET on my local
development machine. When I go to deploy this application on other
machines the application will not execute. The following error occurs:

..exe Common Language Runtime Debugging Services
Application has generated an exeception that could not be handled.
Process id=0xf1c (3868), Thread id=0xca0 (3232).

..exe No debugger found.
Registered JIT debugger is not available.

cordbg.exe !a 0xf1c

It appears that is application works on machines with VS.Net installed
on them. However, on the deployment machine I have all the .net dll's
and other files as that on the development machine. The references in
the project are pointed in the right and same locations for the
development and deployment machines.

Has anyone else run into this issue. Any help or direction would be
great!

Thanks,

Brett

 

[bwalke]

Also, .net framework files 1.1 and 1.0 files are on the deployment
machine.

 

[Nick Malik [Microsoft]]

I'm going to completely guess, with no reason to believe that this may
help...

Do you have assert calls in your code and you are deploying a debug version
of your app? If so, when the assert is hit, .Net will look for the
debugger.

Hope this helps,

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.

 

[bwalke]

I have tried deploying both a debug version and also the release
version of the project. Also, I am not quite sure what a assert call
is and were to use it. It appears that the program is looking for a
debugger and if Visual Studio.Net is not installed on the deployment
machine than the error stated above is thrown. The error appears even
before the windows form loads. Is there any way the application can be
deployed without debugging it, or are there extra files or dll's I my
be missing.

Brett

 

[Guest]

download the
http://www.microsoft.com/downloads/...a6-3647-4070-9f41-a333c6b9181d&displaylang=en

and debug your application using the cordbg.exe
You will see what actually causing the problem in the command prompt.

raj