You have a Facebook profile with a lot of connected friends. You share your interests and personal information with those friends. You also have a LinkedIn profile with just as many connected contacts with whom you share your job related information. All your pictures are in the hands of Flickr and your Twitter account tells your friends what you are up to on an hourly basis.
A lot of people have requested that we added AJAX to certain parts of BlogEngine.NET, so we did. Because of the rule of not using third party components, it is implemented using the build-in client-callback feature with some custom JavaScript. All in all very few lines of code was needed. The calendar widget to the right on this site is now ajaxified for a more smooth navigation between months. The postback reloaded the page every time you navigated to a new month and that was not very cool. The performance is actually pretty descent I think.
Over the years, I've used a lot of third-party components and self built control libraries. It an easy way to add functionality to your code projects - just reference the dll file and that's it. This encapsulated functionality comes in most cases at a high cost. Imaging that you have an assembly of your homemade ASP.NET controls that you wish to use in your new website. In there you have a custom version of the GridView control that does something smart. On your new website this is exactly what you need, but you need it to behave a little different in a certain situation.
Many websites have two points of entry for each individual page - one with www and one without. It means that if other websites link to yours, they might link to the same page using two different addresses.
If you want to test your position in Google for a certain search term, you can do so by using the Google website. By position I don't mean Page Rank, but the actual place in the search results.
If you want to make your website validate the WAI or Section 508 accessibility guidelines, you have to separate adjacent links with more than white space.
A couple of months ago one of my readers asked me to build a stock quote class that would automatically update the quote.
In many different scenarios we need to check if a string can be converted into an integer e.g.
In many cases we write our ASP.NET logic around query strings in order to show the right product page or what not.
I was playing around with HTTP request headers and for some reason started thinking about how limited information they provide about the requesting browser.