msdn.microsoft.com will be the end of me
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
... and add to that, all of the examples are in Visual Basic!! Vacancy for signature; Apply within.
-
... and add to that, all of the examples are in Visual Basic!! Vacancy for signature; Apply within.
Ben Wootton wrote: Vacancy for signature; Apply within. Within where??? :omg:
"Never tell people how to do things. Tell them what to do, and they will surprise you with their ingenuity." - General George S. Patton Jr.
-
Ben Wootton wrote: Vacancy for signature; Apply within. Within where??? :omg:
"Never tell people how to do things. Tell them what to do, and they will surprise you with their ingenuity." - General George S. Patton Jr.
Not sure really now you mention it - :confused: My first email client used to fill in the subject with "vacancy for subject, apply within" if you didnt enter a subject- I thought it was funny, but thats my odd sense of humour i guess- Ben Vacancy for signature; Apply within.
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
Even better is when Microsoft provides no examples and very little documentation for a certain piece of technology. I am reverse engineering Pocket PC's new Outlook Client .... I can feel an article coming on ... Regards Ray "Je Suis Mort De Rire"
-
... and add to that, all of the examples are in Visual Basic!! Vacancy for signature; Apply within.
Yeah but VB programmers need examples. Us C++ programmers are tough and don't need our hand holding :-D MSDN had become a bit of a pain to search recently, I also tend to make google my first port of call. Michael :-)
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
-
Yeah but VB programmers need examples. Us C++ programmers are tough and don't need our hand holding :-D MSDN had become a bit of a pain to search recently, I also tend to make google my first port of call. Michael :-)
Michael P Butler wrote: Yeah but VB programmers need examples :laugh: :laugh: :laugh: :laugh: Not only that, but VB "programmers" need sample applications ! Cheers, Simon "I get paid for my brain and my thinking in several obscure worlds", Olli, The Lounge
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
www.google.com/microsoft Cheers Kannan
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
Ben Wootton I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. I get the Windows CE thing direct from MSDN. Really bizarre. It happens all the time. John Carson
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
When you are searching with Google, do you search just microsoft.com? I've done that in the past and it seems to work pretty well. You can search just a domain or set of domains through the advanced search. I *hate* the fact that Windows CE documents always show up! This is a problem even in the MSDN that works as Visual's F1 help system... when I hit F1 on a function, there are usually two entries that show up... one for the regular function, one for WinCE, but because the length of the listbox showing those topics is too small, it cuts off the "Windows CE" part at the end of the description so I never know which one I'm going to get! For these reasons alone, I am against Windows CE. :) recursive adj. See RECURSIVE.
-
When you are searching with Google, do you search just microsoft.com? I've done that in the past and it seems to work pretty well. You can search just a domain or set of domains through the advanced search. I *hate* the fact that Windows CE documents always show up! This is a problem even in the MSDN that works as Visual's F1 help system... when I hit F1 on a function, there are usually two entries that show up... one for the regular function, one for WinCE, but because the length of the listbox showing those topics is too small, it cuts off the "Windows CE" part at the end of the description so I never know which one I'm going to get! For these reasons alone, I am against Windows CE. :) recursive adj. See RECURSIVE.
I guess the inurl feature of google is one way around it, and you can also use - to exclude features: e.g: +"mapi" +inurl:msdn.microsoft -"windows ce" www.google.com/microsoft is good too, thanks for that. I just think there will be a knack to using msdn! :-D Vacancy for signature; Apply within.
-
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
Ben Wootton wrote: and its sooooo sloooowwwwwww. That's a feature by design. :) Jeremy L. Falcon "The One Who Said, 'The One Who Said...'" Homepage : Sonork = 100.16311
01000010011011110110001000100000011101110110000101110011
00100000011010000110010101110010011001010010111000000000 -
I always seem to go through the following when searching for something on msdn: 1. Search for hours with no luck. Get seemingly random search results. 2. Try google instead, but find an msdn page which sounds perfect. 3. Go to the page, find it is actually a page about Windows CE. 4. Give up on whatever I was trying to do originally. 5. Start something else and end up back at msdn.microsoft.com 6. Find what I was looking for in the first place. I know they must have millions of documents on there, but something is not right with it ;P and its sooooo sloooowwwwwww. :(( Ben Vacancy for signature; Apply within.
I love how searching for "SQL Server 7" doesn't return anything, but "SQL Server 7.0" does. Theoretically, shouldn't you be supposed to get *more* hits if your search string is shorter? That's how everybody's search engine works...'cept for MS, of course... I forget where I was exactly...I was trying to determine on which MSDN CD SQL Server 7 SP3 was supposed to be on (which I still haven't determined). Had to go through the 130+MB download, despite being a Universal subscriber...
-
When you are searching with Google, do you search just microsoft.com? I've done that in the past and it seems to work pretty well. You can search just a domain or set of domains through the advanced search. I *hate* the fact that Windows CE documents always show up! This is a problem even in the MSDN that works as Visual's F1 help system... when I hit F1 on a function, there are usually two entries that show up... one for the regular function, one for WinCE, but because the length of the listbox showing those topics is too small, it cuts off the "Windows CE" part at the end of the description so I never know which one I'm going to get! For these reasons alone, I am against Windows CE. :) recursive adj. See RECURSIVE.
Hey, so I am not the only one bitten by that. And if you have installed Visual Studio 6.0 Visual Studio Net, MSDN and the Plattform SDK you have the same docs in several places. Even with todays HD sizes this is a waste of HD space. I am a signature virus! Help me spread and copy me to your sig! Ooops I am infected
-
When you are searching with Google, do you search just microsoft.com? I've done that in the past and it seems to work pretty well. You can search just a domain or set of domains through the advanced search. I *hate* the fact that Windows CE documents always show up! This is a problem even in the MSDN that works as Visual's F1 help system... when I hit F1 on a function, there are usually two entries that show up... one for the regular function, one for WinCE, but because the length of the listbox showing those topics is too small, it cuts off the "Windows CE" part at the end of the description so I never know which one I'm going to get! For these reasons alone, I am against Windows CE. :) recursive adj. See RECURSIVE.
I fixed this by deleting the wce*.chi index files in the MSDN directory. Now the WCE documentation doesn't show up when I search.