Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

October, 2011

  • Aaron Stebner's WebLog

    Mailbag: Do I need still need older versions of the .NET Framework on my system after installing the .NET Framework 4?

    • 20 Comments

    Note: This is an updated version of a previous mailbag entry that I posted before the .NET Framework 4 shipped.

    Question:

    I recently installed the .NET Framework 4 on my system. Afterwards, I looked in Add/Remove Programs, and it shows that I have all of the following versions of the .NET Framework installed on my system:

    • Microsoft .NET Framework 1.1
    • Microsoft .NET Framework 2.0 SP2
    • Microsoft .NET Framework 3.0 SP2
    • Microsoft .NET Framework 3.5 SP1
    • Microsoft .NET Framework 4 Client Profile
    • Microsoft .NET Framework 4 Extended

    Do I need any of these older versions of the .NET Framework now that I’ve installed the .NET Framework 4, or can I safely uninstall them?

    Answer:

    In general, my recommendation is to leave the .NET Framework 2.0 SP2, 3.0 SP2, 3.5 SP1 and 4 installed on your computer.

    Unlike previous versions of the .NET Framework, the .NET Framework 4 does not allow an application that was built with previous versions of the .NET Framework to migrate forward and run on it if the previous version is not installed. If you are using any applications that were built with any version of the .NET Framework before version 4, then I recommend leaving both the .NET Framework 3.5 SP1 and the .NET Framework 4 installed.

    You cannot use the .NET Framework 3.5 SP1 unless you also have the .NET Framework 2.0 SP2 and 3.0 SP2 installed. Therefore, you will not be allowed to uninstall the .NET Framework 2.0 SP2 or 3.0 SP2 if you have the .NET Framework 3.5 SP1 installed. If you try to uninstall the .NET Framework 2.0 or 3.0 when the .NET Framework 3.5 is installed, their uninstall processes will block and tell you that they are needed by another application on your system.

    The .NET Framework 1.0 and .NET Framework 1.1 can be installed side-by-side with the .NET Framework 2.0, 3.0, 3.5 and 4. Most applications that were created for the .NET Framework 1.0 or 1.1 will automatically use the .NET Framework 2.0 instead if it is installed on the system. In most cases, that means you do not need to keep the .NET Framework 1.0 or 1.1 installed on your system if you already have the .NET Framework 2.0 installed.

    However, there are some applications that are configured to require a specific version of the .NET Framework, even if later versions of the .NET Framework are installed. If you have any applications like that on your system and try to run them without installing the .NET Framework 1.0 or 1.1, you will get an error message that looks like the following:

    ---------------------------
    MyApplication.exe - .NET Framework Initialization Error
    ---------------------------
    To run this application, you first must install one of the following versions of the .NET Framework:
    v1.1.4322
    Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework.
    ---------------------------
    OK
    ---------------------------

    In the above error message, the version number will be v1.0.3705 if you need to install the .NET Framework 1.0, and it will be v1.1.4322 if you need to install the .NET Framework 1.1.

    If you end up seeing any error messages like this, you can re-install the .NET Framework 1.0 or 1.1 in order to resolve the errors. If you don't end up seeing any error messages like this, then you don't need to worry about re-installing the .NET Framework 1.0 or 1.1.

  • Aaron Stebner's WebLog

    Direct download links for the XNA Game Studio 4.0 Refresh and XNA Framework Redistributable 4.0 Refresh

    • 1 Comments

    Last week, we released the final version of the Windows Phone SDK 7.1, which includes the final version of the XNA Game Studio 4.0 Refresh.  After a bit of a delay, we have now also released the standalone versions of the XNA Game Studio 4.0 Refresh and the XNA Framework 4.0 Refresh so you can download and install them separately if you plan to develop Windows and/or Xbox 360 games with XNA Game Studio but do not want to install the full Windows Phone SDK 7.1 in order to do so.

    Here are the standalone download links:

    XNA Game Studio 4.0 Refresh

    XNA Framework Redistributable 4.0 Refresh

    If you have the original version of XNA Game Studio 4.0 or the XNA Framework Redistributable 4.0 installed on your computer, the Refresh installers will automatically upgrade them for you behind the scenes.  If you have any beta version of the Windows Phone SDK 7.1 installed, the Refresh installers will not automatically upgrade them, and you will need to uninstall the beta version first.

    If you encounter XNA Game Studio setup failures

    If you run into an installation or uninstallation failure for XNA Game Studio, please zip your setup log files, upload them to a file server of your choice (such as http://skydrive.live.com), and post a link to the log files in the App Hub Forums or in a comment on my blog to get additional support.  Here are the log file locations for each version of XNA Game Studio:

    • XNA Game Studio 2.0 - %ProgramFiles%\Microsoft XNA\XNA Game Studio\v2.0\Setup\Logs
    • XNA Game Studio 3.0 - %temp%\XNA Game Studio 3.0 Setup\Logs
    • XNA Game Studio 3.1 - %temp%\XNA Game Studio 3.1 Setup\Logs
    • XNA Game Studio 4.0 - %temp%\XNA Game Studio 4.0 Setup\Logs
    • XNA Game Studio 4.0 Refresh - %temp%\XNA Game Studio 4.0 Setup\Logs

    If you run into uninstallation issues with any release of the Windows Phone SDK or XNA Game Studio, you can use the cleanup tool described at http://blogs.msdn.com/astebner/pages/9544320.aspx to forcibly remove the Windows Phone SDK or XNA Game Studio.

  • Aaron Stebner's WebLog

    Link to information about the WiX v3.6 beta

    • 0 Comments

    Rob Mensching posted an item on his blog announcing the release of the WiX v3.6 beta.  The key feature in WiX v3.6 is the Burn bootstrapper/chainer.  To summarize Rob’s post, Burn includes the following features:

    • Modern setup UI, including using managed code for setup UI even if the .NET Framework isn’t installed
    • Child setup package download management
    • Unified progress UI across packages
    • Package-level reference counting
    • Patch slip-streaming
    • Elevation prompt management

    In addition, all known WiX core toolset bugs that were opened against WiX v3.5 or earlier have been fixed in the WiX v3.6 beta.

    I encourage you to download the WiX v3.6 beta and give it a try if you get a chance.

Page 1 of 1 (3 items)