Quote:
Originally Posted by obrienj
Cableguy,
Let' start over.
|
Yes, let's...
Quote:
An example:
I want to build a B4P library DLL that provides .Net Event processing. Using their C++ names, I will use the .Net equivalent of CreateEvent, SetEvent, ResetEvent, WaitForMultipleObjects, and CloseHandle.
All of those methods exist in both .Net for the PC and .Net CF (both 2.0) and have the same parameters.
My assumption, which could be very wrong, is that I can write one piece of source code that provides the functionality for creating an event, waiting for event to be posted, posting the event, and destroying the event.
In the simpliest case, I would have to compile that source twice, once for the PC and once for the device, in each case creating a DLL with the same name.
So far, is my assumption correct?
|
Yes, very.
As I sayed before, any DLL targeting the Compact(ed) FrameWork, WILL run on bothe platforms.
Quote:
If so, how do I manage the source file, the two output files, and the project file?
Or, is the simpliest way to simply treat them as two different projects (one for the PC and one for the device) and manually keep the source the same in both.
|
The only Problem I forsee, is that Compilation wise, the resulting EXE file ARE diferent...
So, Yes, Two (or more, since B4PPc has added support for Smartphone compilation) diferent EXE would have to be created, trough compilation on the IDE, targeting the especific platform as needed...Still all the other files (i.e. DLL, Txt, etc) would be the same....
In some cases, especially with the legacy and forcedQVGA Mode compiling, some extra files may be created during compilation.
The souce file (.spb) does Not need to be provided with the compiled project...unless of course, you make it available for your own purposes.