Compact Framework 1.1 on Whidbey

  • Thread starter Thread starter compulim
  • Start date Start date
SmartPhone apps target CF 1.0 in Whidbey, but other device apps target CF
2.0.
 
Thanks Ginny!

Any way to set Whidbey to target 1.0 on PPC?

Or is it legal to publish software that requires 2.0 to end users? Any end
user redistributable available?
 
There is no way to make an application compiled aginst .NET CF 2.0 to run
against .NET CF 1.0 without having .NET CF 2.0 on the device. The act of
changing the target framework is known as binding redirection and this is
only available in .NET CF 2.0 (in a basic form).

At the present time, there is no license available to you that will allow
you to distibute .NET CF 2.0 applications.

HTH
Neil
 
Neil Cowburn said:
There is no way to make an application compiled aginst .NET CF 2.0 to run
against .NET CF 1.0 without having .NET CF 2.0 on the device. The act of
changing the target framework is known as binding redirection and this is
only available in .NET CF 2.0 (in a basic form).

At the present time, there is no license available to you that will allow
you to distibute .NET CF 2.0 applications.
Click to expand...

But is it possible to compile in Whidbey against .NET CF 1.0? If not,
that would be a major blow - I'd really like the features of Whibey (as
an IDE) but our customers are unlikely to be using .NET CF 2.0 in the
near future...
 
Last I heard (July), Whidbey would target CF 2.0 only :-(
[with the exception of SmartPhone projects of course]

Cheers
Daniel
 
Unfortunately, Microsoft has no plans to support .NET CF 1.0 for Pocket PC
or Windows CE in Whidbey
 
Neil Cowburn said:
Unfortunately, Microsoft has no plans to support .NET CF 1.0 for Pocket PC
or Windows CE in Whidbey
Click to expand...

Oh joy. I hope they get things right in terms of VS.NET 2003 and VS.NET
2005 co-existing then (I gather things are flaky with the beta, which
is what I'd expect) as we will definitely be wanting to use .NET 2.0
for some things (web services etc) but still developing CF 1.0 apps.

I'm sure we can't be the only business in that position...
 
Jon,

I'm running both versions of VS on my production machine with no issues, so
I'm pretty sure they'll work side by side for release.

--
Ginny Caughey
..Net Compact Framework MVP
 
Ginny Caughey said:
I'm running both versions of VS on my production machine with no
issues, so I'm pretty sure they'll work side by side for release.
Click to expand...

I've heard some people who have been running that way, but others
who've had problems. I really hope they'll be able to run side-by-side
for everyone by release time. (I'd rather Whidbey were able to target
CF1.0 though so I could ditch VS.NET 2003 entirely.)
 
Hi Jon,

I'd like to do it all from Whidbey too.

--
Ginny Caughey
..Net Compact Framework MVP
 
Ginny Caughey said:
I'd like to do it all from Whidbey too.
Click to expand...

If they've got to make it able to target 1.0 for SmartPhones, I
wouldn't have thought it would be too hard to do it for other devices.
I suggest next time there's an appropriate web chat, whoever's there
requests it :)
 
Robert Levy said:
I'm not on the VS for Devices team but I know that this was definitely a
painful cut for them.
Click to expand...

It's going to be more painful for us, I suspect... :(
The good news is that there has been a lot of work on getting a great
extensibility model into Whidbey so it wouldn't be unreasonable for a 3rd
party to create a plugin that gives CF v1 support for Pocket PC if there is
enough demand for it.
Click to expand...

Sounds like a project for OpenNETCF.org. I'd certainly be interested in
helping such an effort. Do you know if VS.NET 2005 beta 2 will have
enough support to make it worth starting such a plugin before the final
release?
To clear things up about what is/isn't supported, I've attached a chart
showing the current plan of record (all subject to change, of coure).

Green = tool connects with platform for full support of deployment,
debugging, etc
Yellow = apps written with tool will run on platform but tool does not
connect to platform for deployment, debugging, etc
White = tool is not supported for writing apps that run on the platform

I know it's a bit difficult to interpret but hopefully this will make things
less rather than more confusing :)
Click to expand...

Slightly :)

Thanks for taking the time to respond, even if it confirms the bad news
:(
 
Jon,

Thanks for volunteering! We have been talking about this already but haven't
done anything yet. Keep in touch...

--
Ginny Caughey
..Net Compact Framework MVP
 
Back
Top