.netframework
-
Yes, it's called "studying". Perhaps you've learned the technique in school??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
You do not "memorize" it, it's too big - and by the time you know it by heart, there'll be a new version. You'd learn how to use it; once you worked through a C#-book, you should be able to use the documentation[^].
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
-
I doubt how much storage capacity you had to memorize the entire .Net framework :confused:. Its a bad idea too and save your time doing other interesting stuffs rather running behind memorizing .net framework. you better store in stack - use it throw it.
Jibesh.V.P India
-
You do not "memorize" it, it's too big - and by the time you know it by heart, there'll be a new version. You'd learn how to use it; once you worked through a C#-book, you should be able to use the documentation[^].
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]
I agree with this. I'd add that when I started out I invested in a copy of the Base Class Library text (it was c# 2005 at the time). That was a great book for showing me a great, useful slice of the framework, how it works, and what it can do. Once you get in the 'mindset' of the framework, how it goes about things etc. You can, more often than not, predict where in the documentation you'll need to look to solve your problem.