How to install the .NET 2.0 MSI during FBA
Quite a few people have asked how this can be accomplished without having to have a componentized version from the XPe team. The answer is - yes - this can be done. I've even made a component to do it for you so it's easier for you! *grin* To use this component to enable the .NET Framework v2.0 MSI to be installed on an Embedded runtime first download a couple prerequisites to get started.
Here is the XPe Component package - netfx2.0_MSI_FBA_Install.zip
Here is the .NET Framework v2.0 MSI for full Windows XP
Now that you've got that taken care of lets extract out the files from the 'dotnetfx.exe' file.
- Open CMD.EXE
- Navigate to where you saved the file (e.g. - C:\Temp)
- Make a new directory for these files (e.g.- C:\Temp\Extracted_Files)
- Enter the command dotnetfx.exe /C /T:"Full Path" (e.g.- dotnetfx.exe /C /T:"C:\Temp\Extracted_Files")
Alright. Now we're on the home stretch.
- Import the dotNet 2.0 Setup MSI During FBA.sld into your database.
- An empty repository folder for this component will be created under \Windows Embedded Data\Repositories- {858FABF0-7111-403D-A4EA-D05F8926CFFF}
- Copy the extracted files from your extract path into the repositories folder listed in step 2. These files in my scenario above would be found in C:\Temp\Extracted_Files.
- Open Target Designer, import your PMQ and add the “.NET Framework 2.0 - Setup MSI during FBA” component to your runtime.
- Run check dependencies. Resolve any dependencies for the runtime as per usual.
- Build and deploy.
The .NET Framework v2.0 should be now installed after FBA is complete. Phase 8300 (as viewed in the component above) occurs right before the first reboot happens after FBA has run for several minutes. Please note that you are still able to add the 1.x framework VIA Target Designer. The interactions and ramifications of doing this scenario have not been tested, documented, or even looked at. You *COULD* see weirdness and/or parts stomped out between the versions. Just beware is all. *grin*
That should be all you have to do to get the framework installed. The directory dotnetfx that is located on your %systemroot% ( C:\dotnetfx\ for example ) is safe to delete once you're in your runtime. I would personally remove it before doing any system cloning, EWF, or any other feature setup so that there's no extra clutter in your OS.
Happy developing!
Update 2006.05.16
There was an issue found with the component that is contained within this article. Unfortunately it would cause ASP.NET to not setup correctly. The missing item was a dependency upon the component "WMI Win32 Provider" which is used during the setup of ASP. So - if you're utilizing the older component and are having issues please grab the new one and import it. Just uncheck the box on the import dialog labeled "Copy repository files to repository root", upgrade the component in your configuration, run check depdendencies, and re-build your image. You should be good to go. Alternatively you can manually add the component listed above, run check dependencies, and re-build. The choice is up to you. *grin*
- Nick
