ThomasHillNew Member Posts:
24 Feb 2006 10:43 AM |
|
I have created my own platform and created an SDK for it. But it only shows up in embedded VC++, and not in Visual Studio 2005.
Has anyone used Visual Studio 2005? If so, how do include my own SDK?
Thanks.
|
|
|
|
mikea@logicpd.comNew Member Posts:
25 Feb 2006 02:59 PM |
|
Tom,
Have you tried the LogicPD SDK in the same scenario? (This is listed under the 'Software Development Tools' section under each specific platform's downloads page.
This may help us lead to the problem if it does or doesn't work.
Thanks,
-Mike A.
|
|
|
|
ThomasHillNew Member Posts:
27 Feb 2006 07:24 AM |
|
I've installed the LogicPD SDK, and it does show up for inclusion in the 2005 wizard. And I can build a project as long as I have all the platform configuration correct (or remove all except LPD during the wizard stage).
So now I guess that I need to figure out what components are required for my own image that will build an SDK that can be included in VS2005. I've build SDKs that don't show up when the wizard runs, but can be included later; but they have their own set of problems, which very likely are related to the fact that they aren't being automatically included.
As soon as I figure out what components are needed, I'll post them here. If someone doesn't beat me to it.
Thanks.
|
|
|
|
ThomasHillNew Member Posts:
27 Feb 2006 09:54 AM |
|
I missed Smart Device Authentication Utility (EAC180B3-4DD8-465A-B7EB-9F7056E153E4, SYSGEN_VS_SD_AUTH), since it was listed under .NET Compact Framework and not under .NET Compact Framework 2.0.
I also had to add Windows Networking API/Redirector (SMB/CIFS) (88B461B5-0833-4708-AA2B-8B04E71EC4DD, SYSGEN_REDIR) so that winnetwk.h could be found in order for compiles to work.
|
|
|
|
mikea@logicpd.comNew Member Posts:
27 Feb 2006 09:55 AM |
|
Tom,
Thanks for posting your findings. Great information.
-Mike A.
|
|
|
|
ThomasHillNew Member Posts:
01 Mar 2006 10:00 AM |
|
Follow up:
I successfully ported my MFC application built in eVC++ 4x to VS2005.
To do it I added to my existing PB/CE image:
Smart Device Authentication Utility
Windows Networking API/Redirector (SMB/CIFS)
I also created and included a catalog item that included updated runtimes:
atl80.dll
mfc80u.dll
msvcr80.dll
Of course, I also have a catalog item that includes my .EXE and supporting files, and the registry settings needed to launch my app, etc. I just had to change the postlink.bat file to get the new VS2005 .EXE instead of the old eVC++ one.
Very little had to be done to the application itself to compile in VS2005, and what changes I had to make were minor and obvious.
This doesn't sound like much, and it really isn't -- but I hope it helps others who are just starting out. At times the whole process can seem overwhelming.
|
|
|
|