.NET Framework 1.1 component isn't working

[james]

I've included the .NET Framework 1.1-Hotfix Q831558 component, which I
downloaded from the MSDN QFE site, along with WinLogon, which is a
dependency of the .NET Framework 1.1-Hotfix Q831558 component. After FBA,
when an attempt to run an application that was written in C# using Visual
Studio .NET 2003 is made, an error message appears stating that .NET
Framework 1.1 needs to be installed in order to run the application. Has
anyone else encountered this?

Although a working .NET Framework 1.1 component is the preference, as a work
around solution, I attempted to create a component which launches the .NET
Framework 1.1 installation file, dotnetfx.exe (which is used to install .NET
Framework 1.1 on a desktop system). My component basically includes the
installation executable and an FBA Generic Command resource, which launched
the EXE after FBA is complete. The installer program seems to require a
component that isn't present. Does anyone know which XPE component is
required to run the .NET Framework 1.1 installation program (dotnetfx.exe)
on XP Embedded?

 

[Ben Madsen]

I just installed this component (and a slew of other hotfixes I had
neglected for a few months). I haven't had any problems. The one thing I
did, however, was remove the .NET Component and re-add it in manually.
When it upgraded it for me previously, there were some messages that made
me feel uncomfortable with the upgrade of that particular component. Then
again, it may just be that it requires one of the other hotfixes you might
have missed.

Hope this helps,
-Ben

[posted and mailed]

 

[Ben Madsen]

Let me re-phrase my response to include thoughts that came to me AFTER
reading the WHOLE post... My brain has been turning off on me here in
the later afternoons since the flu season has been on...

While the .Net 1.1 Framework Component install was fine on my system, it
seemed that it was only activated AFTER the FBA was completed. It seems
to me that this would indicate a design in the framework component, and
indeed the XP Embedded FBA Build process, of the following description.
If at all possible, move the scripting of the actual installation
routines either into componentized steps like registry entires, file
copies and the like, or move it to a seperate installer that runs after
the FBA is completed.

My hack involved setting a wrapper application that ran the installer
and did some last minute system checks as the user shell. At the end of
that process, the wrapper application set the installed application as
shell and rebooted.

Now, this is a MAJOR KLUDGE in my book, but it seemed the only way to do
this at the moment, and we were on a tight deadline. I'll be looking
for better ways to install my application anyway.

-Ben

I just installed this component (and a slew of other hotfixes I had
neglected for a few months). I haven't had any problems. The one
thing I did, however, was remove the .NET Component and re-add it in
manually. When it upgraded it for me previously, there were some
messages that made me feel uncomfortable with the upgrade of that
particular component. Then again, it may just be that it requires one
of the other hotfixes you might have missed.

Hope this helps,
-Ben

[posted and mailed]

I've included the .NET Framework 1.1-Hotfix Q831558 component, which
I downloaded from the MSDN QFE site, along with WinLogon, which is a
dependency of the .NET Framework 1.1-Hotfix Q831558 component. After
FBA, when an attempt to run an application that was written in C#
using Visual Studio .NET 2003 is made, an error message appears
stating that .NET Framework 1.1 needs to be installed in order to run
the application. Has anyone else encountered this?

Although a working .NET Framework 1.1 component is the preference, as
a work around solution, I attempted to create a component which
launches the .NET Framework 1.1 installation file, dotnetfx.exe
(which is used to install .NET Framework 1.1 on a desktop system). My
component basically includes the installation executable and an FBA
Generic Command resource, which launched the EXE after FBA is
complete. The installer program seems to require a component that
isn't present. Does anyone know which XPE component is required to
run the .NET Framework 1.1 installation program (dotnetfx.exe) on XP
Embedded?

 

[KM]

James,

Do you see any related messages (or maybe errors) in your FBALog.txt log?
There should be a message on "OC Manager Request for .NET Framework"
request.

 

[Andy Allred [MS]]

James, this sounds an awful like a mail thread from earlier today where I
realyed the following:

Our contact on the CLR team says to check out this msdn article:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/redistdeploy1_1.asp
and read the section called "Detecting that the .NET Framework 1.1 is
installed". It's possible that the application is detecting the netfx
installation differently than recommended.

Thanks
Andy

 

[KM]

Andy,

Looks like [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v1.1.4322],"Install"=1 dword value is missing from the ".NET
Framework 1.1 - Hotfix Q831558" component registry data entries as well as
"MSI"=1, and "SP"=0 values.
Bug?
Interesting but relative Language Pack values are in place for ".NET
Framework 1.1 JPN Language Pack - Hotfix Q831558" component (of course,
under 1041 subkey).

Also, if you do the install of the .Net Framework 1.1 on XPe image using
WindowsUpdates, the registry entries get set properly (I guess that's why
the .Net works fine getting installed this way).

KM

 

[Andy Allred [MS]]

So i've only briefly looked at the component this morning, initial
appearances show the component is incorrectly processing the netfxocm.inf as
a custom action during FBA. When the process is working properly it should
be injecting many registry keys to the runtime. Let me forward the
information to Jon so he can work on this.

I apologize for the headache folks. Bear with me.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

Andy,

Looks like [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v1.1.4322],"Install"=1 dword value is missing from the ".NET
Framework 1.1 - Hotfix Q831558" component registry data entries as well as
"MSI"=1, and "SP"=0 values.
Bug?
Interesting but relative Language Pack values are in place for ".NET
Framework 1.1 JPN Language Pack - Hotfix Q831558" component (of course,
under 1041 subkey).

Also, if you do the install of the .Net Framework 1.1 on XPe image using
WindowsUpdates, the registry entries get set properly (I guess that's why
the .Net works fine getting installed this way).

KM

James, this sounds an awful like a mail thread from earlier today where I
realyed the following:

Our contact on the CLR team says to check out this msdn article:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/redistdeploy1_1.asp

and read the section called "Detecting that the .NET Framework 1.1 is
installed". It's possible that the application is detecting the netfx
installation differently than recommended.

Thanks
Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================


a
work install
.NET

 

[james]

Thanks Andy, and everyone else, for your input.

By the way, my ".NET installer" work-around component worked once I included
the Windows Installer Service component. This isn't the ideal solution, but
it works for now.

So i've only briefly looked at the component this morning, initial
appearances show the component is incorrectly processing the netfxocm.inf as
a custom action during FBA. When the process is working properly it should
be injecting many registry keys to the runtime. Let me forward the
information to Jon so he can work on this.

I apologize for the headache folks. Bear with me.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

Andy,

Looks like [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v1.1.4322],"Install"=1 dword value is missing from the ".NET
Framework 1.1 - Hotfix Q831558" component registry data entries as well as
"MSI"=1, and "SP"=0 values.
Bug?
Interesting but relative Language Pack values are in place for ".NET
Framework 1.1 JPN Language Pack - Hotfix Q831558" component (of course,
under 1041 subkey).

Also, if you do the install of the .Net Framework 1.1 on XPe image using
WindowsUpdates, the registry entries get set properly (I guess that's why
the .Net works fine getting installed this way).

KM

James, this sounds an awful like a mail thread from earlier today

where

I

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/redistdeploy1_1.asp as

a the
.NET

require

a