Two different install locations?
First of all, big thanks to all of you who responded to my post last week re the poor download stats for the SDK. I really appreciate all your responses, and I've already used them in one meeting so far. I promise to get back to you later this week on my investigation of Microsoft and BitTorrent. I know we don't use that technology, but I'm curious what the specific corporate reason for that is. I wanna know what we do to mirror our content around the world, and what the recommended ways are to handle large downloads. I'll post again on this topic when I have a few more answers.
I wanted to get your feedback on something else our team has been debating: the question of where exactly to install content.
Background: In Windows Vista, files that can be modified have to be installed to a location outside of the Program Files directory. But the SDK installs to Program Files. So where do we put our samples, which are created to be modified? The answer we came up with was to post them to \Documents and Settings\All Users\My Documents, which then would make them available for each member of a team to use.
Does that concept make sense?
Second issue, relaated to that, is that we're going to add Custom Install Locations for RC1. If you have the ability to change one location, do you want to change another? If so, how do you think the screen should look? If I'm using this blog software right, a mockup of this options screen is attached below. What do you think of it?
No hype - I'm using this data to help drive these decisions. Thanks in advance.
