The Sharepoint Developer Introduction for .NET Developers

A good resource for dotnet developers for a hands on Microsoft Office Sharepoint Server 2007 Development.

There are not much developers who are experts in MOSS 2007 Developments. This is the Microsoft's step for the .net communities to gain momentum in sharepoint development.

Video Tutorials and hands on Sessions are included and are really informative.

The Sharepoint Developer Introduction for .NET Developers

Architect Webcast Series

Aspiring Architect Series 2008 - A Web Cast series for aspiring architects.
Checkout the following link

Architect Webcast series

Software Patterns

Architectural Patterns

• Highest level patterns
• Determines overall system architecture and provides the skeleton for the system
• Determines and specifies the relationship, roles and responsibilities of each subsystem
• It organizes the relationship between the sub systems
Eg.. SOA, Layered Architecture

Design Patterns

Used to fine tune the overall architecture and solve problems specific to the subsystem
It does structuring components, delegating and distributing workloads and organizing the communication and creation of components

Three Categories
• Creational Pattern
• Structural Pattern
• Behavioral Pattern

Implementation Patterns or Idioms

Defines solutions specific to a language
Even if I know the syntax in a language, to do efficient implementation one should use some specific styles that the language provides.

Yet Another reason why Properties should be used instead of Fields

Today, I did a little experiments on Properties VS Fields. It is better to use properties especially when that property is to interact with the other DLLs or external Assemblies.

Scenario: library.library.Name is a field in my library which I refer in my winapp. I executed it worked fine. I wanted to validate Name field for special characters so I decided to change “Name” (At present a Field in library) to a property so that I could validate it in the set property.

As the member name and the return type (string) did not change I did not recompile my winapp. But I got the following exception “Field not found” as it’s a property now.

Conclusion: When you need a member to interact with the external assemblies or DLLs or EXEs make it a property instead of field. This enables you to add validators later within your class.