is it possible to install the .NET compact framework?

  • Thread starter Thread starter Guest
  • Start date Start date
It might or might not have the .NET CF *on the device* from the factory.
You don't need the SDK for it; Visual Studio.NET 2003 has support for
"Windows CE.NET" from the 'factory'.

Paul T.

"spacedog"
this may be a dumb question, but i'm working with some HW that is going to
Click to expand...
be running Windows CE 4.2 . this doesn't necessarily mean that the .NET
compact framework is going to be available in their SDK does it? or does
it? from what i read on this FAQ
(http://msdn.microsoft.com/mobility/prodtechinfo/devtools/netcf/FAQ/default.
aspx) it seems that the SDK has to have it included w/ the SDK, so i'm
guessing you can't install it later?
 
i'm not quite sure i understand your answer. if the device i get doesn't have .NET CF on it but it is running windows 4.2, is there a way to install .NET CF on it? or does it have to be installed at the same time the HW people install the windows 4.2 OS

thanks ....
 
Sure, you can install it from VS.NET, just as you can with a PPC2002 device,
which doesn't have it in ROM, either. Whether the device has a persistent
location to store it or not, I can't tell you...

Paul T.

"spacedog"
i'm not quite sure i understand your answer. if the device i get doesn't
Click to expand...
have .NET CF on it but it is running windows 4.2, is there a way to install
..NET CF on it? or does it have to be installed at the same time the HW
people install the windows 4.2 OS?
 
what do you mean by "persistent"? when the .NET CF is deployed i see that "System_SR_enu.cab" is copied over (i found out "The .NET Compact Framework provides localized exception strings for applications in the system resource file System.SR.dll"). also, dlls and files are copied over (and registered i assume). the registry is persistent and the files that were copied over would still be there, so which part of that wouldn't be persistent?

thanks ...
 
It's the files that are the question (although I suppose the registry might
not be persistent on some devices). When power is cycled on most industrial
devices, the contents of the Windows directory is *gone* (there's no little
coin battery like there is to keep the power on on a Pocket PC). Anything
not in ROM has to be reinstalled. Most devices have some area which is
persistent through a power cycle, but it's often not the Windows directory
(where VS.NET installs the .NET CF). Maybe it's a storage card of some type
or a flash 'drive'. If you can install to persistent storage and the
registry is persistent, then you're fine. What device are we talking about,
anyway?

Paul T.

"spacedog"
what do you mean by "persistent"? when the .NET CF is deployed i see that
Click to expand...
"System_SR_enu.cab" is copied over (i found out "The .NET Compact Framework
provides localized exception strings for applications in the system resource
file System.SR.dll"). also, dlls and files are copied over (and registered i
assume). the registry is persistent and the files that were copied over
would still be there, so which part of that wouldn't be persistent?
 
thanks for clearing all this up. i didn't realize handhelds were quite so different than desktops. we're getting specialized hardware for a company we're working with, and we don't really have much control over whether they include .NET CF or not. last question: i take it that there's no easy way to set VS .NET 2003 to deploy to a diff directory than the default

thanks again.
 
I'm not aware of *any* way to tell it where to deploy. If you can figure
out *what* is being deployed, you might be able to copy it to a persistent
location and arrange for it to be copied back on a cold boot or something.

Paul T.

"spacedog"
thanks for clearing all this up. i didn't realize handhelds were quite so
Click to expand...
different than desktops. we're getting specialized hardware for a company
we're working with, and we don't really have much control over whether they
include .NET CF or not. last question: i take it that there's no easy way
to set VS .NET 2003 to deploy to a diff directory than the default?
 
Back
Top