Mixing 1.1 and 2.0?

[Brett Romero]

I'm slowly making the move to 2.0. I have a solution in 1.1 with two
projects - EXE and DLL. I'd like to upgrade the EXE (user interface of
this solution) to 2.0 and leave the DLL at 1.1 for the time. How will
that work?

In other words, I suppose the solution needs to be either 1.1 or 2.0?
Does that mean I basically have to put these two projects in their own
solution and their respective IDEs (VS.NET 2003 for DLL and 2005 for
EXE)?

If the 2.0 EXE project file references the 1.1 DLL, will I still be
able to "step into" the DLL's methods while debugging the 2.0 EXE in
2005 and vice versa?

Thanks,
Brett

 

[John Sun]

I'm slowly making the move to 2.0. I have a solution in 1.1 with two
projects - EXE and DLL. I'd like to upgrade the EXE (user interface of
this solution) to 2.0 and leave the DLL at 1.1 for the time. How will
that work?

[I think that work , because one key point of .Net is it will be able to
run side by side].

In other words, I suppose the solution needs to be either 1.1 or 2.0?
Does that mean I basically have to put these two projects in their own
solution and their respective IDEs (VS.NET 2003 for DLL and 2005 for
EXE)?

[I think so, you have to develop it in different IDES].

If the 2.0 EXE project file references the 1.1 DLL, will I still be
able to "step into" the DLL's methods while debugging the 2.0 EXE in
2005 and vice versa?

[Not sure, but I will try it out].