A
Andy Fish
Hi,
I have a .Net application and I want to upgrade it from .Net 2.0 to
3.5, but I am only using a tiny selection of the 3.5 features.
From what I understand, 3.5 consists of basically the same framework/
CLR as 2.0 but with additional DLLs
Is it possible from (a) a technical perspective and (b) a legal
perspective to simply ship the additional .net 3.5 assemblies I need
in my application's bin directory and leave the user on .Net 2.0,
rather than forcing each user to download 200mb of .Net
redistributable before they can upgrade?
My application has both client and server parts. I don't mind about
having to upgrade the servers, but having to install .Net 3.5 on each
client workstation would be a PITA
Andy
I have a .Net application and I want to upgrade it from .Net 2.0 to
3.5, but I am only using a tiny selection of the 3.5 features.
From what I understand, 3.5 consists of basically the same framework/
CLR as 2.0 but with additional DLLs
Is it possible from (a) a technical perspective and (b) a legal
perspective to simply ship the additional .net 3.5 assemblies I need
in my application's bin directory and leave the user on .Net 2.0,
rather than forcing each user to download 200mb of .Net
redistributable before they can upgrade?
My application has both client and server parts. I don't mind about
having to upgrade the servers, but having to install .Net 3.5 on each
client workstation would be a PITA
Andy