.NET 2.0 not installing - can't run ngen?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

I'm building an image with the .NET 2.0 Framework macro, command shell,
various generic USB support, EWF (disabled on start), and my devices of
course.

I'm auto-resolving everything and using minlogon and ewf loader. The image
gets to about 239MB.

I run it from a hard drive. It boots up, FBA runs all its stuff, and then
reboots to a command prompt as expected. However, a very simple .NET app
won't run. Also, csc.exe, ngen.exe, gacutil.exe, etc... will not run.
Various 'plain' exes do run of course. I noticed during first boot it
doesn't do all the NGen'ing and stuff that .NET framework installation
normally does.

Anyone know why my configuration wouldn't be able to run .NET framework
stuff? I'm at a loss, I've tried all kinds of stuff. Next on the list is
remove EWF altogether, even though it is currently disabled on start. I will
eventually need EWF since this will boot from a CF card.

Thanks in advance
===>David Creel
===>ParkingSoft Inc
 
Probably is related to Minlogon, as I recall .Net has a hard dependency on
some Winlogon functions not available in Minlogon. It's probably been
discussed in the google archives of this NG where you might find more
details on the subject.

Take care.
--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Well, I tried using WinLogon with no success - even though all dependencies
resolve in TD. What would be really cool is a '.NET 2.0 Minimum' type of
macro. If anyone has such as thing, please let me know ;)

For now I guess I'll start from scratch - again - and keep trying random
stuff unless anyone else has suggestions.

===>DavidC
 
Still no luck, even though I am using WinLogon and not using EWF anymore.

Here are the components I am using:
..NET Framework 2.0 for XPe
My Custom Hardware Components
WinLogon
Automatic Logon

I let the auto-resolve do its thing, boot the image, FBA works, then after
it reboots no .NET framework stuff will dare to run.

I'm starting to suspect my installation is screwy somehow. I'm going to try
building it from another PC.
 
I'm going to blow my top soon, but before I do, I'll describe my latest
utterly useless all-day-endeavor into trying to make .NET Framework 2.0 run
on XPe.

Step 1: I wasted a few hours downloading and installing all the stuff for
XPe on a different dev box, including the outdated MSDE.
Step 2: I wasted a few more hours building an image using the same
components mentioned above, EWF not started, auto-resolve dependencies, 245MB
of stuff when i *really* only need ~100MB, etc, etc... Apparently standard
procedure for XPe. Installed it to the target hardware, and watched FBA do
its thing.
Step 3: I tried to run the simplest of .NET console apps, and after that
didn't work, I tried running the pillars of the framework - ngen, gacutil,
etc, none of which worked.
Step 4: I downloaded the 2.0 redistributable to a flash drive and tried to
run it from XPe. Of course this didn't work either; it instead taunted me
with a really vague message about the 'configuration is incorrect'.

Step 5: I posted here out of desperation, then went to gather information on
linux and calling web services from linux, since, ironically, the only reason
I even needed XPe over a firmware-only solution was for ease in calling a web
service!!! This is ridiculous. If there is a depency missing, you'd think
it would be required on the officially-released framework component. Unless
nobody bothered testing it...
 
Hi David,

I don't have any experience with the .NET 2.0 component from the feature
pack, but I've componentized the .NET Framework 2.0 from the installer.
Email me offline and I'll send it to you to try. I've used it on several
builds with good success.

HTH,
Brad
 
Brad,
..net 2.0 was released as a component outside of the FP months ago.

David,
Send an e-mail to wecrt@ microsoft.com Attach a zip with your SLX and your
FBALOG and I will check to see if there's anything obvious here. I don't
know offhand why you're having problems since it's been in use for a while
and already successfully deployed by a lot of other customers. The 'invalid
configuration' may have been because the MSI would not be expecting to see
..net 2.0 already installed via OCM method, it doesn't like to co-mingle like
that. MSI install should work if you did *not* have the .net2.0 component
already there.

In fact, due to servicing challenges, i recommend to a lot of customers that
they use the MSI install method instead of the component, Since DevDiv only
ships MSPs for updates you can get them onto the device much faster
deploying their MSP to the device instead of having to write your custom
scripts to re-register updated binaries.

Check these blog articles (and helpful component you can download) on
deploying the MSI to the device, including during FBA:
http://blogs.msdn.com/embedded/archive/2006/03/17/553921.aspx
http://blogs.msdn.com/embedded/archive/2005/11/23/496333.aspx

Lastly, check out the doc called 'Installing .net" from Product Support team
here:
http://www.microsoft.com/downloads/...e2-fcef-49c2-87ac-cebe233a5f8d&DisplayLang=en

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Yeah, but I use my own component for the same reason you suggest installing
from the MSI. :-)

Actually, I talked to David offline. There is definitely something else at
work here. Other applications such as notepad also do not execute properly.

I sent him a sample SLX and a sample .NET component. I'll report back
results if we have any.

Brad
 
Back
Top