N
Norbert Unterberg
We have a C# project for a PDA (Windows Mobile 5.0 Pcoekt PC, using
VS2008) where we create some utiity classes that should be used both for
the PDA and for the "real" Windows XP platform.
Currently, we create a C# smart device class library project. When
building a PC application, we just reference the PDA class library.
Visual studio warns about possible unexpeced results but allows us to do
it, and the resulting application does work.
My questions: What are the risks and the drawbacks? What is the correct
way? We have not found a way to set different target platforms as build
configuration. The only other solution we found is to create a second
project and import the same set of soure files, but there should be a
better way, shouldn't it?
One drawback we found is that VS does not allow to create PC bases unit
tests for the pocket pc class library.
Any ideas and suggestions?
Norbert
VS2008) where we create some utiity classes that should be used both for
the PDA and for the "real" Windows XP platform.
Currently, we create a C# smart device class library project. When
building a PC application, we just reference the PDA class library.
Visual studio warns about possible unexpeced results but allows us to do
it, and the resulting application does work.
My questions: What are the risks and the drawbacks? What is the correct
way? We have not found a way to set different target platforms as build
configuration. The only other solution we found is to create a second
project and import the same set of soure files, but there should be a
better way, shouldn't it?
One drawback we found is that VS does not allow to create PC bases unit
tests for the pocket pc class library.
Any ideas and suggestions?
Norbert