Hate new MSDN search
-
A week ago I provided little help to my friend on some ASP.NET project. We were sitting in restaurant and working on his laptop after lunch while suddenly I needed more information on impersonation (how to specify user for impersonation). We didn't had any Internet connection so I almost gave up and said: "I'll google-search that first thing when I come home and send you - it's just one line in web.config". But then I remembered - he had Visual Studio .NET 2003 and MSDN library for that version... and in few moments I found what I needed using old MSDN search box. I was delighted that could use MSDN library v2003 again. * * * Point is - ____I HATE____ MSDN LIBRARY THAT COMES WITH VS.NET 2005. AND I HATE www.msdn.com. And I often wonder if I'm just plain stupid for not knowing to use it... or the guys working on it are real talents to screw things that worked fine. Any comment? Any suggestion? Any proposition on how to better search within MSDN Library? Or to just give up and use Google? P.S. I love rant (link) from this guy :)
-
A week ago I provided little help to my friend on some ASP.NET project. We were sitting in restaurant and working on his laptop after lunch while suddenly I needed more information on impersonation (how to specify user for impersonation). We didn't had any Internet connection so I almost gave up and said: "I'll google-search that first thing when I come home and send you - it's just one line in web.config". But then I remembered - he had Visual Studio .NET 2003 and MSDN library for that version... and in few moments I found what I needed using old MSDN search box. I was delighted that could use MSDN library v2003 again. * * * Point is - ____I HATE____ MSDN LIBRARY THAT COMES WITH VS.NET 2005. AND I HATE www.msdn.com. And I often wonder if I'm just plain stupid for not knowing to use it... or the guys working on it are real talents to screw things that worked fine. Any comment? Any suggestion? Any proposition on how to better search within MSDN Library? Or to just give up and use Google? P.S. I love rant (link) from this guy :)
Just Google. It will return a result much faster and chances are that what you get is more related to what you asked for than if you used the "native" MSDN search Roswell
"Angelinos -- excuse me. There will be civility today."
Antonio VillaRaigosa
City Mayor, Los Angeles, CA -
A week ago I provided little help to my friend on some ASP.NET project. We were sitting in restaurant and working on his laptop after lunch while suddenly I needed more information on impersonation (how to specify user for impersonation). We didn't had any Internet connection so I almost gave up and said: "I'll google-search that first thing when I come home and send you - it's just one line in web.config". But then I remembered - he had Visual Studio .NET 2003 and MSDN library for that version... and in few moments I found what I needed using old MSDN search box. I was delighted that could use MSDN library v2003 again. * * * Point is - ____I HATE____ MSDN LIBRARY THAT COMES WITH VS.NET 2005. AND I HATE www.msdn.com. And I often wonder if I'm just plain stupid for not knowing to use it... or the guys working on it are real talents to screw things that worked fine. Any comment? Any suggestion? Any proposition on how to better search within MSDN Library? Or to just give up and use Google? P.S. I love rant (link) from this guy :)
mikker_123 wrote:
Point is - ____I HATE____ MSDN LIBRARY THAT COMES WITH VS.NET 2005. AND I HATE www.msdn.com. And I often wonder if I'm just plain stupid for not knowing to use it... or the guys working on it are real talents to screw things that worked fine.
It's an ongoing complaint - ongoing for years, in fact - back to Visual Studio 6. The general rule is: Each new version of MSDN Help is worse than the previous.
Kevin