Welcome to the OpenNETCF Community
First, let us thank you for your time. We hope that this site will provide useful content and resources for Microsoft Windows Embedded developers today and in the future.
Since its inception, OpenNETCF has been all about community. We know that developers alone can create software, but an active developer community is what allows us as developers to leverage what has already been done by others and to strengthen the environment in which we work. The intent of this site is to facilitate that sense of community and to help you as a developer meet your customer's needs, regardless of who that customer might be or what the needs entail.
While OpenNETCF Consulting and the OpenNETCF name itself are strongly associated to the Microsoft .NET Compact Framework, this site is not targeted solely to Compact Framework developers. We hope that this site provides useful content to all developers that are creating software that either runs on or interfaces with Windows Embedded devices, whether they are Windows CE, Windows Mobile or Micro Framework-based.
We provide interactive Forums for the discussion of not just OpenNETCF libraries, but for the discussion of Windows Embedded development in general. A large wealth of knowledge already exists in our current Forums and we will be working to migrate that information here in a sensible way.
We will also be providing articles and white papers on a variety of topics. If you have a request for a topic, or a desire to write an article, feel free to contact us.
We also provide a community-driven Wiki with content that we hope will organically grow to cover the entire Windows Embedded community.
We also are hosting a Subversion source code control server with our well-known shared-source projects. The hope is that by moving to Subversion, the community can be more involved with both fixes and enhancements with very little red-tape from our side to inhibit that innovation. If you have an Open Source Windows Embedded project that you would like us to host let us know and we can work to set that up.
Every month we also host a coding competition for Windows Embedded and Windows Mobile developers. The goal of the competition is to get good examples of Windows Mobile and Windows CE code into the community as a resource and a tutorial. If we happen to give away some cool stuff as we go, all the better.
Lastly we hope you find this site useful and engaging. Let us know what we're doing right as well and what we're not, what kind of content would you like to see more or less of, and if you would like to contribute. Help us make this your one-stop gateway to the world of Windows Embedded and Windows Mobile development knowledge.
The adventure starts right here!
Your Hosts,
OpenNETCF Consulting
What's New
-
Hi, i have finally got rid of that issue which was due to version difference. I am getting the problem, Error 1 The type or namespace name 'DeviceStatusMonitor' could not be found (are you missing a using directive or an assembly reference?) I must mention that i am trying to detect all the attached removable devices through the sample application...
-
Thanks indeed acaliaro , I understand that part but am confused about using OpenNETCF in my project. I have it installed and have added the reference as well. But when i compile my application, i get the following error. Error 1 The type or namespace name 'OpenNETCF' could not be found (are you missing a using directive or an assembly reference...
-
Hi Ali. I think that you have to know how card reader is "connected" to your pda. It should be via rs232, so you have to open the serial port and send / receive command using the smart card protocol. Alessandro
-
Hi, I want to develop an application for my PDA (BIP 1300) which has integrated smart card reader which is ISO 7816 compliant. How can i make use of OPENNETCF for this project. I just need a bit of support to get started to first detect the reader itself and then events like card inserted and removed and finally writing and reading data on the card...
-
Link doesn't work , could you please rewrite the new link