.Net 1.1 component creates bad directory entry

[Peter Boden]

I noticed the other day that the .Net 1.1 component seems to create a
directory with a bad name. After FBA completes, my image contains the
following folder:

C:\Documents and Settings\All Users\Start Menu\Programs\?????

Which contains two items:
-- Microsoft .NET Framework 1.1 Configuration
-- Microsoft .NET Framework 1.1 Wizards

After looking for the same files on my dev system, it looks like the bogus
directory should be "Administrative Tools". I don't have this component in
my image, so I suppose that directory doesn't get created.

Minor issue, but one that should probably be fixed.

Thanks,
Pete

 

[Ben Harris]

I noticed the other day that the .Net 1.1 component seems to create a
directory with a bad name. After FBA completes, my image contains the
following folder:

C:\Documents and Settings\All Users\Start Menu\Programs\?????

Which contains two items:
-- Microsoft .NET Framework 1.1 Configuration
-- Microsoft .NET Framework 1.1 Wizards

After looking for the same files on my dev system, it looks like the bogus
directory should be "Administrative Tools". I don't have this component in
my image, so I suppose that directory doesn't get created.

Minor issue, but one that should probably be fixed.

Thanks,
Pete

I've noticed this too, but in my case I do have the "Administrative Tools"
folder included in my image.

Ben.

 

[Thomas Johansen]

Same here. Is this component tested ???

 

[Lynda Allen [MS]]

There is a bug on this that should be fixed for the next release. Thanks!

 

[Gordon Smith \(eMVP\)]

The workaround I've been using in the meantime is just installing the 1.1
framework as part of FBA (running dotnetfx.exe) instead of using the buggy
component.

--Gordon Smith (eMVP)

 

[Mark K Vallevand]

Will dotnetfx.exe run without user input?
I'll have to check if it has command line options for silent install.

 

[Gordon Smith \(eMVP\)]

I used the /Q command line option, but it wasn't as quiet as I would have
liked (had to click buttons). I didn't look any further after that - my
customer was in a rush and didn't mind clicking.

--Gordon Smith (eMVP)

 

[Mark K Vallevand]

Yes, I found the same things. Clicks are a problem with a headless system
like mine.
Looks like I'll continue to run dotnetfx.exe using remote desktop after FBA
completes. Its already part of my manual fix-up procedures prior to
official image release.

--
Regards.
Mark K Vallevand

I used the /Q command line option, but it wasn't as quiet as I would have
liked (had to click buttons). I didn't look any further after that - my
customer was in a rush and didn't mind clicking.

--Gordon Smith (eMVP)

Will dotnetfx.exe run without user input?
I'll have to check if it has command line options for silent install.

The workaround I've been using in the meantime is just installing
the 1.1 framework as part of FBA (running dotnetfx.exe) instead of
using the buggy component.

--Gordon Smith (eMVP)

Lynda Allen [MS] wrote:
There is a bug on this that should be fixed for the next release.
Thanks!

I noticed the other day that the .Net 1.1 component seems to
create a directory with a bad name. After FBA completes, my image
contains
the following folder:

C:\Documents and Settings\All Users\Start Menu\Programs\?????

Which contains two items:
-- Microsoft .NET Framework 1.1 Configuration
-- Microsoft .NET Framework 1.1 Wizards

After looking for the same files on my dev system, it looks like
the bogus directory should be "Administrative Tools". I don't
have this component in my image, so I suppose that directory
doesn't get created.

Minor issue, but one that should probably be fixed.

Thanks,
Pete

 

[Gordon Smith \(eMVP\)]

Technically... you could write an app to scan the desktop for the
appearance of the install window and send it the appropriate events. Sort
of like the whole "message box interception" threads, but slightly more
advanced. You'll do more than just sending a close event.

--Gordon Smith (eMVP)

Yes, I found the same things. Clicks are a problem with a headless
system like mine.
Looks like I'll continue to run dotnetfx.exe using remote desktop
after FBA completes. Its already part of my manual fix-up procedures
prior to official image release.

I used the /Q command line option, but it wasn't as quiet as I would
have liked (had to click buttons). I didn't look any further after
that - my customer was in a rush and didn't mind clicking.

--Gordon Smith (eMVP)

Will dotnetfx.exe run without user input?
I'll have to check if it has command line options for silent
install.

The workaround I've been using in the meantime is just installing
the 1.1 framework as part of FBA (running dotnetfx.exe) instead of
using the buggy component.

--Gordon Smith (eMVP)

Lynda Allen [MS] wrote:
There is a bug on this that should be fixed for the next release.
Thanks!

I noticed the other day that the .Net 1.1 component seems to
create a directory with a bad name. After FBA completes, my
image contains
the following folder:

C:\Documents and Settings\All Users\Start Menu\Programs\?????

Which contains two items:
-- Microsoft .NET Framework 1.1 Configuration
-- Microsoft .NET Framework 1.1 Wizards

After looking for the same files on my dev system, it looks like
the bogus directory should be "Administrative Tools". I don't
have this component in my image, so I suppose that directory
doesn't get created.

Minor issue, but one that should probably be fixed.

Thanks,
Pete

 

[Aaron Stebner]

You can work around the bad directory issue by doing the following prior to
building your XP Embedded image:

1. Locate the file 831558_netfx.inf in your repository
2. Open it up in a text editor such as notepad
3. Remove the line starting with ProfileItems in the [netfx_install]
section
4. Save and close the file


Also, you can refer to the article at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/ht
ml/dotnetfxref1_1.asp for information about how to install the .NET
Framework package silently via command line. The easiest command line to
use for a silent install is the following:

dotnetfx.exe /q:a /c:"install.exe /q"