Here is the link to Download SharePoint 2010

I tried it already and you just need to make your computer is configure and have proper OS to run SharePoint 2010

Hardware Reqs

1. 64-bit, four-core, 2.5 GHz minimum per core processor
2. 4 GB RAM
3. 8 GB RAM for farm
4. 80 GB Hard Disk

Double up every Req for your production environment.

SharePoint 2010 was introduced on March 3rd of 2010 and it has more collaboration features than any other prior version.

I like to see new feature called Site Modeling which is designed to provide a template based infra. for the the custom website deployment. It has reach user interface allowing users to customize and format SharePoint 2010 website.

Master Pages as well as more advance customization is required by SharePoint 2008 but not so with 2010. Microsoft did a good job enhancing webstie customization in their new version of the SharePoint 2010 server.

Silverlight Web Part is another nice addition that allows to integrate Silverlight application within SharePoint 2010 in a more intuitive way. It was somewhat a challange to use Silverlight in 2008 and I am glad they released this web part.

Please find the list of the SharePoint 2010 collaboration features

• SharePoint 2010 Document collaboration via document libraries
• Wikis and enhanced blogs
• RSS support with capabilities of displaying ATOM feeds
• Discussion boards and Messaging
• Project task management and Project Management Office Tools
• Contacts, calendars, and tasks all integreated under one umbrela of the SharePoint 2010
• E-mail storing, retrival and management
• Better interworkings with Microsoft Office 2010
• Offline support using SharePoint Workspace 2010

You may look at the full list of features at this website SharePoint 2010 by Microsoft

You need to use download Manager to Install the Visual Studio 2010 and copy paste the following files

1. You can select all four files at the same time. http://download.microsoft.com/download/8/5/c/85c7cca1-7d25-4c9b-85fc-5e837a393a0b/WS08_RTM_x86_EnterpriseVHD.exe

http://download.microsoft.com/download/9/C/0/9C036510-3218-4258-8B03-67DC1D6A497C/SQLFULL_ENU.iso

http://download.microsoft.com/download/1/B/7/1B71259E-9D37-4EB7-BC8A-1B53DF7C7D86/VS2010B2TFS_3PartsTotal.part1.exe

http://download.microsoft.com/download/1/B/7/1B71259E-9D37-4EB7-BC8A-1B53DF7C7D86/VS2010B2TFS_3PartsTotal.part2.rar

http://download.microsoft.com/download/1/B/7/1B71259E-9D37-4EB7-BC8A-1B53DF7C7D86/VS2010B2TFS_3PartsTotal.part3.rar

http://download.microsoft.com/download/F/A/1/FA1DAEA6-B719-461D-96B0-31C9C63680C8/VS2010B2Ult_4PartsTotal.part1.exe

http://download.microsoft.com/download/F/A/1/FA1DAEA6-B719-461D-96B0-31C9C63680C8/VS2010B2Ult_4PartsTotal.part2.rar

http://download.microsoft.com/download/F/A/1/FA1DAEA6-B719-461D-96B0-31C9C63680C8/VS2010B2Ult_4PartsTotal.part3.rar

http://download.microsoft.com/download/F/A/1/FA1DAEA6-B719-461D-96B0-31C9C63680C8/VS2010B2Ult_4PartsTotal.part4.rar

2. Launch the user interface for Free Download Manager (either from the Start Menu or via the system tray icon if FDM is already running).

3. Click File -> Import -> Import List of URLs from Clipboard.

4. When prompted for a download group, accept the default ("Other") and click OK.

Teamprise did a good job at helping to integrate different programming development environments with the TFS and by acquiring it Microsoft improves chances of TFS to be used more widely.

There are many teams working together on the same project utilizing different programming languages such as Java and C#. Java can be used for Web Services and C# for WinForms etc... and there was always a question of how to manage these two different teams using two different languages and with the Teamprise in the Microsoft.

Microsoft will do a better job integrating the Teamprise with the TFS and hopefully it will lead to wider adaptation of the TFS.

You can find out more information about this acquisition online via reading Official Press Release

Newer version of the Microsoft's Visual Studio called Visual Studio 2010 brings a new list of features not available in prior versions of Visual Studio. We compiled short list of these features for your reference. You can always read more about these features on Microsoft MSDN site dedicated to Visual Studio 2010

• You can use the Navigate To feature to search for a symbol or file in the source code.
• You can search for keywords that are contained in a symbol by using Camel casing and underscore characters to divide the symbol into keywords.
• Generate From Usage supports programming styles such as test-driven development.
• Use suggestion mode for situations where classes and members are used before they are defined.
• Calls to and from a selected method, property, or constructor.
• Implementations of an interface member.
• Overrides of a virtual or abstract member.
• Text insertion: Type into a box selection to insert the new text on every selected line.
• Paste: Paste the contents of one box selection into another.
• Zero-length boxes: Make a vertical selection zero characters wide to create a multi-line insertion point for new or copied text.
• Tool windows can now move freely between docking at the edges of the IDE, floating outside the IDE, or filling part or all of the document frame. They remain in a dockable state at all times.

One way to check for the SharePoint site existance is to pass site name to a method that wil return true or false based on the end result. Otherwise, you may run into run time errors when trying to add a file to the SharePoint site that does not exist.

private static bool CheckSPSite(string siteName) 
{
            using (SPSite site = new SPSite(siteName)) 
            { 
                using (SPWeb web = site.OpenWeb()) 
                {                     
                    if (!web.Exists) 
                    { 
                        return false; 
                    } 
                    else
                    { 
                        return true; 
                    } 
                } 
            } 
        }

I would recommend creating util Library where you can store all your helper methods and re-use in other projects.

We published next batch of Microsoft exam reviews which will help you in your preparations for these exams.

• Exam 70-272
• Exam 70-284
• Exam 70-290
• Exam 70-291
• Exam 70-292
• Exam 70-293
• Exam 70-294
• Exam 70-297
• Exam 70-298
• Exam 70-299
• Exam 70-300
• Exam 70-305
• Exam 70-306
• Exam 70-315
• Exam 70-316
• Exam 70-320
• Exam 70-350
• Exam 70-351
• Exam 70-400
• Exam 70-431
• Exam 70-433
• Exam 70-445
• Exam 70-446
• Exam 70-500
• Exam 70-504
• Exam 70-510
• Exam 70-529
• Exam 70-536
• Exam 70-541
• Exam 70-542
• Exam 70-548
• Exam 70-553
• Exam 70-554
• Exam 70-556
• Exam 70-557
• Exam 70-561
• Exam 70-564
• Exam 70-567
• Exam 70-568
• Exam 70-571
• Exam 70-601
• Exam 70-632
• Exam 70-633
• Exam 70-634
• Exam 70-638
• Exam 70-640
• Exam 70-642
• Exam 70-643
• Exam 70-647
• Exam 70-720

We started new section on our Tutorial Page called Exam where we provide descriptions and guidance on each of the known Microsoft Exams.

We are hoping to build community where our readers can exchange information and provide advice to each other with regards to each of the exams listed on our Microsoft Exams page.

There are time when we need to create a new MOSS 2007 site. We can do it in two ways each of which has pros and cons. One is manual another if automated.

I would always recommend automated SharePoint site provisioning and for the following reason.

1. It is faster to provision something that is automated
2. No human errors
3. It can be scaled up easily if needed
4. It is easier to maintain integrity of the taxonomy
5. Ease of use once entire process is set up.

I also recommend to use one of the template sites that come with MOSS 2007 or creating your own. One good candidate for site provisioning template is STS#0 Team Site

There are severl resource online that can help you start with Site Provisioning.

• MOSS 2007 Sample Application
• MOSS 2007 SDK
• Windows SharePoint Services 3.0 Tools: Visual Studio 2008 Extensions

I am planning to release a series of SharePoint tutorial this coming week. In preparation for this release I was studying several online materials that are readily available online. I try to summarize my list of SharePoint training material that was used in SharePoint tutorial which will be part of our tutorial section of the site.

First, you need to start with simple introduction to SharePoint if you have never heard about it. More senior developers who have knowledge may just skip this section all together.

I found that I can learn faster if I see, hear and write all at the same time. As a result, I really like to listen to SharePoint online videos and webcasts that expert produced and published online.

In order to gain information on most recent developments that happen with SharePoint, I like to read blogs of developers who actually developed and support SharePoint development community.

I then like to read up on SharePoint white-papers and practice guides all produced by Microsoft. I rarely follow white-papers by third companies since most of it just hidden form of advertisement for their services. There are actually several of them available online from Microsoft site and CodePlex site

Microsoft produced at least two different sets of training for WSS and MOSS that are deep technically and easy to understand and use.

Finally, when you ready to be certified, you need to complete these two important exams
70-541 TS: Microsoft Windows SharePoint Services 3.0 – Application Development
70-542 TS: Microsoft Office SharePoint Server 2007 – Application Development

You don't need to purchase software to start working with SharePoint, just download SharePoint VPC from Microsoft site

I was browsing google.com and saw underneath each link a message that says "This site may harm your computer" I saw it for every legitimate site even for google itself.

I tried to click on the links and got another Warning page from google that said: "Warning - visiting this web site may harm your computer!"

I am not sure if my computer is infected in some way so that every link on the google.com page is getting this message or google.com really screw things up and This site may harm your computer message pops-up now every there.

There are reports that google.com main index may have been broken or even hacked.

You would normally see this message "This site may harm your computer" when google.com identifies website that has some sort of malware that it tries to install or if website is infected with the virus. This is a big blow to google.com reputation. The interesting part is that all websites that deal with Internet security have this message underneath its main Title on google.com results page.

Google explanation to this error message: "We want our users to feel safe when they search the web, and we're continuously working to identify dangerous sites and increase protection for our users." It means as of now I cannot access any of the site directly from google.com search results page because every site is identified as dangerous.

Here is what you can see if your search for google itself

I tried to type This site may harm your computer into google.com to search for this error message and got back several sites with the same issue

It has been almost 15 minutes since I noticed this message but google.com still is showing it on their website. I am hoping it will get resolved soon. At least, I am sure its not my computer. I have read that many people are experiencing same problem, so it must be google.com issue.

Its 10:45 am EST now and I see that error does not appear on google.com search result. It means that google.com got this issue resolved. I wonder what caused this issue

• A Virus
• Hacker attack
• Google tried to release new feature but broke the site

Error message this site may harm your computer stopped appearing on google.com site even though people from other countries are still experiencing it. It was brought to my attention that first case of this error was recorded in India.

There is a need to log errors, events, exceptions every time you design and develop an application. The Logging is important for many reasons. It helps you to track any issues happening with the application. It helps to track usage statistics. It helps with capturing exceptions. As a result, the Logging should always be an integral part of any solid application design and development

Thankfully, Microsoft's Enterprise Library has Logging Application Block amongst other Application Blocks and it is ready to be used by .NET Developers. This is one of the benefits working with the .NET Framework.

The Logging Application Block is an integral part of every major Enterprise Library release. It lets you capture errors, events, exceptions then email it to you or store this information to:

Application event log
Database
File
Windows Management Instrumentation (WMI)
Custom Locations

In order to start using Logging Application Block you need to add reference to the following libraries that comes with the Logging Application Block:

• Microsoft.Practices.EnterpriseLibrary.Logging
• Microsoft.Practices.EnterpriseLibrary.Logging.ExtraInformation
• Microsoft.Practices.EnterpriseLibrary.Logging.Filters

You may start learning more about the Logging Application Blocks on Microsoft website.

Microsoft release updated version of its Microsoft Enterprise Library 4.1 back in October 2008. This release has several improvements over prior version. There are several blocks that we are all familiar with from other Microsoft Enterprise Libraries.

• Caching Application Block used for application caching. Web based projects or Windows Forms projects are all good candidates for caching.
• Cryptography Application Block takes care of encryption and decryption needed for any security needs while creating applications. .
• Exception Handling Application Block is another very useful block for a routine task such as exception handling within application. .
• Logging Application Block can be used for error logging, events logging which is a powerful way of tracking issues, usage statistics of your application. .
• Policy Injection Application Block can be used to validate form elements for valid inputs without writing your own custom validations. .
• Security Application Block used to incorporate authorization, authentication and security caching for Web or WinForms applications. .
• Unity Application Block. dependency injection container with support for constructor.
• Validation Application Block used to create validation rules for business objects. These Objects can be used in multi payers of the application. .

Links that will help you to further your knowledge about Microsoft Enterprise Library 4.1

1. EntLib
2. MSDN Information about Microsoft Enterprise Library 4.1

Microsoft is reading new set of exams that will certify you in NET 3.5 and Visual Studio 2008. There are several exams for you to learn if you plan to pass MCPD for the first time and there is also a set of exams for the upgrade from MCPD 2005 to MCPD 2008.

New MCDP 2008 certification is following same pattern as MCDP 2005 with the new certifications available in the following exam paths:

• Windows Developer 3.5
• ASP.NET Developer 3.5
• Enterprise Application Developer 3.5

upgrade certifications available for the following exam paths:

• Windows Developer
• Web Developer
• Enterprise Application Developer

You can read more about MCPD 2008 on Microsoft website at:

P.S. Upgrade exams are not available as of 1/2/2009

TFS Branching is a hot topic amongst development team. There are many was to branch your project and each approach has its advantages as well as disadvantages. However, branching is needed and this is the only thing that is certain.

VSTS Rangers came very close in answering questions that so many development teams have with regards to branching. They identified three different strategies for TFS Branching. They also call them TFS Branching Plans

Basic TFS Branch Plan – the idea behind Basic Branch Plan is to enable dev. team to develop for the next release and at a same time keep fixing bugs in the new release. In other word, you have main TFS branch with two offshoots: development branch and release branch. You dev team can work on each individually and then changes are merged back into the main branch.

Standard TFS Branch Plan – this is more advanced TFS branching technique and it is aligned with your release strategy. If you push any type of service packs or hotfixes as a stand alone packages then you need to have additional branch just for these hotfixes or service packs. This new service pack branch will sit between your main TFS branch and your release branch and changes are merged between these three branches.

Advanced TFS Branch Plan – this is the most comprehensive approach and it is mostly done by companies like Microsoft when you have multiple releases of the service packs and along with the releases of the main application. Advanced TFS branching allows to have as many branches between main branch and release branch as necessary to support your release strategy. For example, if you release hot fixes along with major service packs then you’ll have two branches sitting between your main branch and your release branch.

You can read more about it on CodePlex...

There is set of rules that you can run against your code for the Code Analysis.

Here is a list of those rules. You may not alwasy run all of them agsint your code and here is very good explanation for it.

Public Rule Set:

Design
CA1008 EnumsShouldHaveZeroValue
CA1009 DeclareEventHandlersCorrectly
CA1011 ConsiderPassingBaseTypesAsParameters
CA1012 AbstractTypesShouldNotHaveConstructors
CA1014 MarkAssembliesWithClsCompliant
CA1017 MarkAssembliesWithComVisible
CA1018 MarkAttributesWithAttributeUsage
CA1019 DefineAccessorsForAttributeArguments
CA1023 IndexersShouldNotBeMultidimensional
CA1025 ReplaceRepetitiveArgumentsWithParamsArray
CA1026 DefaultParametersShouldNotBeUsed
CA1027 MarkEnumsWithFlags
CA1028 EnumStorageShouldBeInt32
CA1030 UseEventsWhereAppropriate
CA1032 ImplementStandardExceptionConstructors
CA1034 NestedTypesShouldNotBeVisible
CA1036 OverrideMethodsOnComparableTypes
CA1038 EnumeratorsShouldBeStronglyTyped
CA1039 ListsAreStronglyTyped
CA1040 AvoidEmptyInterfaces
CA1041 ProvideObsoleteAttributeMessage
CA1043 UseIntegralOrStringArgumentForIndexers
CA1044 PropertiesShouldNotBeWriteOnly
CA1045 DoNotPassTypesByReference
CA1046 DoNotOverloadOperatorEqualsOnReferenceTypes
CA1050 DeclareTypesInNamespaces
CA1051 DoNotDeclareVisibleInstanceFields
CA1052 StaticHolderTypesShouldBeSealed
CA1053 StaticHolderTypesShouldNotHaveConstructors
CA1054 UriParametersShouldNotBeStrings
CA1055 UriReturnValuesShouldNotBeStrings
CA1056 UriPropertiesShouldNotBeStrings
CA1057 StringUriOverloadsCallSystemUriOverloads
CA1058 TypesShouldNotExtendCertainBaseTypes
CA1059 MembersShouldNotExposeCertainConcreteTypes

Globalization
CA1300 SpecifyMessageBoxOptions
CA1301 AvoidDuplicateAccelerators
CA1304 SpecifyCultureInfo
CA1305 SpecifyIFormatProvider
CA1306 SetLocaleForDataTypes
CA1307 SpecifyStringComparison
CA1309 UseOrdinalStringComparison
CA2101 SpecifyMarshalingForPInvokeStringArguments

Interoperability
CA1401 PInvokesShouldNotBeVisible
CA1402 AvoidOverloadsInComVisibleInterfaces
CA1403 AutoLayoutTypesShouldNotBeComVisible
CA1404 CallGetLastErrorImmediatelyAfterPInvoke
CA1405 ComVisibleTypeBaseTypesShouldBeComVisible
CA1406 AvoidInt64ArgumentsForVB6Clients
CA1408 DoNotUseAutoDualClassInterfaceType
CA1413 AvoidNonpublicFieldsInComVisibleValueTypes

Naming
CA1700 DoNotNameEnumValuesReserved
CA1701 ResourceStringCompoundWordsShouldBeCasedCorrectly
CA1702 CompoundWordsShouldBeCasedCorrectly
CA1703 ResourceStringsShouldBeSpelledCorrectly
CA1704 IdentifiersShouldBeSpelledCorrectly
CA1707 IdentifiersShouldNotContainUnderscores
CA1708 IdentifiersShouldDifferByMoreThanCase
CA1709 IdentifiersShouldBeCasedCorrectly
CA1710 IdentifiersShouldHaveCorrectSuffix
CA1711 IdentifiersShouldNotHaveIncorrectSuffix
CA1712 DoNotPrefixEnumValuesWithTypeName
CA1713 EventsShouldNotHaveBeforeOrAfterPrefix
CA1714 FlagsEnumsShouldHavePluralNames
CA1715 IdentifiersShouldHaveCorrectPrefix
CA1716 IdentifiersShouldNotMatchKeywords
CA1719 ParameterNamesShouldNotMatchMemberNames
CA1720 IdentifiersShouldNotContainTypeNames
CA1721 PropertyNamesShouldNotMatchGetMethods
CA1722 IdentifiersShouldNotHaveIncorrectPrefix
CA1724 TypeNamesShouldNotMatchNamespaces

Performance
CA1811 AvoidUncalledPrivateCode
CA1812 AvoidUninstantiatedInternalClasses
CA1813 AvoidUnsealedAttributes
CA1815 OverrideEqualsAndOperatorEqualsOnValueTypes
CA1816 DisposeMethodsShouldCallSuppressFinalize
CA1819 PropertiesShouldNotReturnArrays

Portability
CA1900 ValueTypeFieldsShouldBePortable
CA1901 PInvokeDeclarationsShouldBePortable

Reliability
CA2001 AvoidCallingProblematicMethods
CA2002 DoNotLockOnObjectsWithWeakIdentity
CA2004 RemoveCallsToGCKeepAlive
CA2006 UseSafeHandleToEncapsulateNativeResources

Security
CA2102 CatchNonClsCompliantExceptionsInGeneralHandlers
CA2103 ReviewImperativeSecurity
CA2104 DoNotDeclareReadOnlyMutableReferenceTypes
CA2105 ArrayFieldsShouldNotBeReadOnly
CA2106 SecureAsserts
CA2107 ReviewDenyAndPermitOnlyUsage
CA2108 ReviewDeclarativeSecurityOnValueTypes
CA2109 ReviewVisibleEventHandlers
CA2111 PointersShouldNotBeVisible
CA2112 SecuredTypesShouldNotExposeFields
CA2114 MethodSecurityShouldBeASupersetOfType
CA2115 CallGCKeepAliveWhenUsingNativeResources
CA2116 AptcaMethodsShouldOnlyCallAptcaMethods
CA2117 AptcaTypesShouldOnlyExtendAptcaBaseTypes
CA2118 ReviewSuppressUnmanagedCodeSecurityUsage
CA2119 SealMethodsThatSatisfyPrivateInterfaces
CA2120 SecureSerializationConstructors
CA2121 StaticConstructorsShouldBePrivate
CA2122 DoNotIndirectlyExposeMethodsWithLinkDemands
CA2123 OverrideLinkDemandsShouldBeIdenticalToBase
CA2124 WrapVulnerableFinallyClausesInOuterTry
CA2126 TypeLinkDemandsRequireInheritanceDemands
CA2127 SecurityTransparentAssembliesShouldNotContainSecurityCriticalCode
CA2128 SecurityTransparentCodeShouldNotAssert
CA2129 SecurityTransparentCodeShouldNotReferenceNonpublicSecurityCriticalCode

Usage
CA1806 DoNotIgnoreMethodResults
CA2207 InitializeValueTypeStaticFieldsInline
CA2208 InstantiateArgumentExceptionsCorrectly
CA2209 AssembliesShouldDeclareMinimumSecurity
CA2211 NonConstantFieldsShouldNotBeVisible
CA2213 DisposableFieldsShouldBeDisposed
CA2214 DoNotCallOverridableMethodsInConstructors
CA2216 DisposableTypesShouldDeclareFinalizer
CA2217 DoNotMarkEnumsWithFlags
CA2218 OverrideGetHashCodeOnOverridingEquals
CA2220 FinalizersShouldCallBaseClassFinalizer
CA2221 FinalizersShouldBeProtected
CA2224 OverrideEqualsOnOverloadingOperatorEquals
CA2225 OperatorOverloadsHaveNamedAlternates
CA2227 CollectionPropertiesShouldBeReadOnly
CA2228 DoNotShipUnreleasedResourceFormats
CA2229 ImplementSerializationConstructors
CA2230 UseParamsForVariableArguments
CA2233 OperationsShouldNotOverflow
CA2234 PassSystemUriObjectsInsteadOfStrings
CA2235 MarkAllNonSerializableFields
CA2236 CallBaseClassMethodsOnISerializableTypes
CA2237 MarkISerializableTypesWithSerializable
CA2240 ImplementISerializableCorrectly

Non-Public Rule Set:

Globalization
CA2101 SpecifyMarshalingForPInvokeStringArguments

Portability
CA1900 ValueTypeFieldsShouldBePortable
CA1901 PInvokeDeclarationsShouldBePortable

Reliability
CA2002 DoNotLockOnObjectsWithWeakIdentity

Security
CA2100 ReviewSqlQueriesForSecurityVulnerabilities
CA2102 CatchNonClsCompliantExceptionsInGeneralHandlers
CA2103 ReviewImperativeSecurity
CA2104 DoNotDeclareReadOnlyMutableReferenceTypes
CA2105 ArrayFieldsShouldNotBeReadOnly
CA2106 SecureAsserts
CA2107 ReviewDenyAndPermitOnlyUsage
CA2108 ReviewDeclarativeSecurityOnValueTypes
CA2109 ReviewVisibleEventHandlers
CA2111 PointersShouldNotBeVisible
CA2112 SecuredTypesShouldNotExposeFields
CA2114 MethodSecurityShouldBeASupersetOfType
CA2115 CallGCKeepAliveWhenUsingNativeResources
CA2116 AptcaMethodsShouldOnlyCallAptcaMethods
CA2117 AptcaTypesShouldOnlyExtendAptcaBaseTypes
CA2118 ReviewSuppressUnmanagedCodeSecurityUsage
CA2119 SealMethodsThatSatisfyPrivateInterfaces
CA2120 SecureSerializationConstructors
CA2121 StaticConstructorsShouldBePrivate
CA2122 DoNotIndirectlyExposeMethodsWithLinkDemands
CA2123 OverrideLinkDemandsShouldBeIdenticalToBase
CA2124 WrapVulnerableFinallyClausesInOuterTry
CA2126 TypeLinkDemandsRequireInheritanceDemands
CA2127 SecurityTransparentAssembliesShouldNotContainSecurityCriticalCode
CA2128 SecurityTransparentCodeShouldNotAssert
CA2129 SecurityTransparentCodeShouldNotReferenceNonpublicSecurityCriticalCode

Usage
CA2233 OperationsShouldNotOverflow

http://blogs.msdn.com/fxcop/archive/2007/08/09/what-rules-do-microsoft-have-turned-on-internally.aspx

In addition, you don't have to use Microsoft toolset even though it comes for free. There are other nice commercial tools out there that can do better job at visually presenting you with the charts and other visual effects of your code analysis. NDepend is one such example. You can read an article on how to use this tool here.

http://www.ndepend.com/

We got new studio and we got new visual capability to manage Branching and Merging. This is really big deal with the Branching and Merging which was only availble via command line.

Microsoft's Channel 9 produced nice video about Branching and Merging in Visual Studio 2010.

I strongly recommend this video for the Branching and Merging as a concept as well as particular application.