G
Guest
Situation:
I've been using VS .NET 2003 to develop apps w no problems. So, today, my
manager had me install VS 2005 (& with it the .NET 2.0 framework) so now my
machine has VS .NET 2003 (.NET Framework 1.1) and VS 2005 (.NET Framework
2.0).
Issue:
A program that I developed in VS .NET 2003 now gets a run time exception
when executing the program outside the VS 2003 development environment (when
I execute the program through VS 2003 the problem doesn't appear). Anyway,
title bar on the error dialog box says "<my exe name> - Common Language
Runtime Debugging Services". The message body has a message stating that the
app generated an exception that could not be handled, gives the PID and
thread ID, and options OK and CANCEL (enter DEBUG). When I attempt to CANEL
(enter DEBUG), I get another error message stating that the parameters are
incorrect and the DEBUGGER failed to start.
The error message able leads me to believe that there may be some conflict
between versions 1.1 and 2.0 of the .NET Framework. If anyone has knowledge
of such conflicts and/or any proposed workarounds I'd be grateful to hear
your ideas.
Thanks for your attention to this...
Charles
I've been using VS .NET 2003 to develop apps w no problems. So, today, my
manager had me install VS 2005 (& with it the .NET 2.0 framework) so now my
machine has VS .NET 2003 (.NET Framework 1.1) and VS 2005 (.NET Framework
2.0).
Issue:
A program that I developed in VS .NET 2003 now gets a run time exception
when executing the program outside the VS 2003 development environment (when
I execute the program through VS 2003 the problem doesn't appear). Anyway,
title bar on the error dialog box says "<my exe name> - Common Language
Runtime Debugging Services". The message body has a message stating that the
app generated an exception that could not be handled, gives the PID and
thread ID, and options OK and CANCEL (enter DEBUG). When I attempt to CANEL
(enter DEBUG), I get another error message stating that the parameters are
incorrect and the DEBUGGER failed to start.
The error message able leads me to believe that there may be some conflict
between versions 1.1 and 2.0 of the .NET Framework. If anyone has knowledge
of such conflicts and/or any proposed workarounds I'd be grateful to hear
your ideas.
Thanks for your attention to this...
Charles