[.net] Install which windows compoents before install Visual Studio 2003
I must install which Windows Components before I install Visual Stduio 2003?
I insert the CD1 of VS2003, it always tell me to restart computer.
The restart message is as below:
http://www.game.csie.ndhu.edu.tw/~akira/Else/vs2003error_eng.JPG
[Edited by - akira32 on February 22, 2008 3:53:43 AM]
2003 is also getting kind of old now. You can get the 2008 express edition for free; that plus the PlatformSDK should get you all the functionality you're likely using in 2003 but with a newer, more supported and more standards compliant application.
Just google: "2008 express edition" and "PlatformSDK" respectively for download links.
-me
Just google: "2008 express edition" and "PlatformSDK" respectively for download links.
-me
If memory serves me right, the vs.net IDEs tell you what dependencies have to be installed. So if it just keeps telling you to restart after supposedly installing them, something sounds broken.
My OS is xp home edition version 2002 SP2.
There is no IIS in my computer, so the vs2003 CD does not tell me the requirement of IIS and Frontpage 2000 Server Extensions. It just said there is some thread run, you must restart computer in chinese.
There is no IIS in my computer, so the vs2003 CD does not tell me the requirement of IIS and Frontpage 2000 Server Extensions. It just said there is some thread run, you must restart computer in chinese.
Hm, I'm presuming that because you want to debug shaders that you've already got an engine to employ them in...which would imply that you've already got a development environment?
Anyways, the reason only VS.NET does this sort of thing is because MS doesn't want you to do it this way anymore. I was going to suggest PIX (or FX composer to be honest) -- and I remember a certain thread you ought to read: Debugging HLSL shaders in VS 2005. The title was the original problem -- suggestions are posited in the thread.
hth,
~Shiny
[EDIT] I might as well give you the link, save some reading. Check out PIX here
Anyways, the reason only VS.NET does this sort of thing is because MS doesn't want you to do it this way anymore. I was going to suggest PIX (or FX composer to be honest) -- and I remember a certain thread you ought to read: Debugging HLSL shaders in VS 2005. The title was the original problem -- suggestions are posited in the thread.
hth,
~Shiny
[EDIT] I might as well give you the link, save some reading. Check out PIX here
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement