Thanks Craig!! I have another question about this, if you don't mind.

Even though the Framework may be 3.5, and even though I may be using VS2008, does everything still compile to the 2.0 CLR? I should know this I suppose, but I just want to be sure.

We use a distributed scenario, in that the user's workstation has only an EXE and two supporting DLLs. The rest of the DLLs are downloaded from the server as needed (using Reflection).

When we do upgrades, we typically do not touch the workstations. That EXE and those two DLLs are designed to never have to be changed (hopefully never ). They've been compiled using VS2005.

So, here's the hypothetical situation: now, we're coming out with some new stuff and we want to switch to VS2008 and maybe take advantage of some of the new stuff. We won't be putting any of that new stuff into that small EXE and the two DLLs, but they will obviously have been part of the solution that gets ported to VS2008.

As long as the user's workstation has the 3.5 Framework, we should still be able to leave it untouched, still run the old EXE and those two supporting DLLs (all still having been compiled under VS2005), and have the newer DLLs still automatically download from the server, even though all those new DLLs have been compiled under VS2008 ... and everything will still run ok. Right or wrong?

~~Bonnie