NullPointer exception in System.Data.dll

If You encounter null pointer exceptions on CF 2.0 then this might be caused by insufficient memory. I did experience such random placed exceptions on Pocket PC 2003 device. Each of those exceptions source were somewhere inside System.Data.dll, and was happening at places like inserting (with Rows.InsertAt()) new table row or by assigning new DataSource to DataGrid. After closing some background applications – all was back to normal. For some time now I keep putting more and more code inside try and catch clauses, just to catch such unwanted exceptions.

Advertisement

Windows CE 4.2 Standard SDK

If you desperately are searching for this SDK, then you won’t find it on MSDN, but it still is possible to find it on the internet, one good place for it is: http://www.hpcfactor.com/developer/. I hardly can understand why Standard SDK’s are being withdrawn by Microsoft. I understand that the general idea is to write applications for specific devices and use SDK that is provided by the device developer, but there are companies that does not target specific device and also does not use specific device features. You can find many examples of this situation in Navigation Systems market.

How do you use your linux box?

By that I meant whether you use it normally as a separate operating system on your hard disk, or maybe use it in some fancy way. I would like to describe here how I set up my linux work environment. My main work is under windows os and this wont change in some time, and I really don’t like reseting computer to switch to linux box working in dual boot. The solution was to use VMWare Player with Ubuntu image, I quickly stopped using VMWare window which is from my perspective not user friendly, and installed No Machine client, whose window seamlessly integrates with Windows GUI. Now I can do my programming on linux and windows at the same time. There are still some problems with Samba and accessing windows folders, but I hope to fix it soon.

Visual Studio 2005 and "Unable to start debugging" issue

It’s been long since my last post, but it was due to a lot of work I was into. Today I want to share my experience with the dreadfull error from the post title.

I work under Windows XP sp3, with Visual Studio 2005 sp1, I also installed evc4, and STANDARD_SDK.msi (WCE 5.0 SDK) from MSDN. After that I installed Visual Studio 2008, and this is what causes problems. The only visual difference is that after installation of VS2005 I can see “Windows CE 5.0 Device” and debugging works OK, while after installation of VS2008 I can see “Windows CE Device” and debugging does not work. Unfortunately I have no solution to this other than uninstalling VS2008.