.NET Framework 1.1 QFE for XPe

  • Thread starter Thread starter David Repko
  • Start date Start date
David,

It is unlikely that it will be out by that particluar date, but it should be
available shortly.
--
Thanks,

Lynda

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

I'm just now starting the development of an XPe target
that will go through a concept demonstration in March. Our
application developers have indicated that the 1.1
framework is required, but since 1.1 is not available as
an XPe component, I'm going to rebuild the app for 1.0 and
keep my fingers crossed.

If 1.1 is necessary I would consider creating my own 1.1
component ... a not-too-attractive option. Is it possible
that a pre-release version of the QFE would be available
to get a head start? Otherwise, does sometime-in-October
look reasonable for the release?

BTW: I was still waiting to hear more about an MSDE QFE,
but it looks like we're close to success on a home-grown
solution for that ... testing it tomorrow.

Thanks,

Craig
 
Lynda said:
It is unlikely that it will be out by that particluar date, but it should be
available shortly.

Sorry to keep pushing on this point but it is something that I am
looking out for and would appreciate a more definitive release date.
Unfortunately, my boss doesn't seem to accept "available shortly" as a
valid timescale for our project plan.

Thanks,

Andy.
 
Sorry to keep pushing on this point but it is something that I am
looking out for and would appreciate a more definitive release date.
Unfortunately, my boss doesn't seem to accept "available shortly" as a
valid timescale for our project plan.

You can make a custom component to install .NET 1.1. We did. Start
off by making sure .NET 1.0 and the Windows Installer are in your
build. Then make a custom component containing the 1.1 files:

InstMsiW.exe
install.exe
netfx1.cab
InstMsi.exe
dotnetfx.exe
netfx.msi

and include a tiny .cmd script that you write:

c:
cd \where\you\pre-installed\the\files\above
msiexec /qb /l* c:\some\log\directory\dotNet.log /i netfx.msi

Then if you are using the Explorer shell add a RunOnceEx resource to
run the tiny .cmd script when Explorer first starts. You might try
running it from FBA using an FBA generic command but I'm not sure that
would work or not.
 
Back
Top