|
Home > Archive > SQL Anywhere ultralite > December 2005 > Plans for UL.NET support for Compact Framework v2.0
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Plans for UL.NET support for Compact Framework v2.0
|
|
|
| I'm currently developing a Windows Mobile 5.0 UL.NET app
with the compact framework v2.0 in VS 2005. The thought
occurred to me that I may have a problem becuase the compact
framework v2.0 version of ul.net is currently not functional
and I have no way of knowing if or when it will become
functional.
Technically the supported platforms doc says, "Requires .NET
Compact Framework version 1.0.3705 or later" which means
v2.0 should be working, right?
(**Side note on the doc: There was never a CF version
1.0.3705. The first version was 1.0.2268.)
So should I be cutting my losses now, scrapping my current
code and heading back to VS.NET 2003 and cf 1.0? Or can I
be confident that a new patch which works with version 2.0
is coming soon?
Thanks
rr12
| |
| Liam Cavanagh 2005-12-19, 11:23 am |
| I believe if you are developing a new VS2005 app that uses the v2.0
framework then you will need to use a UltraLite ADO.NET driver which also
supports version 2.0 of the Compact Framework (meaning the old 1.0 version
will not work)
There is an EBF (build 3228 for Windows CE) which is scheduled to be
uploaded today. I recommend downloading this.
--
Liam Cavanagh
Sr. Product Manager
Certified ASA Developer Version 8
iAnywhere
<rr12> wrote in message news:43a05b5e.3b91.1681692777@sybase.com...
> I'm currently developing a Windows Mobile 5.0 UL.NET app
> with the compact framework v2.0 in VS 2005. The thought
> occurred to me that I may have a problem becuase the compact
> framework v2.0 version of ul.net is currently not functional
> and I have no way of knowing if or when it will become
> functional.
>
> Technically the supported platforms doc says, "Requires .NET
> Compact Framework version 1.0.3705 or later" which means
> v2.0 should be working, right?
>
> (**Side note on the doc: There was never a CF version
> 1.0.3705. The first version was 1.0.2268.)
>
> So should I be cutting my losses now, scrapping my current
> code and heading back to VS.NET 2003 and cf 1.0? Or can I
> be confident that a new patch which works with version 2.0
> is coming soon?
>
> Thanks
>
> rr12
| |
|
| The new version works fine. I guess I'll stick with cf 2.0.
Thanks.
|
|
|
|
|