.NET Framework - HELP - DOT NET API IN .CHM FORMAT

Asked By vaib on 03-Nov-11 03:27 PM
Hi,

I come from some java background. I mean I played with it a bit in
college - one or two desktop applications, not much.

So while coding in java I used to feel very comfortable because of
just one thing - Franck Allimant's java API documentation in chm
format. Wow, it is so cool. I rarely used to google for anything. I
just open my Eclipse\NetBeans and open this chm file and I'd be ready
to code. It was like all the java api was right there and I could look
for anything. All the classes(package wise) are listed on the left and
you could just take a look at a few suspecting classes if you were
searching for something and then all the methods in that class would
come up(along with pretty nice explanation and examples) and it would
be very easy to look for stuff and a pleasure to code.

Oh, and here is the link for Franck's site - http://www.allimant.org/javadoc/
- just go to the end of the page and download what you want.

Anyways, now I have a day job and I work in .Net. Pretty awesome
platform again.

BUT, there is something missing. Ever since I came to code in .Net I have
been looking for such a simple chm file for the .Net api documentation
and I have not been able to find one yet. MSDN is too extensive and
boring to go through. it is unnecessarily lengthy. Who needs all those
pages of explanations. So, I mostly find myself googling. Which rarely
happened with Java(thanks to Franck)! Googling is good sometimes but
having the full api doc in a b'ful concise manner under your nose is
awesome.

So. Is there any such thing you have come across in .Net that someone
maintains? Can my dream come true?

I'd love your feedback and thoughts and answers.

Thanking in anticipation.
Vaibhav




Arne_Vajhøj replied to vaib on 05-Nov-11 06:37 PM
Use the MSDN docs.

And start with ".NET Framework Class Library".

Arne
RaZiel replied to vaib on 06-Nov-11 02:34 PM
I feel your frustration. "Win32 Programmer's Reference" was a .hlp file
distributed with the same intent. I still use it today. Didn't even know
there existed something similar for Java, so thanks :)

To answer your question, perhaps this will lead you onto the right
track: http://demiliani.com/blog/archive/2007/04/30/6146.aspx

MSDN is definitely sluggish, huge and a pain in the a**. But it does
help with a powerful dev box.

- RaZ