T
Tomppa
Does the SDF 2.0 work with WinCE 6.0 or only 5.0
THX
THX
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Paul G. Tobey [eMVP]
Since 6.0 isn't released yet, I don't think that there's a read on that.
Since .NET CF itself is supported in CE6, I would expect it to work just
fine.
Paul T.
Since .NET CF itself is supported in CE6, I would expect it to work just
fine.
Paul T.
T
Tomppa
Yea, I hope so.
There are alot of pInvoke calls used though. I hope the OS exposed the same
interfaces for legacy app support.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:%[email protected]...
There are alot of pInvoke calls used though. I hope the OS exposed the same
interfaces for legacy app support.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:%[email protected]...
G
Guest
Of course classes like the PhysicalAddressPointer may break but generally
speaking the underlying APIs are supposed to be the same for most things.
The place where differences lie are in kernel and driver work. We're well
above that, so the provided OS shims should insulate you from any of that.
--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--
speaking the underlying APIs are supposed to be the same for most things.
The place where differences lie are in kernel and driver work. We're well
above that, so the provided OS shims should insulate you from any of that.
--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--
Tomppa said:Yea, I hope so.
There are alot of pInvoke calls used though. I hope the OS exposed the
same interfaces for legacy app support.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:%[email protected]...Since 6.0 isn't released yet, I don't think that there's a read on that.
Since .NET CF itself is supported in CE6, I would expect it to work just
fine.
Paul T.
P
Paul G. Tobey [eMVP]
Some calls may now be privileged that previously weren't, but most that
changed in that way were not things that average applications would use, so
I doubt that any significant fraction of the support would break. Certainly
controls and user interface stuff won't be a problem. If you're using some
part of SDF to map registers on some piece of hardware so that you can
access it directly from the application, *that* will not work (it won't work
from unmanaged code, either).
Paul T.
changed in that way were not things that average applications would use, so
I doubt that any significant fraction of the support would break. Certainly
controls and user interface stuff won't be a problem. If you're using some
part of SDF to map registers on some piece of hardware so that you can
access it directly from the application, *that* will not work (it won't work
from unmanaged code, either).
Paul T.
Tomppa said:Yea, I hope so.
There are alot of pInvoke calls used though. I hope the OS exposed the
same interfaces for legacy app support.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:%[email protected]...Since 6.0 isn't released yet, I don't think that there's a read on that.
Since .NET CF itself is supported in CE6, I would expect it to work just
fine.
Paul T.