itsRashmi

hello all,

We are developing windows mobile applications for supporting wide range of

devices belonging to smart phone and pocket pc families. .Net compact

framework 2.0 provides an exra edge over .net cf 1.0. but we heard that .Net

cf 1.0 is shipped with OS and .net cf 2.0 needs to be downloaded separately.

So is this means that if we use .net cf 2.0 for application development our end

user has to download .net cf 2.0 which is extra burden of 4-5 MB over an

application cab size if downloaded with OTA. Please let us know what is the

industry standard and should we go for .net cf 1.0 or .net cf 2.0

If some white paper or case study we can get to explain benifits of 2.0 over 1.0 or vice versa that will be great

regards,

Rashmi



Re: .NET Compact Framework .Net compact framework 2.0 vs 1.0 --- please suggest

Ilya Tumanov

That is a fairly common misconception: if I use NETCF V1 I dont have to install it. Yes, you do have to install it to make sure you have the latest version your application was tested against. In other case device might have older version which your application cant run against. You also would probably have to use number of 3rd party libraries you might not need with NETCF V2 and you would need to add more code to your application to implement whatevers not available in V1. To sum up:

NETCF V1 needs:

- NETCF V1 SP3.

- Your application

- Probably several 3rd party libraries to provide functionality you need.

NETCF V2 needs:

- NETCF V2 SP2

- Your application.

Total size might be or might not be smaller for NETCF V1 but it certainly would be much harder for you not to mention potentially limiting your application to obsolete devices.






Re: .NET Compact Framework .Net compact framework 2.0 vs 1.0 --- please suggest

Christopher Fairbairn

Hi,

This is also something which is constantly improving, for example with Windows Mobile 6 you have .NET CF v2 SP1 and SQL Server Compact Edition in ROM.

In general however the versions in ROM will be lagging the current releases due to different ship dates and scheduling requirements between the various Microsoft teams who develop these components.

For example the Compact Framework team has many internal customers within Microsoft other than Windows Mobile, for example the XBox360 team. So sometimes releases can't be aligned to benifit Windows Mobile.

I typically handle this as Ilya has mentioned, by depolying the latest service pack along with the initial installation of my product. This makes the initial deployment larger, but is a one time only requirement. As upgrades to our product occur we only deploy over the wire the components which have changed. So if we don't change the .NET CF version for two years, it's only deployed to the devices once, even if we make five revisions of our product in that same timeframe.

If evaluating third party deployment products this is something to keep in mind.

Hope this helps,

Christopher Fairbairn






Re: .NET Compact Framework .Net compact framework 2.0 vs 1.0 --- please suggest

itsRashmi

Thanks for the reply guys.

so we should go for .net cf 2.0. but dont you think on OTA, increasing size of cab by 4-5 mb is hurdle and can hit number of

downloads for our applications as far as current phones avilable in US market concerns , our application download free of cost right now , with cab size around 200kb, so our marketing guys conerned abt just adding up 4-5 mb of extra load just beacuse of .net 2.0 cf extension , so what do you sugget I mean if we ge somewhere a statistical data of probablity having .net 2.0 already installed on device then it is useful to take the decesion.

also I heard that .net cf can be easily distributable if we use msi instead of OTA.

regards,

Rashmi





Re: .NET Compact Framework .Net compact framework 2.0 vs 1.0 --- please suggest

MarkIsMobile

I can appreciate your concerns about targeting your app towards v2.0, but to target an earlier (much earlier) runtime might not leave you a lot of options for the future of your customers. In my opinion your argument to target v1.x apps would be analogous to building desktop software for Windows 95 or Windows 2000. Ya, it may be easier to build apps that are smaller and more easily downloaded, but your application would be at a competitive disadvantage on many fronts. In the final analysis it's all about the "user experience," which includes both the actual use of the software as well as its installation experience. If your application is sufficiently simple that the APIs of v2.0 are wasted (and you have no plans to use them in the future) then this is all just academic. Otherwise, you're much better served by moving towards v2.





Re: .NET Compact Framework .Net compact framework 2.0 vs 1.0 --- please suggest

kareshi

Hi Ilya Tumanov,

In your statement:

NETCF V1 needs:

- NETCF V1 SP3.

- Your application

- Probably several 3rd party libraries to provide functionality you need.

Does it mean that netcf v1 and netcf v1 sp3 are two separate installations I have downloaded the .NET Compact Framework 1.0 SP3 Redistributable here and when I run the downloaded msi file from my PC, it automatically installs both to my PC and the docked device.


If they are two separate installations where can I get the NETCF V1


Regards from a newbie programmer,

K