The .NET Framework 4 Installer Improvements
This post has moved here.
Comments
Anonymous
April 15, 2010
I know when I was looking at the file size, I wasn't sure I downloaded the whole thing! Good job :DAnonymous
April 15, 2010
I wrote the same comment on beta 2 post (I'm not sure if you still checking it): I'm also interested in examples (samples) of bootstrapper. I will appreciate if you can share some samples. Did you use Burn as bootstrapper for .NET 4.0? Because I heard that it is not ready yet.Anonymous
April 17, 2010
Greate job peter. Big thumbs up to you guys. For me this is the most important improvement or feature of fx 4.0. Without this i would have to use 2.0 for future development. Part of the world where i work asia, africa (most part or atleast to most people i would say) net connectivity is not great or costly. and people use XP. Users wont have .net fx and i can't ask them to download bloated installer. This created app distribution problem. so i stuck with fx 2.0. Now i can use all the new things since 2.0.Anonymous
April 17, 2010
@Igor, the codebase the we used to ship .NET 4 is part of the foundation of Burn but there are a lot of general use features that a lot of products need (like feature selection and reboot support) that .NET 4 didn't need. So in a way, yes, we used a early version of Burn to ship .NET 4 but the statement that Burn isn't quite ready yet for general use is also correct. Look for it towards Sept/Oct timeframe. Rob Mensching's blog is the place to get the latest release info for Burn.Anonymous
April 17, 2010
If your 2.0 application has v4.0 listed as a supported runtime in its exe.config, then v4 will load it. You can also load 2.0 dll's into v4. Make sure in both these cases you test your application on 4.0 to make sure the 2.0 assets are fully v4 compatible.Anonymous
April 17, 2010
The comment has been removedAnonymous
April 18, 2010
There is a good chance your app will run on 4.0 but if you continue to compile targeting 3.5 you will need to add an supported runtime entry in your exe.config so if it can't find the 3.5 runtime it will load on the 4.0 runtime. If you just want it to run on 4.0 and never 3.5, omit the 2.0 runtime as a supported runtime. The order they are listed below determines what will happen if both are available, the first available runtime is the one that it will be loaded in. Example: <configuration> <startup> <supportedRuntime version="v2.0.50727" /> <supportedRuntime version="v4.0" /> </startup> </configuration>Anonymous
April 18, 2010
"There is a good chance your app will run on 4.0" What are the main reasons that the app working on .Net Framework 2.0 could not work after changing framework to 4.0 ?Anonymous
April 19, 2010
Thank you for your answer! I again feel a hope that I can use Burn, because after last Rob's email I lost my belief, that I will use Burn for "my" installers. I'm still not sure that I will need feature selection and reboot support (because a lot of bootstrappers doesn't support it either). Which version (build) did you use for .net 4.0? Can you please post some examples how to use it, because currently almost zero information is available about it. Thank you in advance!Anonymous
April 19, 2010
@Chris - here is a migration doc that talks about the changes and the recommended fix to properly run on 4.0. http://msdn.microsoft.com/en-us/library/ee941656.aspx Hope this helps... Note: I've migrated a few aps by just using the exe.config to run on .NET 4 and they just worked but that wont be the case for all apps depending on what .NET features they use.Anonymous
April 19, 2010
@Igor - We didn't use a WiX build for our chainer. The codebase that we had for our chainer got merged into burn a few months ago. There isn't a WiX build that you can pick up to get exactly the chainer we used for .NET 4.Anonymous
April 19, 2010
Thank you for clarification. So mainly it won't be the same if I will use Burn from lastest build and most probably Wix Team won't have time to finish all merging till autumn.Anonymous
April 20, 2010
Thats a good way to put it. Even samples right now would be premature because the schema is under development and the build process is also being defined.Anonymous
April 20, 2010
How do you go about deploying .net 4 using group policies? using the msi does not work, errors with use setup.exe to install, it also doesnt allow an admin install.Anonymous
April 21, 2010
Admin installs are documented here: http://msdn.microsoft.com/en-us/library/ee390831.aspx Group policy deployment is not supported.Anonymous
April 25, 2010
Thanks for the link, I had seen that before but was hoping that there was a way to deploy a little more reliably than just scripting, or having to purchace a deployment infrastructure. Looks like I will have to just script it. Are microsoft moving away from one of their own deployment and installations methods (group policy and MSIs)? More and more of their software these days arent fully implemented msis, another example, office 2007 and now 2010, msi implementation and group policy deployment, appauling, recommended deployment method scripting, wow, going back to the good old days. Why on earth did they choose to use an xml file and/or an msp to configure the installtion instead of an mst?Anonymous
April 29, 2010
Make a comment Click here to cancel reply. Login via Newstalk Nation Username: Password: Remember Me Lost Password Sign up to Newstalk Nation Sign up today to comment here and join Newstalk Nation. We'll email you to ask you your views on what matters to you. It might be about elections, schools, sport, economy or what brings a smile to your face. It's your voice, your station, your nation. It's your chance to be heard. Click here to join upAnonymous
July 17, 2010
great info nice to see documented diff: between versions very well set out aswellAnonymous
August 12, 2010
Hello Peter. I installed .NET framework 4 today on my Windows Server 2003 server and I noticed that the installer saved all the setup files to one of my removable disks and left them there under G:�6df43e01594a7d4d1221f960070bf This removable disk will soon be sent to another office and I'm concerned that the setup files path has been recorded in the registry or somewhere else and removing this disk will cause problems for future updates or maintenance. Is there a tool I could use to remove or relocate these files?Anonymous
January 11, 2011
Where is the MSI installer for GPO managed installs?Anonymous
February 07, 2011
Is it possible to make the .Net 4.0 installer not require a reboot after installing?Anonymous
March 03, 2011
why im still getting download fallback of this (KB2160841) although this is a auoto download from windows im getting frustrated of this