Both can be used to define a bond between two objects, then why do we need one or the other, wouldn't one of them be sufficient. Here are my 2 cents. Interfaces are actually nothing but a contract that you are publishing to the external world, so whoever is agreeing to contract must see that their application agrees to that by implementing behavior defined in the contract, where as on the other hand if you something beyond say sharing the state as well as behavior then you need abstract classes.

Attributes vs. Properties

These are one of the confusing terms at least in programmer’s world. Often they get swapped.

Here is my opinion about them ...

Marker Interfaces & Custom Attributes

Marker Interfaces are dummy interfaces having no methods. These can be used to verify an object type at runtime. They are nothing but contracts without any behavior.

Dialog boxes on Windows forms will be hidden if you are actively in a different window and you will not be able to notice, especially Adobe Acrobat Reader and Visual Studio Team Foundation Client Network login credentials dialog box. for example you started Acrobat Reader and opened some other program while the first is still loading. Adobe decides to update itself and waits for your response. You would be noway notified about this pending request no where on Toolbar or system tray alerting you. Sometimes if you try to open a second adobe document without attending the first request, you are freezing your machine for good time. until you hit ok to the first one, good luck to find it out, because that dialog box is hidden under the main document and if you don't see it until you close the main document.

The issue with VSTS is simple, your logon dialog box is not notified but atlest it will be on top of the visual stu ...

I found this thread interesting and kudos to Hector Cruz for. This thread shows how to create a LINQ enabled VB.NET Web Projects Template.

Here is the link: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=290434&SiteID=1