#### Archived

This topic is now archived and is closed to further replies.

# DirectX9.0b Summer Update [rant]

This topic is 5056 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

At first I didn't want to download it because of its Managed DirectX bug. Then, Microsoft released a patch that is supposed to fix this bug. So I was convinced to download and install it. After spending 10+ hours downloading that beast with my 56k, I uninstalled my DirectX9.0 SDK and installed the Summer Update. After the installation is done, Managed DirectX files (still) can't be found on my .NET references. Tried to include them manually, it can't find "dependencies." I thought the patch is supposed to fix it. In addition to that, I can't open all C# sample project files because they are in VS.NET 2003 format, and I use VS.NET 2002. I was outraged. I uninstall the Summer Update, and reinstall the good old DirectX9.0. It turned out that Summer Update ruined my system that now both SDKs didn't work. I kept installing/uninstalling both SDKs, wasting my precious 3 hours, hoping that one of them would work. Too bad the attempts were unsuccesful. Now I don't know how to fix my system so that I can work on Managed DirectX once again. I don't want to reformat my Windows or reinstall VS.NET because it takes hours to complete, and I have to download those security fixes again with my 56k. Since now I can no longer test drive Managed DirectX and the so-promising C# for my next game, and my system is now ruined, hateToMicrosoft += REALLY_REALLY_LARGE_NUMBER; Let's see if I can restore my system... edit: I think I can call myself lucky. The System Restore checkpoint was yesterday. Thanks a LOT, Microsoft! [edited by - alnite on October 15, 2003 5:05:29 PM]

##### Share on other sites
why did you remove your previous version of directx... Summer is an update not a whole new package..?

Do some searching before downloading the whole thing next time. And my advice I guess is start clean.. that''s the easiest way to get rid of all the crap that gets on your computer after a while.. though really it often is the step taking the longest time.

##### Share on other sites
oops did an error. Sorry.. yeah stupid microsoft not offering a patch for summer from normal. Sorry again. This was a patch to fix the summer update.. sorry again

##### Share on other sites
Personally, I love 9.0b because of all the HLSL tutorials/samples/docs it comes with. Now I can finally start doing some of that stuff. But yea, I am using the C++ version, not C#.

##### Share on other sites
I agree with the last post. When I started with HLSL there was almost no documentation. Still, I wouldn''t download over my existing SDK just for the docs...

##### Share on other sites
Yeah, I wouldn''t bother with the bug if I decided to use C++. It''s only for Managed DirectX anyway. HLSL and other documentations they included in the SDK are sweet. More samples too. But I decided to give C# a try because I want to make games fast, instead of twiddling pointers and header files.

Strange, C++ projects can be opened with VS.NET 2002, but not C# ones even though all of them have .sln extension. It is like Microsoft is saying:
"O'' loyal customers, thou shalt upgrade to VS.NET 2003 and give us your dollar bills. We wouldn''t provide you supports if you continue using VS.NET 2002."

##### Share on other sites
You could create a new project and add the files yourself...

Stay Casual,

Ken
Drunken Hyena

##### Share on other sites
I''m using Visual Studio .NET 2002 as well, and also downloaded the Summer 2003 release. I figured the references weren''t showing up because they were compiled in .NET 1.1. At least, that''s what it seems. They show up just fine in the references for Borland C#Builder. For using VS .NET, I simply hit Browse and include them myself, and everything seems to work just fine.

##### Share on other sites
I had the same problem. Just go into the folder where you unzip the setup files. Browse into "Developer Runtime/Managed DirectX" and then either Debug or Retail depending on which you want installed. For some reason the managed stuff is not installed by the installer!! Very crazy but this fixed it for me. Good luck.

##### Share on other sites
Clicky to see how I feel.

WiseElben.com | My Journal | My Profile

Projects: nMagic - Voted #1 in DOSGamesWeekly, a nondiversial DOS lover magazines.

[edited by - GameDev Staff on September 27, 1989 9X:58:97 XMS] For violating Article 43 Page 456 Paragraph 251 Line .042]

##### Share on other sites
quote:
Original post by Anonymous Poster
I had the same problem. Just go into the folder where you unzip the setup files. Browse into "Developer Runtime/Managed DirectX" and then either Debug or Retail depending on which you want installed. For some reason the managed stuff is not installed by the installer!! Very crazy but this fixed it for me. Good luck.

Just tried that.. still not showing up. Oh well.

##### Share on other sites
yeah... i just did the same too..
not showing up,

pent

btw: wehre would the path to the DLL''s be?

##### Share on other sites
If installed, look into your windows folder, Microsoft.NET. There should be a Managed DirectX folder now. I even have two versions in there, v9.00.0900 and v9.00.1126. In any case, just reference those .dll in your projects, and everything will be set.

##### Share on other sites
found it (on another post) thanks anyways

##### Share on other sites
quote:
Original post by alnite
edit: I think I can call myself lucky. The System Restore checkpoint was yesterday. Thanks a LOT, Microsoft!

Your thanks are justified since System Restore is designed to checkpoint whenever you do an install.

As for your other post, I was using VS2002 with C# projects as recently as this past February...