XPE - .NET & minlogin/cmd shell

[Jeff Arnett]

Even though target designer allows it; it seems that
the .NET FW does not work on a minlogin/cmd shell image.

All the .NET dependencies are included in the image just
fine.

FBA fails w/ corrupt files error. (Regasm.exe has been
tampered w/ failed to validate blah blah ...)

Is .NET not support on minlogin? If not, it seems that
target designer ought to enforce this.

-jeff

 

[Jeff Arnett]

Andy,

This has become a major issue for us and our industry.
If .NET, then the XPE image is very large, and basically
requires hardware similar to XPPro.

We see little value in using XPE/.NET if the image is
large, if .NET support lags (still no .NET 1.1 SLD), it's
buggy (investigation turned up the issue w/ certain .NET
API's working at all on XPE), the update process is
different and requires effort from the OEM to make the
DUA script.

Many of the headaches we can live with but if we can't
get .NET/XPE image down to ~150 MB we can't use it. Is
there plans to further componentize .NET in longhorn or
even XPE SP2? Is there plans to put .NET CF on XPE? Or
how about supporting .NET on minlogin/cmd shell? Isn't
most of .NET just a wrapper around Win32 & COM - why do
we need "windows logon" and "explorer"??

Sorry for the tough questions but we are seriously
backpedaling on our interest in XPE because of these non-
granular .NET issues?

Thoughts?

 

[Slobodan Brcin]

Hi Jeff,

Many of the headaches we can live with but if we can't
get .NET/XPE image down to ~150 MB we can't use it.

You should be able to squeeze winlogon and .NET to 150MB..

Just don't let TD resolve all dependencies.

Best regards,
Slobodan

 

[Andy Allred [MS]]

Hi Jeff.
We're in the process of componentizing netfx 1.1 right now, i have no idea
what the release date is, so all I can do right now is thank you for your
patience. If netfx has a dependency on Winlogon due to security reasons,
then there is little that can be done with the existing netfx binaries to
remove this dependency since .net framework for XP was architected before
there was such a thing as XPe. So there was some "catch-up" that needed to
happen.

Now that this is an issue, it's on the netfx team's radar for future
releases and is bugged.

Thanks