Partilhar via

Update on how to deploy the .NET Framework 3.0 on Windows XP Embedded

  • Artigo

Earlier this week, I posted an item with a link to an article on the Windows Embedded team's blog that provides step-by-step instructions to create a Windows XP Embedded runtime image that you can install the .NET Framework 3.0 on.

Today, I noticed this post on Mike Hall's blog that includes download links for a package that enables installation of the .NET Framework 3.0 on Windows XP Embedded images without requiring all of the manual steps in that previous step-by-step guide.

If you are an embedded developer or image builder who wants to include the .NET Framework 3.0 in your runtime images, I encourage you to check out Mike's post and the links that it includes for more information.

Comments

  • Anonymous
    June 12, 2007
    The comment has been removed

  • Anonymous
    June 12, 2007
    Hi Desi - Unfortunately, the setup bootstrapper for the .NET Framework will always use the %temp% directory to unpack and install from.  Changing that environment variable should allow you to redirect the temporary space to another drive. If that doesn't work, you can also run each of the child packages that are a part of the .NET Framework 3.0 individually to avoid the bootstrapper trying to use the %temp% directory.  There is a list of packages and command lines in the deployment guide at http://msdn2.microsoft.com/en-us/library/aa964979.aspx that should help you accomplish that if you need to. Hope this helps!

  • Anonymous
    November 02, 2007
    The comment has been removed

  • Anonymous
    November 02, 2007
    The comment has been removed

  • Anonymous
    November 06, 2007
    The comment has been removed

  • Anonymous
    November 13, 2007
    The comment has been removed

  • Anonymous
    November 13, 2007
    The comment has been removed

  • Anonymous
    November 13, 2007
    The comment has been removed

  • Anonymous
    November 13, 2007
    Hi Smedlytonker - DLL initialization errors like this on XPe are nearly always caused by missing dependencies in the runtime image.  Hopefully Depends will help you narrow down the root cause.  You could also try running a tool like Process Monitor (http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/processmonitor.mspx) during .NET 3.0 setup in this scenario to see if it helps narrow down what is missing as well.

  • Anonymous
    November 14, 2007
    The comment has been removed

  • Anonymous
    November 14, 2007
    Hi Smedlytonker - I'm sorry for the continued hassles that this issue is causing for you.  You may want to try to use FileMon (http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx) and/or RegMon (http://www.microsoft.com/technet/sysinternals/utilities/regmon.mspx) instead of Process Monitor to see if that helps avoid the error dialog you're seeing there. Hopefully one of these tools will help you narrow down exactly what dependency is missing that is causing .NET Framework 3.0 setup to fail in this scenario.

  • Anonymous
    November 20, 2007
    The comment has been removed

  • Anonymous
    November 20, 2007
    The comment has been removed

  • Anonymous
    November 20, 2007
    Thanks. I got the same error as listed by SmedlyTonker when attempting to use Proc Mon so I used FileMon and RegMon and I'm plowing thru the log files now. I had tried once before to disable the IIS service and it didn't help but it's worth another try. I'll post again if I discover anything new.

  • Anonymous
    November 21, 2007
    The comment has been removed

  • Anonymous
    November 28, 2007
    I tried adding ASP .NET and it also fixed my webengine.dll problem, however I just moved on to the next cryptic installation problem (nothing in the error log and no return value 3). Thanks for the heads up on your progress. BTW, we're all engineers so the details are never 'boring'. :-)

  • Anonymous
    November 29, 2007
    The comment has been removed