I've come across a bit of a problem since installing the 2.0 framework.  I
had created a class library using Visual Studio 2003, with one class
configured as a COM object.  The project was configured to launch a simple
Visual Basic 6.0 project which allowed me to create the object and call some
of its methods.

Previously, this worked seamlessly and was highly useful.  However, since
installing framework version 2.0 VB 6.0 is bombing out at the point of
creating the object (closing down, no errors or warnings, Visual Studio 2003
returns to Design mode).  Having dug in a bit further it seems that the
class is being instantiated in a 2.0 domain, which is presumably what is
killing the 2003 debugger.

Is there any way to configure which version of the framework is launched in
this scenario?  I do not believe there would be any particular issues with
the assembly running under 2.0 normally, but clearly if debugging is to work
it will need to run under 1.1 on my development machine.

Thanks,

Nick Hall