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.
I ran across a question on the .NET Framework setup forum today about installing the .NET Framework 3.0 on a Windows XP Embedded runtime image. Fortunately, Andy alerted me to a post on the Windows Embedded team blog that describes the following:
You can find this blog post at http://blogs.msdn.com/embedded/archive/2007/03/23/deploying-net-framework-3-0-desktop-distribution-package-on-windows-xp-embedded-sp2-runtime.aspx.
If you are a Windows Embedded developer and plan to develop .NET Framework 3.0 applications for you Windows XP Embedded runtimes, I encourage you to take a look at this blog post.
How would you go about installing .Net3 if you didn't want to have the Windows Installer Service as part of the XPe image? I ask this as we don't want to allow end users the ability to install anything else onto the system once we ship it.
Hi Davidwatson66 - Unfortunately, this type of scenario is not supported for the .NET Framework 3.0. You have to install the MSI packages in order to add it to your XPe runtimes. That means that you have to include the Windows Installer Service component in your runtime images. You could look into using other means of locking down your images after they are deployed (possibly Group Policy settings to restrict users from installing for example?)
I'm sorry for the inconvenience that this has caused for you.
Earlier this week, I posted an item with a link to an article on the Windows Embedded team's blog that
PingBack from http://msdnrss.thecoderblogs.com/2007/06/08/update-on-how-to-deploy-the-net-framework-30-on-windows-xp-embedded/