Sign in to follow this  

[.net] Managed DirectX distribution..

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

Guest Anonymous Poster

On a Side note,

Remeber that if the user already has the .net frame work installed, and then instals the April 2005 Redist' the MDX System is automaticly installed.

I have seed hacks where people have included the MDX Assemblies with there packaged application. When doing this they transfer the Assemblies to the root directory of there application, I would try and stay away from this and let the main redist' system handle it.

Share this post


Link to post
Share on other sites
Quote:
then instals the April 2005 Redist' the MDX System is automaticly installed.


Yes, but that's the whole problem. Users (sans those on uber-fast internet) don't want to download a 24meg .NET Framework and then a ~34meg MDX redist.

Share this post


Link to post
Share on other sites
The .NET Framework install size is becoming less and less of a concern. According to March 2005 stats (available at http://blogs.msdn.com/scottwil/archive/2005/03/09/391199.aspx):

More than 120M copies of the .NET Framework have been downloaded and installed using either Microsoft downloads or Windows Update
More than 85% of new consumer PCs sold in 2004 had the .NET Framework installed
More than 58% of business PCs have the .NET Framework preinstalled or preloaded
Every new HP consumer imaging device (printer/scanner/camera) will install the .NET Framework if it’s not already there – that’s 3M units per year
Every new Microsoft IntelliPoint mouse software CD ships with the .NET Framework

So while there is a small percentage of users that you have to worry about who don't have the Framework at all, the biggest issue that you're facing is getting people the April 2005 DirectX runtimes.

That being said, it sounds like you're going to be distributing over the Internet. If the visitor to your site is using Internet Explorer, you can check the browser string to see if the visitor has the .NET Framework installed and direct them to either a larger install (.NET+DX9+Title) or the smaller install (DX9+Title).

If they are not using Internet Explorer, it's best to assume the worst and point them to the larger install.

Given the choice, most people would rather download 100Mb all at once instead of 3 33Mb files in bursts.

Share this post


Link to post
Share on other sites

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

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this