Who actually has the MSDN Documentation installed?

D

Denaes

Senior Contributor
Joined
Jun 10, 2003
Messages
956
I normally do... but at work I realized that the interface is kinda lacking in the search capabilities I want and takes longer to load than a Google Query.

Google gets me what I want faster... and without taking up so much hard drive space. Plus it's the updated MSDN without me having to install updates onto my computer.

I say to myself "What if I don't have a connection to the internet... and happen to really need the MSDN? Not bloody likely I'm thinking. So I'm giving it a pass this time.
 
Denaes said:
I normally do... but at work I realized that the interface is kinda lacking in the search capabilities I want and takes longer to load than a Google Query.

Google gets me what I want faster... and without taking up so much hard drive space. Plus it's the updated MSDN without me having to install updates onto my computer.

I say to myself "What if I don't have a connection to the internet... and happen to really need the MSDN? Not bloody likely I'm thinking. So I'm giving it a pass this time.
Click to expand...

I've recently heard the same "there's no need for locally installed MSDN as Google way faster" thing recently. I've been using MSDN since 1998 and although internet search engines have changed my search habits drastically I reckon there's a still few points to have it locally installed:

*I've got quite fast broadband connection but local MSDN library is still a quickest way to do a lookup for a method prototype (intelliscence doesn't give me all the information I usually need), list of methods defined by class or implemented interfaces.

*When I'm searching for articles in MSDN I'm quite sure that the information I would find be from technology experts.

*MSDN library is reasonable well structured and carefully maintained - hence providing good "surf-explore" experience.

*You've made a good point about not having internet connection or if it became too slow to be usable.

*I've got 0.75 of terabyte space on my PC :cool: and half of this space is still free.

Considering all above, I don't think that I'm going to give up installing local MSDN library for at least two coming years.
 
Just to clarify, I'm not talking about using other peoples documentation, but using the MSDN Documentation. This is written & maintained by Microsoft, not someone else.

Microsoft has the most up to date version of the MSDN Documentation online and fully searchable. It's the same stuff you have on your PC, only more up to date (unless you have a MSDN subscription and apply all the updates monthly) and you can take advantage of Googles superior search engine.

I'm just noting that having access to both at work, I use the online version exclusvely. It also helps that I use Firefox and I can just start typing on a page and it starts searching for that text. So when it came time last night, I figured why spend the time/space installing when I'm not going to use it.

I hope thats a bit more clear.
 
Last edited:
The MSDN interface online is poopy. It is slow and klunky. Even if you just view one page. It doesn't work with the mouse wheel in FireFox and the text renders incorrectly: some times text overlaps or doesn't scroll with everything else. The index on the left is useless. Not to mention, it doesn't remember my language filter settings.

Besides all that, this is how I use MSDN: When I need more info on a specific class, function, or keyword I will use MSDN. I am not lacking in hard drive space, and the locally installed MSDN documentation is easy and fast, except for the search. If I need to search I go to the object browser or google, depending on what I'm looking for. The fact is that I don't find myself googling for .Net documentation very often though.

To each, his own. If you like MSDN online, that's fine, but it doesn't fulfill my personal programming needs.
 
I've got MSDN installed locally only because sometimes I need to do development without an internet connection while at client sites. Google is sort of hard to use when you don't have an internet connection. ;) The MSDN browser is kind of annoying, though. And, as marble_eater put, the online MSDN is extremely weak -- slow and clunky to put it mildly.

This is sort of related... http://www.codinghorror.com/blog/archives/000500.html
 
Back
Top