2005 project conflicting with 2003

[Jack Russell]

I have a project developed under VS2005 on one PC. If I move the exe
file and dlls to another PC which has VS2003 installed plus framework 2
When I try to run the exe (by clicking on the exe) it asks me which 2003
debugger I want to use. Whatever answer I give it does not work!
I built the exe as a "release". Can someone tell me what I am doing wrong.

[Spam Catcher]

Jack Russell <ja***@norubbish.tpg.com.auwrote in
news:#N**************@TK2MSFTNGP06.phx.gbl:

I have a project developed under VS2005 on one PC. If I move the exe
file and dlls to another PC which has VS2003 installed plus framework
2 When I try to run the exe (by clicking on the exe) it asks me which
2003 debugger I want to use. Whatever answer I give it does not work!
I built the exe as a "release". Can someone tell me what I am doing
wrong.

Release DLLs don't have debugging symbols, so debugging a release binary
will fail.

[Jack Russell]

Spam Catcher wrote:

Jack Russell <ja***@norubbish.tpg.com.auwrote in
news:#N**************@TK2MSFTNGP06.phx.gbl:

>>I have a project developed under VS2005 on one PC. If I move the exe
file and dlls to another PC which has VS2003 installed plus framework
2 When I try to run the exe (by clicking on the exe) it asks me which
2003 debugger I want to use. Whatever answer I give it does not work!
I built the exe as a "release". Can someone tell me what I am doing
wrong.

Release DLLs don't have debugging symbols, so debugging a release binary
will fail.

Sorry, can you expand that. I am not trying to debug, I just want to run it.

[Jack Russell]

Jack Russell wrote:

Spam Catcher wrote:

>Jack Russell <ja***@norubbish.tpg.com.auwrote in
news:#N**************@TK2MSFTNGP06.phx.gbl:

>>I have a project developed under VS2005 on one PC. If I move the exe
file and dlls to another PC which has VS2003 installed plus framework
2 When I try to run the exe (by clicking on the exe) it asks me which
2003 debugger I want to use. Whatever answer I give it does not work!
I built the exe as a "release". Can someone tell me what I am doing
wrong.

Release DLLs don't have debugging symbols, so debugging a release
binary will fail.

Sorry, can you expand that. I am not trying to debug, I just want to run
it.

Its Ok I had not copied all the dlls over. Surely .net could tell you
that was the problem as it does if the framework is not present!

[Spam Catcher]

Jack Russell <ja***@norubbish.tpg.com.auwrote in
news:Oo**************@TK2MSFTNGP02.phx.gbl:

>Sorry, can you expand that. I am not trying to debug, I just want to
run it.

Its Ok I had not copied all the dlls over. Surely .net could tell you
that was the problem as it does if the framework is not present!

..NET probably did:

I have a project developed under VS2005 on one PC. If I move the exe
file and dlls to another PC which has VS2003 installed plus framework
2 When I try to run the exe (by clicking on the exe) it asks me which
2003 debugger I want to use. <---------

If you cancelled the debugger request, a crash message with the stack trace
would have shown up.

However, you tried to debug a release DLL with no debug symbols nothing was
debugged (probably only hex code). Are you familiar with the difference
between release and debug binaries? I can't find a good link explaining the
difference bug suffice to say debug builds contain information required for
debugging while release builds do not. Release builds also run faster than
debug builds :-)