J
Jamie Macleod
What are people's opinions on OpenNetCF? In what case would it be helpfull
to develop with this framework?
Jamie
to develop with this framework?
Jamie
G
Ginny Caughey [MVP]
Jamie,
The OpenNetCF Smart Device Framework is intended to provide "missing"
functionality for the .NetCF, and although it's packaged as a single
distribution that is easy to install and use, since you have the source code
you can use as much or as little of it as you want. Which parts you need
depend on what you're doing. For example, if you need to do serial
communications, you'll find the serial class very useful. If you're writing
a desktop app in C# or VB.Net, the Rapi class will save you a ton of time.
And if you want to use a LinkLabel or any of the other specialized controls
that .NetCF doesn't have yet, you can use the one from OpenNetCF right from
your Form designer. I think one of the coolest parts is the ApplicationEx
class which gives you the ability to work with Windows messages directly
from a nice wrapper.
I think the best answer I can give you though is to just download and
install it and play with it a bit. The OpenNetCF Help files integrate with
Visual Studio, so you can see what's there that you might want to use. As
the .NetCF matures with version 2, we expect and hope that some of the
classes from OpenNetCF will be replaced with .NetCF workalikes, and we've
tried to make the OpenNetCF interfaces as similar to what the new ones from
Microsoft might be to ease the transition. And of course as OpenNetCF
classes become obsolete (because they would just duplicate functionality
available in future versions of .NetCF) new classes will be added.
BTW if there is functionality you'd like to have that OpenNetCF doesn't yet
provide, let us know from the Feedback link.
HTH,
The OpenNetCF Smart Device Framework is intended to provide "missing"
functionality for the .NetCF, and although it's packaged as a single
distribution that is easy to install and use, since you have the source code
you can use as much or as little of it as you want. Which parts you need
depend on what you're doing. For example, if you need to do serial
communications, you'll find the serial class very useful. If you're writing
a desktop app in C# or VB.Net, the Rapi class will save you a ton of time.
And if you want to use a LinkLabel or any of the other specialized controls
that .NetCF doesn't have yet, you can use the one from OpenNetCF right from
your Form designer. I think one of the coolest parts is the ApplicationEx
class which gives you the ability to work with Windows messages directly
from a nice wrapper.
I think the best answer I can give you though is to just download and
install it and play with it a bit. The OpenNetCF Help files integrate with
Visual Studio, so you can see what's there that you might want to use. As
the .NetCF matures with version 2, we expect and hope that some of the
classes from OpenNetCF will be replaced with .NetCF workalikes, and we've
tried to make the OpenNetCF interfaces as similar to what the new ones from
Microsoft might be to ease the transition. And of course as OpenNetCF
classes become obsolete (because they would just duplicate functionality
available in future versions of .NetCF) new classes will be added.
BTW if there is functionality you'd like to have that OpenNetCF doesn't yet
provide, let us know from the Feedback link.
HTH,
E
Elisa
Hi Jamie,
Personally, I use it as a "How-to" guide. The source files are a great
help in figuring out how to work around several missing features in the
standard .NET CF. If only Microsoft made the source code of the whole
..NET CF available, similar to how Sun makes the source for the Java
Swing components available, and Borland makes the source for their VCL
components available. It would make things like debugging, creating
custom controls, etc. SOOOO much easier.
Thumbs up for the OpenNetCF team for their effort!
Regards,
Elisa
Personally, I use it as a "How-to" guide. The source files are a great
help in figuring out how to work around several missing features in the
standard .NET CF. If only Microsoft made the source code of the whole
..NET CF available, similar to how Sun makes the source for the Java
Swing components available, and Borland makes the source for their VCL
components available. It would make things like debugging, creating
custom controls, etc. SOOOO much easier.
Thumbs up for the OpenNetCF team for their effort!
Regards,
Elisa
C
Chris Tacke, eMVP
I might be biased, but I give it a thumbs up. 
I think many of the pieces are usefult for everyday projects because it
provides easier access to features not in the CF. Can you do without it?
Sure. But you'll likely end up reinventing the work we've done or something
similar.
The SDF itself is actually so large now that there are big sections that
even I've never looked at, but then I've also never used the Sql classes or
the Xml classes in the CF either. Really.
I think many of the pieces are usefult for everyday projects because it
provides easier access to features not in the CF. Can you do without it?
Sure. But you'll likely end up reinventing the work we've done or something
similar.
The SDF itself is actually so large now that there are big sections that
even I've never looked at, but then I've also never used the Sql classes or
the Xml classes in the CF either. Really.
J
Jamie Macleod
Hi Ginny,
Thanks for the input.
Excuse my ignorance. What is the Rapi?
Jamie
Thanks for the input.
Excuse my ignorance. What is the Rapi?
Jamie
K
Kevin Hutchison
Two part essay answer:
1. OpenNETCF SDF
There are some things that you *need* that the compact framework doesn't
provide. My list:
1. Callbacks.
While not part of the SDF, Mr. Feinman provided an excellent start to
providing a callback mechanism for developing in .NETCF
2. MarshalEx
You would either have to write your own, almost verbatim version of this (if
working with API functions) .
3. Audio Support
I first hit OpenNETCf and used the audio libraries for a record and forward
speech recognition project. It saved me a lot of time.
4. HTMLViewer
This provides rich display capability that is not available in any of the CF
distributed controls.
2. OpenNETCF Personnel
Google through the archive of this site and look at the contributions the
folks from OpenNETCf have made. Their responses have been incredibly
helpful for my work and I thank them for it!!
1. OpenNETCF SDF
There are some things that you *need* that the compact framework doesn't
provide. My list:
1. Callbacks.
While not part of the SDF, Mr. Feinman provided an excellent start to
providing a callback mechanism for developing in .NETCF
2. MarshalEx
You would either have to write your own, almost verbatim version of this (if
working with API functions) .
3. Audio Support
I first hit OpenNETCf and used the audio libraries for a record and forward
speech recognition project. It saved me a lot of time.
4. HTMLViewer
This provides rich display capability that is not available in any of the CF
distributed controls.
2. OpenNETCF Personnel
Google through the archive of this site and look at the contributions the
folks from OpenNETCf have made. Their responses have been incredibly
helpful for my work and I thank them for it!!
G
Ginny Caughey [MVP]
Hi Jamie,
Rapi == Remote API. These are functions that allow you do to stuff on the
device from the desktop. For example, CeCreateFile creates or opens a file
on the device from a desktop app whereas CreateFile does that on the
desktop. I also have VO wrappers for these functions if you need them.
Rapi == Remote API. These are functions that allow you do to stuff on the
device from the desktop. For example, CeCreateFile creates or opens a file
on the device from a desktop app whereas CreateFile does that on the
desktop. I also have VO wrappers for these functions if you need them.
M
Maarten Struys, eMVP
As Chris I am a probably a little biased.
The Smart Device Framework is quite large, and contains lots of
functionality. It works perfectly together with the .NET CF and fills in the
white spaces and will continue to do so. Just for day to day work it can be
a huge time saver, you don't have to reinvent the wheel over and over again,
but just go ahead and just SDF. At the same time it is also a great way of
learning a lot about managed code development. Just take a look at the
sources and see how much very cool things are done.
--
Regards,
Maarten Struys, eMVP
PTS Software bv
www.opennetcf.org | www.dotnetfordevices.com
The Smart Device Framework is quite large, and contains lots of
functionality. It works perfectly together with the .NET CF and fills in the
white spaces and will continue to do so. Just for day to day work it can be
a huge time saver, you don't have to reinvent the wheel over and over again,
but just go ahead and just SDF. At the same time it is also a great way of
learning a lot about managed code development. Just take a look at the
sources and see how much very cool things are done.
--
Regards,
Maarten Struys, eMVP
PTS Software bv
www.opennetcf.org | www.dotnetfordevices.com
W
William Ryan eMVP
I'm biased too but I give it the highest rating I can. Like others have
mentioned, it fills in many of the gaps of the CF but there are other really
good reasons too. There are active forums with many people who use it
regularly. The creaters of Opennetcf also work really hard answering
questions. There are walk throughs provided and excellent documentation and
in every instance I can think of, you'll get up and running faster using it
than if you try to figure it out on your own with trial and error. I also
think that 40,000 downloads in such a niche area speaks volumes for how
others feel about it
mentioned, it fills in many of the gaps of the CF but there are other really
good reasons too. There are active forums with many people who use it
regularly. The creaters of Opennetcf also work really hard answering
questions. There are walk throughs provided and excellent documentation and
in every instance I can think of, you'll get up and running faster using it
than if you try to figure it out on your own with trial and error. I also
think that 40,000 downloads in such a niche area speaks volumes for how
others feel about it
J
Jamie Macleod
Thanks everyone for the responses. Were are these "walk throughs" located?
G
Graham McKechnie
Hi Jamie,
As Ginny said, Remote API. If you ever need to do syncing from SqlCe to say
dbfs (or any other format) and vice versa in VO (or any other language),
then Rapi is how you would do it. SqlCe on the smart device works really
well, but most assume it also needs it big brother on the desktop. Ginny's
VO wrappers were really handy on a project I did last year, that had to sync
with dbfs on the desktop. I would guess in many apps, having the desktop
control the sync process can be very useful.
Graham
As Ginny said, Remote API. If you ever need to do syncing from SqlCe to say
dbfs (or any other format) and vice versa in VO (or any other language),
then Rapi is how you would do it. SqlCe on the smart device works really
well, but most assume it also needs it big brother on the desktop. Ginny's
VO wrappers were really handy on a project I did last year, that had to sync
with dbfs on the desktop. I would guess in many apps, having the desktop
control the sync process can be very useful.
Graham
J
Jamie Macleod
Hi Ginny,
Sorry to still be dense, but I can't find the RAPI class. Were is it?
I am doing all new development in .Net, so I probably won't need the VO
wrappers. I'll let you know though.
Jamie
Sorry to still be dense, but I can't find the RAPI class. Were is it?
I am doing all new development in .Net, so I probably won't need the VO
wrappers. I'll let you know though.
Jamie
C
Chris Tacke, eMVP
G
Ginny Caughey [MVP]
Hi Jamie,
I see that Chris has replied to you. Let us know if you have any problems
finding it.
I see that Chris has replied to you. Let us know if you have any problems
finding it.
J
Jamie Macleod
Thanks you two. It was right in front of my face.
N
Nonymous
Elisa said:
....and how Microsoft itself makes the source code to MFC available.