Description. Thank you for visiting Dot Net Perls. This web site serves the .NET developer community with clear explanations of code. It isn't a blog and it isn't about the author. It is about you and the millions of programmers looking for competent and simple code examples.
1. Contacting Sam
Please send emails regarding technical flaws in the website to the author. He greatly appreciates being told where he has made mistakes. Unfortunately, Sam cannot answer all emails regarding the site, but appreciates all feedback. He cannot provide technical support for nontrivial programs.
Task: Read about the author.
Solution: See this page.
Task: Send email to Sam.
Help out by pointing out errors.
Solution: Send it to sam.allen@rocketmail.com.
[mailto:]
Task: Flame the author.
Solution: Click on the back button.
Also see "Technical criticisms" below.
[Back Button]
Task: View the Dot Net Perls reading list.
Solution: Read the books article.
[Books]
[Terms, Describing Programming]2. Website goal
This website's topic is about programming and discovering new and fascinating things with technology. It is here not just to impart knowledge to software developers, but to bring a positive perspective to the community. The best way to help improve this site is to point out the mistakes in it by email. It doubtless contains several technical or coding errors and flaws that Sam is not aware of. He welcomes all objective technical comments.
3. Writing and developing Dot Net Perls
At first, when Sam wrote articles for the old Dot Net Perls blog, they took a lot of time and were not easy to read. Now, he can write much better articles, which require much less editing, very quickly. Most of the new articles have not taken much time to write. Far more time is spent researching the topics.
Creating Dot Net Perls. Sam didn't create Dot Net Perls with the purpose of developing a large, top .NET developer site. However, he found there was an incredible demand for technical information. He kept improving the articles and the site to where it is now. He does not expect the site to ever be finished.
4. Commenting on posts
The author decided against having commenting available on the articles, mainly because he doesn't want to have to delete junk comments and manage all the data. Additionally, commenting slows down pages and increases the complexity of the site—not just the technical side but also the information side.
5. Technical criticisms
The author welcomes technical comments on his articles through email. He will not respond to emotional rants or flames—ever. So it you send that sort of email or post that kind of content on your blog, I will not respond.
6. Notes on advertising
It costs Sam a significant amount of money to pay for hosting of this site. Also, the site makes much less money than the average .NET developer. Sam is investigating ways to minimize advertising for regular readers. If you are interested in advertising on Dot Net Perls, please send an email. [See table above.]
Where the advertisements are. The ads on the site are located on all articles that are not personal pages or navigation pages. The home page, the category browsing pages, the sitemap, and all the about pages do not advertise.
7. Dot Net Pearls?
Sam's decision to use the play on words in the programming language Perl has caused some confusion, and people end up searching for dotnetpearls. Fortunately, dotnetpearls.com and dotnetperls.com go to the same site.
8. Legal note
Using code derived from the examples in the articles is encouraged, and is allowed without attribution. The articles themselves are original work and the author uses the full extent of the law to protect them. [Digital Millennium Copyright Act]
9. Summary
Here we looked at the goals of Dot Net Perls, and also saw a picture of the author and discussed some issues related to Perl and pearls, along with comments and flames. The author hopes the site is useful to you and that you bookmark it. He uses it as a reference source quite frequently.