Suggestions for Dev Setup
-
I'm trying to decide which is the best way to go about setting up my dev machine with VisualStudio and eMbeddedVisualTools. I do development work for both the desktop and PocketPC environments. Currently, I have my trustly old VisualStudio6 (sp5 i think) with MSDN (VS6 version), along with eMbeddedTools3 (PPC2k2 SDK). Maybe I'm being too picky here, but I really like having my MSDN integrated into my IDE, so that when I press F1, it loads up the help system. I've got this working for VisualStudio6, but I don't have it working for eVT3. Sure, I can live without the integration, but if I can fix it, then, obviously, I'd much rather do it that way. :-D So, I appeal to the CP masses: what is the best way that I should setup my system so that I can develop for desktop and PPC, with both having integrated MSDNs. I'm not doing ANY kinda of .NET related development (desktop or PocketPC), and don't plan on doing it in the future (just yet :-D), so that's not a factor. Currently, I have this software: VisualStudio6 VS.NET (not VS.NET 2003) eMbeddedTools 3 (with PPC2002 SDK) eMbeddedTools 4 (.NET version, with sp2) MSDN (Visual Studio 6 version (it's pre Oct2001) MSDN (VS.NET version) MSDN (Apr2003) Alternatively, if anyone can just tell me how to get MSDN (any version) to integrate into eVT3, then I could save myself the hassle of changing my current setup. :-D I'm just a poor starving Kraft macaroni-and-cheese-eating student, so I can't really afford to buy MSDN Universal (which I assume can fix all this easily). Thanks! I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]
-
I'm trying to decide which is the best way to go about setting up my dev machine with VisualStudio and eMbeddedVisualTools. I do development work for both the desktop and PocketPC environments. Currently, I have my trustly old VisualStudio6 (sp5 i think) with MSDN (VS6 version), along with eMbeddedTools3 (PPC2k2 SDK). Maybe I'm being too picky here, but I really like having my MSDN integrated into my IDE, so that when I press F1, it loads up the help system. I've got this working for VisualStudio6, but I don't have it working for eVT3. Sure, I can live without the integration, but if I can fix it, then, obviously, I'd much rather do it that way. :-D So, I appeal to the CP masses: what is the best way that I should setup my system so that I can develop for desktop and PPC, with both having integrated MSDNs. I'm not doing ANY kinda of .NET related development (desktop or PocketPC), and don't plan on doing it in the future (just yet :-D), so that's not a factor. Currently, I have this software: VisualStudio6 VS.NET (not VS.NET 2003) eMbeddedTools 3 (with PPC2002 SDK) eMbeddedTools 4 (.NET version, with sp2) MSDN (Visual Studio 6 version (it's pre Oct2001) MSDN (VS.NET version) MSDN (Apr2003) Alternatively, if anyone can just tell me how to get MSDN (any version) to integrate into eVT3, then I could save myself the hassle of changing my current setup. :-D I'm just a poor starving Kraft macaroni-and-cheese-eating student, so I can't really afford to buy MSDN Universal (which I assume can fix all this easily). Thanks! I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]
I don't think you can get MSDN Library to integrate into eVC. The device-specific help is only available in the 'Welcome to Windows CE' stuff, which ought to pop up in eVC when you press F1. Even if you have MSDN Universal. I still refer to MSDN Library because the help is more detailed (and often more accurate) for the desktop SDK than for eVC 3.0. 4.0 looks a little better but I haven't really used it yet. -- Mike Dimmick
-
I don't think you can get MSDN Library to integrate into eVC. The device-specific help is only available in the 'Welcome to Windows CE' stuff, which ought to pop up in eVC when you press F1. Even if you have MSDN Universal. I still refer to MSDN Library because the help is more detailed (and often more accurate) for the desktop SDK than for eVC 3.0. 4.0 looks a little better but I haven't really used it yet. -- Mike Dimmick
Mike Dimmick wrote: to pop up in eVC when you press F1 I just get the error message: "The MSDN collection does not exist. Please reinstall MSDN" popping up twice (2 message boxes). Mike Dimmick wrote: I don't think you can get MSDN Library to integrate into eVC Well.. that just sucks. X| Thanks for the help anyways. I prefer to wear gloves when using it, but that's merely a matter of personal hygiene [Roger Wright on VB] Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. [Rich Cook]