wtf wrong with msdn in .net 2003? I can't find stuff I _know_ is there..

  • Thread starter Thread starter silangdon
  • Start date Start date
S

silangdon

<rant> I've spent 30 minutes trying to find information on the CString
left function. in VC6 you get MFC class & a complete list of
operators. And an overview. This seems to be entirely absent or hard
to find.

I _hate_ it when software gets worse, not better.

</rant>
 
<rant> I've spent 30 minutes trying to find information on the CString
left function. in VC6 you get MFC class & a complete list of
operators. And an overview. This seems to be entirely absent or hard
to find.

I _hate_ it when software gets worse, not better.

</rant>
Click to expand...

And I hate it when I hit F1 to get help on some Win API function and
it takes me to the corresponding MFC or ATL method (of which I care
nothing), often without a link to the real thing!

Oh well, at least Sarch works pretty well, and you can filter it...
 
And I hate it when I hit F1 to get help on some Win API function and
it takes me to the corresponding MFC or ATL method (of which I care
nothing), often without a link to the real thing!
Click to expand...

I'd actually like that... if it wasn't for the wince variation of mfc.
 
not only that, but form the way MSDN is composed, you'd think that Microsoft
does not want anyone to use STL.

- classes do not show up on the index tab (try finding string class for
example)
- members are listed on different pages
- nowhere do they have a listing of the different exceptions that can be
trown by each method. I mean, WTF? how am i supposed to handle exceptions if
i don't even know what i can expect?
the only thing i can do is browse through the actual header files and check
what each message does.
and believe me, trying to read and understand the STL headers does not make
your day.
- function descriptions, and especially constructor descriptions are
extremely terse.

it seems they spent as little time as possible on the STL documentation,
instead promoting their own MFC cruft.

Bruno.
 
I was beginning to think that I was the only one. I mean I know what I
want to do, but the syntax isn't quite right and I can't seem to find any
relevant documentation.

Why does help keep showing VB stuff when I am using VC? I do know about
the filter, and have it set but it doesn't always seem to work and in fact
may filter what I am looking for.

Also a few code fragments would be gold.

I mean if you want people to switch to your new environment, MAKE IT EASY
to switch. e.g. "ojb->x" becomes "System::Object->x.ToString" or whatever.
 
Back
Top