MSDN Jan 2002 with Visual Studio 6?
-
Hey all- For several years now, the standard M.O. for me has been that when a new version of MSDN was released, I would uninstall the previous version, then install the new version, and all would be ok from VS' standpoint. I just installed MSDN for Jan2002 and have been greeted by a "MSDN not installed. Please install MSDN" error from within VisualStudio 6. I chose the same directory and such as I always have, but all of a sudden VS isn't finding it. Presumably it *should* work with 6, as I have found nothing in the documentation to say that it doesn't work, but perhaps I have to fiddle with the registry to have VS find it? Thanks for any info, Ron
-
Hey all- For several years now, the standard M.O. for me has been that when a new version of MSDN was released, I would uninstall the previous version, then install the new version, and all would be ok from VS' standpoint. I just installed MSDN for Jan2002 and have been greeted by a "MSDN not installed. Please install MSDN" error from within VisualStudio 6. I chose the same directory and such as I always have, but all of a sudden VS isn't finding it. Presumably it *should* work with 6, as I have found nothing in the documentation to say that it doesn't work, but perhaps I have to fiddle with the registry to have VS find it? Thanks for any info, Ron
It is my understanding that from Jan 2002, MSDN will only intergrate with Visual Studio 7 and not version 6. If you want Version 6 integration you''ll need to keep October 2001 installed. Michael :-)
-
Hey all- For several years now, the standard M.O. for me has been that when a new version of MSDN was released, I would uninstall the previous version, then install the new version, and all would be ok from VS' standpoint. I just installed MSDN for Jan2002 and have been greeted by a "MSDN not installed. Please install MSDN" error from within VisualStudio 6. I chose the same directory and such as I always have, but all of a sudden VS isn't finding it. Presumably it *should* work with 6, as I have found nothing in the documentation to say that it doesn't work, but perhaps I have to fiddle with the registry to have VS find it? Thanks for any info, Ron
Welcome to the fucking world of .NET. You have to stick with the Oct 2001 MSDN in order to use it with VC 6. "We're telling you where you will go today." -- Microsoft --Mike-- "Everyone has figured out what 'service pack' really means, so they had to go and change the language. Perhaps this is what Bill was talking about in the 'security is top priority' letter." -- Daniel Ferguson, 1/31/2002 My really out-of-date homepage Sonork - 100.10414 AcidHelm Big fan of Alyson Hannigan.
-
Hey all- For several years now, the standard M.O. for me has been that when a new version of MSDN was released, I would uninstall the previous version, then install the new version, and all would be ok from VS' standpoint. I just installed MSDN for Jan2002 and have been greeted by a "MSDN not installed. Please install MSDN" error from within VisualStudio 6. I chose the same directory and such as I always have, but all of a sudden VS isn't finding it. Presumably it *should* work with 6, as I have found nothing in the documentation to say that it doesn't work, but perhaps I have to fiddle with the registry to have VS find it? Thanks for any info, Ron
I always run a seperate instance of MSDN rather than use it from VS.
-
Hey all- For several years now, the standard M.O. for me has been that when a new version of MSDN was released, I would uninstall the previous version, then install the new version, and all would be ok from VS' standpoint. I just installed MSDN for Jan2002 and have been greeted by a "MSDN not installed. Please install MSDN" error from within VisualStudio 6. I chose the same directory and such as I always have, but all of a sudden VS isn't finding it. Presumably it *should* work with 6, as I have found nothing in the documentation to say that it doesn't work, but perhaps I have to fiddle with the registry to have VS find it? Thanks for any info, Ron
-
I installed new version of .Net last night,and MSDN was part of it,and many article is updated and changed.I think for VC++6 it is better to use old version of MSDN Mazy
This is a post I put round work today re this: "Dear All, Be aware that the new MSDN Jan 2002 collection does not work with visual studio 6 (F1 for example produces an error). A quick investigation reveals that MS have changed their help system (again) - it now uses the: C:\Program Files\Common Files\Microsoft Shared\Help\dexplore.exe 'Document Explorer' to launch the collection. Since this is significantly different from .chm files and suchlike it ain't gonna work for VS6. Their may be a way to hack around this - the collection is nominally launched through VS via an intermediary DLL (vshelpui.dll - i think) and checks the following key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTML Help Collections Of interest is this - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTML Help Collections\Developer Collections\0x0409\0x039a1a660 which points at the chm collection for old MSDN installs and tells VC6 where to find it.. Basically MSDN *used* to tell VS6 where to find it and how to launch it. MS couldn't make MSDN compatible with VS6 and/or couldn't be bothered to produce a patch for VS6 to launch things correctly. You can add a tool to the tools menu (really) that launches the new MSDN via the following path "C:\Program Files\Common Files\Microsoft Shared\Help\dexplore.exe" " And yes, it sucks X|
-
This is a post I put round work today re this: "Dear All, Be aware that the new MSDN Jan 2002 collection does not work with visual studio 6 (F1 for example produces an error). A quick investigation reveals that MS have changed their help system (again) - it now uses the: C:\Program Files\Common Files\Microsoft Shared\Help\dexplore.exe 'Document Explorer' to launch the collection. Since this is significantly different from .chm files and suchlike it ain't gonna work for VS6. Their may be a way to hack around this - the collection is nominally launched through VS via an intermediary DLL (vshelpui.dll - i think) and checks the following key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTML Help Collections Of interest is this - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTML Help Collections\Developer Collections\0x0409\0x039a1a660 which points at the chm collection for old MSDN installs and tells VC6 where to find it.. Basically MSDN *used* to tell VS6 where to find it and how to launch it. MS couldn't make MSDN compatible with VS6 and/or couldn't be bothered to produce a patch for VS6 to launch things correctly. You can add a tool to the tools menu (really) that launches the new MSDN via the following path "C:\Program Files\Common Files\Microsoft Shared\Help\dexplore.exe" " And yes, it sucks X|
Ok, me again. Worked out the following. You can install BOTH MSDN Oct and MSDN Jan 2k2 on the same machine - and they work with both VS .NET and VS 6. Yay! We're using a network install here so the total cost of having VS .NET plus two MSDN 'lite' installs is about 1 GIG. Works for me.. Timbo :omg: :rolleyes: :laugh: :rolleyes: :omg: