Posts Tagged ‘.net’
Several weeks ago I mentioned that I store the images that the user uploads to the system into the database.
Some of you have expressed an interest in how I do that. So I plan to cover that today.
For the purposes of this article, I’m going to assume that you’ve already got the image uploaded and scaled and that all that is left is getting it into the database.
Republished by Blog Post Promoter
I wrote the following article a long time ago on my main domain, but recently I had a reader send in a question that this article addresses. So I’m putting this article here so that it is easier for readers to find in the future….
In the past, when you selected a language, you were selecting an application programming interface (API) as well. So if you decided to use C++, you automatically were selecting the MFC class libraries as well as ATL and STL. You don’t really need to know what these initials stand for, just understand they represent a complete set of functionality that did not have to be written by the programmer.
In the last post I mentioned there were a few topics we need to close up today. The two topics we’ve left undone are popping the attribute information off the stack when we hit a closing element and dealing with the paragraph gap that normally appears between paragraph elements.
Here is a great question from a visitor.
“What is the exact use of GetHashCode of an object in .net? Does it have any relation with garbage collection?”
Let’s answer the second question first. No, it has nothing to do with garbage collection.
While this isn’t specifically targeted at iTextSharp, which we’ve been covering in recent posts, this is really the closest book you are going to find on the subject.
The basics are the same. Keep in mind that the main difference is that setPropertyName and getPropertyName methods have been changed to .NET style properties (versus Java style) where it makes sense. Method names start with a capital letter in iTextSharp, and event wiring is a little funky (we’ll get to that later).