Impact on clients migrating from the .NET framework 2.0 to 3.5

We have a desktop application running on several thousand client computers. We want to move from the framework 2.0 to 3.5, but we are talking about the impact on customers. I understand that 3.0 and 3.5 are additions to the structure and install service packs up to 2.0; What I want to know specifically:

  • When a client updates to the latest version (forced update) and they only have a 2.0 or 3.0 frame, will Windows go and grab 3.5 invisibly in the background?
  • If not, can we make this part of the installer or is it available only through Windows Update? ( Edit : we use MSI.)
  • If there is no way to make the process invisible to the user, is there a website that provides step-by-step instructions?
  • If the client is in a box where they do not have permission to update the framework, is there anything that can be done to keep the application working correctly?
+3
source share
6 answers

If you use the MSI installer for your application, it will try to install 3.5 for them.

If you are not using MSI, tell them to go here: http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en

Then download and install.

If they do not have administrator access, they need it.

+1

, .NET 3.5 SP1. Windows .NET 2.0 3.5. , - . , , - .

.

+2

, . OneClick, , .

, , .

+1

1) .

2) .

4) IMO .

.Net 3.5 Client Profile .

.Net 3.5.dll .

: .Net 3.5 Client Profile . 2,8 . .

+1

, , , , :

+1
  • ? , .net 3.5 . . , Zenworks , "" .

  • , .net 2.0?

  • .., , , , , , . , , , "" C $ , "" login- script.

. , .

0

Source: https://habr.com/ru/post/1724781/


All Articles