Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS with no warranties, and confer no rights. Additionally, views expressed herein are my own and not those of my employer, Microsoft.
A while back, I posted some instructions that can be used to create an administrative install point for the .NET Framework 2.0. The .NET Framework 2.0 SP1 was recently released (it is required in order to install the .NET Framework 3.5). There are some behind the scenes architecture changes in the .NET Framework 2.0 SP1 setup (which I'm planning to describe in more detail in a future blog post). Those changes cause the previous instructions I posted for creating an administrative install point to no longer work.
Here are some updated steps that can be used to create an administrative install point for the .NET Framework 2.0 SP1 for each of the supported processor architectures.
To create an administrative install point for the .NET Framework 2.0 SP1 x86:
With these steps, you will have an administrative install point for the .NET Framework 2.0 SP1 x86 located at c:\netfx20sp1\x86\AIP. You can then install the MSI directly using a command line like the following:
msiexec.exe /i c:\netfx20sp1\x86\AIP\netfx20a_x86.msi /l*v %temp%\netfx20sp1x86log.txt /qb VSEXTUI=1
You can adjust the parameters as needed if you want a fully silent install instead of basic UI, or want to use any other standard Windows Installer command line parameters.
To create an administrative install point for the .NET Framework 2.0 SP1 x64:
With these steps, you will have an administrative install point for the .NET Framework 2.0 SP1 x64 located at c:\netfx20sp1\x64\AIP. You can then install the MSI directly using a command line like the following:
msiexec.exe /i c:\netfx20sp1\x64\AIP\netfx20a_x64.msi /l*v %temp%\netfx20sp1x64log.txt /qb VSEXTUI=1
To create an administrative install point for the .NET Framework 2.0 SP1 ia64:
With these steps, you will have an administrative install point for the .NET Framework 2.0 SP1 ia64 located at c:\netfx20sp1\ia64\AIP. You can then install the MSI directly using a command line like the following:
msiexec.exe /i c:\netfx20sp1\ia64\AIP\netfx20a_ia64.msi /l*v %temp%\netfx20sp1ia64log.txt /qb VSEXTUI=1
<update date="1/23/2008"> Added example command lines to install the MSI directly after creating the administrative install point. </update>
PingBack from http://geeklectures.info/2007/12/16/creating-an-administrative-install-point-for-the-net-framework-20-sp1/
I recently posted a set of instructions for creating an administrative install point for the .NET Framework
PingBack from http://msdnrss.thecoderblogs.com/2007/12/20/creating-an-administrative-install-point-for-the-net-framework-30-sp1/
.NET Framework 2.0 SP1 appears to be a full version with sp1 slipstreamed. Can go skip 2.0 install and go straight to install 2.0 Sp1 instead?
Hi TerryCheng - You're correct, the .NET Framework 2.0 SP1 is a slipstream release that includes the original .NET Framework 2.0 functionality and the patched binaries that are a part of SP1. The 2.0 SP1 package will correctly install on a system that does not yet have the .NET Framework 2.0, and it will automatically upgrade the .NET Framework 2.0 to SP1 if it is already on the system.
If you're interested, I posted a bit more about the behind the scenes details of 2.0 SP1 setup at http://blogs.msdn.com/astebner/archive/2008/01/17/7145670.aspx.
PingBack from http://blogs.msdn.com/astebner/archive/2008/01/17/7145670.aspx
The official deployment guides for system administrators and application developers have been posted
After installing and using Quickbooks 2008 for awhile, all of a sudden a laptop could not get into quickbooks. the Loading screen appeared but then would disappear without opening quickbooks. after much research (see http://support.quickbooks.intuit.com/support/pages/knowledgebasearticle/1009275
it indicated it was a damaged component of Microsoft.NET Framework 2.0
It suggested going thru add/remove programs to delete Microsoft .net framework 2.0--which of course didn't work. we also tried restoring to an older date, and that didn't work (3 attempts). In looking on line there were lots of complicated ways to try.
One computer "expert" suggested wiping the harddrive and restoring everything from start(way over my head) and another said the server computer and laptop may not have the same level of Microsoft Net, which was the case. The laptop had 2.5, the main server had 3.0--however another computer was working fine with the 2.5 framework and attaching to quickbooks without a problem.
We tried loading Framework 3.0 onto the laptop, and that wouldn't work either, however it did work on the 2nd computer.
However, I found a way to fix our situation without alot of trouble---maybe it will work for some of you.
go to control panel, add/remove programs.
Click on Microsoft Framework Net 2.0
DO NOT do the change/remove button
there is a place to click that says:
"click here for support" click on that button
you then get an option of support or products update link. click on the products update link
which brings you to the MSDN page.
http://msdn2.microsoft.com/en-us/vstudio/default.aspx
a microsoft silverlight install screen will come up---i just closed that screen
then scan down that page and there is an option to download Microsoft Framework Net 3.5
hit download, then save.
We were then able to again open quickbooks on the laptop, and have since added this 3.5 to all our computers, and so far all is working well.
Good Luck, I hope this saves some of you time, and works.
JW
Since the .NET Framework 2.0 SP1 and 3.0 SP1 shipped (as prerequisites for the .NET Framework 3.5 and
PingBack from http://msdnrss.thecoderblogs.com/2008/02/19/how-to-perform-a-silent-repair-and-uninstall-of-the-net-framework-20-sp1-and-30-sp1/
Following the procedure 'To create an administrative install point for the .NET Framework 2.0 SP1 x86:' I found that the administrative install MSI would not run with the switches given, or any switches for that matter. I got the message that I had to run setup.exe. The only way I found around this was to edit the MSI using Wise Windows Installer Editor and remove the Custom Action "*BlockDirectInstall*".
Then it worked fine and I should be able to deploy via Active Directory Software installation which is my goal.