Here is a nice collection of useful T-SQL coding standards: T-SQL Coding Standards.
Note that these are by no means the end-all of coding standards. Each person has their own style and convention, but following an agreed standard helps everyone involved in the team (or organization) easily understand code that has been developed by a collegue. So feel free to invent on top of these. In my case, our organization has a subset of this, but after seeing this article, am planning to expand more on the list that we have.
Been working with BizTalk regularly for the past few weeks now and I must say that I'm enjoying it. We finally managed to integrate two system (our flagship product developed in Microsoft technoligies with another flagship product developed by us in Oracle). It works really great and I must say that I did write very minimal code and the rest was handled by BizTalk.
Three cheers to BizTalk.
Hmmmmm, another acronym. WSRP stands for Web Services for Remote Portlets. What does this mean? If you are working with portals like SharePoint and are looking at supporting multiple portals for your application, then WSRP is for you.
To understand WSRP more, imagine that you are developing an application (say a stock quote sample) that generates the quotes for a given set of stock symbols. You then configure an application (maybe VS.NET) that reads data from this web service and then generates content in HTML. This can now be plugged as a web-part into a portal like SharePoint. Easy, right? OK, what happens when you need to integrate with another web-service (say a weather web-service) and show that in SharePoint. You will again have to create an application that uses the weather web service and then generates the appropriate UI. Now, things are getting ugly, right? You will need to write as many interface pages for as many web-services that you want to integrate.
Rather, image for a second if all web-service implemented a standard interface with a bunch of methods that get you either the data or the presentation. Now, all that your application has to do is to call these various interfaces with standard method calls and it will get back presentation content! Similar to writing an interface based implementation, but extended to web-services. If you are with me still now, then WSRP is basically just a WSDL specification that outlines the set of methods and interfaces that a web-service will have to adhere to. These web-services are called producers. Once you have created as many producers as you want, a consumer application (like SharePoint) can simply call the various producers using standard method calls and just render the content. Easy, right and structured too.
What have you achieved? Basically you have eliminated the intermediary application that is required to format the data received into presentable content (you can still do this if needed, though using WSRP). All you will need to know is the URLs to call to get the content and you can now call standard methods and the service will respond in a predictable way.
WSRP is catching up fast and portals like SharePoint 2003 support it already. There is a beta version of a toolkit that you will need to install on top of SharePoint 2003 and once done, you can configure WSRP compliant web-services as web-parts in SharePoint. To get the toolkit, visit: WSRP Toolkit for SharePoint. To know more about WSRP, here is an excellent proposal document from IBM: WSRP Basics. Here is an excellent FAQ on the subject: WSRP FAQ.
Another application that I ran into over the week. Thunderbird 1.0 is an application from Mozilla that allows you to have a unified view of mail, blogs, newsgroups and RSS feeds. To me, it is extremely useful, because I keep shifting between Outlook Express, RSS Readers (like Firefox) and mail. After installing Thunderbird, I'm in love with it! I can now have a single view of RSS feeds, newsgroups, blogs and mail (I have not syncronized mail till now).
If you are interested, you can download it from here: Thunderbird