D
dotAge
Can I install Client Profile by installing DotNetFx??Client_Package_x86.exe
in turn?
For example:
1) if there isn't any .NetFramework have been installed, then all 3 packages
will be installed:
DotNetFx20Client_Package_x86
DotNetFx30Client_Package_x86
DotNetFx35Client_Package_x86
2) If there is .NetFramework 2.0 have been installed, then I only install
the last 2 packages:
DotNetFx30Client_Package_x86
DotNetFx35Client_Package_x86
3) If there is .NetFramework 3.0 have been installed, then I only install
the last package:
DotNetFx35Client_Package_x86
Because .NetFramework 3.5 client profile setup package is too large, and the
huge package dotnetfx35setup.exe(231M) always be downloaded and installed at
most scenarios by bootstrapper, it is intolerable.
I have tested the scenario 2 by a .Net 3.5 client only program with WCF
technology, it worked, but I am afraid that there will be some potential
risks, who can tell me about this?
Thanks!
in turn?
For example:
1) if there isn't any .NetFramework have been installed, then all 3 packages
will be installed:
DotNetFx20Client_Package_x86
DotNetFx30Client_Package_x86
DotNetFx35Client_Package_x86
2) If there is .NetFramework 2.0 have been installed, then I only install
the last 2 packages:
DotNetFx30Client_Package_x86
DotNetFx35Client_Package_x86
3) If there is .NetFramework 3.0 have been installed, then I only install
the last package:
DotNetFx35Client_Package_x86
Because .NetFramework 3.5 client profile setup package is too large, and the
huge package dotnetfx35setup.exe(231M) always be downloaded and installed at
most scenarios by bootstrapper, it is intolerable.
I have tested the scenario 2 by a .Net 3.5 client only program with WCF
technology, it worked, but I am afraid that there will be some potential
risks, who can tell me about this?
Thanks!