||
|
 Tuesday, March 02, 2004
Using the same compiled assmbly on Desktop and Compact Frameworks
A recent Mobile Minute had a link to some stuff by Kyle Cordes on the Compact Framework. This short piece by Kyle gives a great once over lightly of CF development and covers off many of the questions that always seem to raise their head in any discussion of CF development. I had a few of them the other day in my web cast *plugs web cast*. Kyle even includes some very interesting BAT file instructions for building CF applications automatically... very cool this.
I'll add just a couple of quick points to some of the stuff there.....
“You can't run the same EXE/DLL on both the CF and desktop .NET“
Actually you can. With DLLs you can run the same DLL on a device as on a desktop. If your DLL is written to to only use the subset of the framework supported by both platforms. Alternativly with intelligent exception handling you can get away with making some platform specific calls too.
A great example of a .NET assembly that works fine on both platforms is SharpZipLib
http://www.icsharpcode.net/OpenSource/SharpZipLib/Default.aspx
“If you include both a desktop and CF project in the same ?Solution?, and you build/run the desktop app, VS.NET will build and deploy (!) the CF project. “
If you right click the VS.NET solution and choose 'configuration manager' you can turn CF project deployment on and off on a project by project basis.
“Many CF API calls throw/return much less helpful error messages than the corresponding desktop .NET calls; a lot of descriptive error text was left out to keep the CF small.“
They were'nt completely removed. They are just held in a separate assembly that you need to include called System.SR.dll. Always worth having a reference to this in ya project while debugging.
.NET | Mobility|Tuesday, March 02, 2004 4:55:26 AM UTC||Tracked by:
"online poker cash bonus" (online poker cash bonus) [Trackback]
"blackjack" (blackjack) [Trackback]
|
|
|