.NET - The .NET Framework 4.0 Client Profile installation is SLOW. What are my options for a workaround?
I just built a little baby console app for deployment on 3 or 4 laptops. I didn't think too hard about deployment when building it. Anyway, I've deployed it on 3 machines, and it runs fine, but the .NET 4.0 Framework Client Profile installation is SLOW. The framework takes a good 3 to 5 minutes to install while my little app takes about 3 seconds. Are there any good developer strategies to get around this?
Code for .NET 3.0?
Do it some other way?
Code for .NET 3.0?
Do it some other way?
Nasir Razzaq
If you are not using 4 specific features then using 3.5 is a good option because most computers have 3.5 installed (default in win 7 and included in service packs on other versions).
How much time does it take to install any version of Windows?
How much time does it take to install any version of the framework?
If you see the framework as the operating system (and basically it is almost what it is), then you will find that 3 to 5 minutes without user intervention is a wonderful evolution.
How much time does it take to install any version of the framework?
If you see the framework as the operating system (and basically it is almost what it is), then you will find that 3 to 5 minutes without user intervention is a wonderful evolution.
For Windows installation, allow at least 30 minutes on a PC or server with a multi-core processor.
For Framework installation, it should take less than 5 minutes for offline installation but can take longer if you're installing through Windows Update.
For Framework installation, it should take less than 5 minutes for offline installation but can take longer if you're installing through Windows Update.
ASKER
Thanks guys,
Follow-up question: Does Microsoft have a time-table for pushing .NET Framework 4.0 in XP, Vista, and W7 service packs?
Follow-up question: Does Microsoft have a time-table for pushing .NET Framework 4.0 in XP, Vista, and W7 service packs?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Simply a question of semantic on "pushed".
I do not see something that is installed with the OS as being pushed.
I do not see something that is installed with the OS as being pushed.
So a .Net app will only work if the framework was Pushed to the OS rather than being part of OS?
Installing the OS installs the version of the framework that is current at the time the OS is installed. For me, this is installing the framework, not pushing it.
Pushing, for me, would be that an update to the OS (through Windows Update), would force a new version of the framework to be installed. This never happened in the 10 years or so that the framework has been officially on the market. You will be offered patches and service packs for an already existing version of the framework, but Windows Update, in my experience, will never "push" on the user computer a newer version of the framework that what has been previously installed.
A .Net application that needs a specific version should define it as a prerequisite for the application, or set it installation program so that it makes the check and install the proper version if needed.
Pushing, for me, would be that an update to the OS (through Windows Update), would force a new version of the framework to be installed. This never happened in the 10 years or so that the framework has been officially on the market. You will be offered patches and service packs for an already existing version of the framework, but Windows Update, in my experience, will never "push" on the user computer a newer version of the framework that what has been previously installed.
A .Net application that needs a specific version should define it as a prerequisite for the application, or set it installation program so that it makes the check and install the proper version if needed.
ASKER
Great feedback. Thanks guys. (I think your disagreement was purely semantics.)