Skip to main content

Code branching in TFS

Being in the IT world we should be always thirsty in learning new things apart from the regular work. In the world of .net , we are using to have a code repository called TFS.
   First of all we should know what is TFS?
   TFS refers to the Team Foundation Server to which all the development systems would be connected , so that the CODE will have its own house.

I will show simple example here











The developer needs to check-in the code to the TFS server so that when the other developer takes the updates from the TFS, he will get the recently checked-in code, so that he will be having updated code.

Before client release, we need to have stable branch of the code which is thoroughly tested and branched as separate version and so that developer can continue check-in the code in the current trunk in the TFS as they complete the developement , so that if there is any bug or issues in the recently checked-in code ,there will not be any problem on previously taken branch of the code.

So now the point is how to do branching?
 Yeah, here i am going to explain how to branch the code. Follow the steps as i have mentioned here.
 Step 1:
            Open the Visual studio with administrator credential. Open the Team Explorer . 

Click 'View' menu and select the 'Team Explorer' option
















Step 2:  
          Your Team Explorer window looks as follows.















Step 3:
           Right click on the Team project's root folder and select 'New Team Project'














Step 4:
       An wizard will get opened. In the 'What is the name of the team project' text box provide the name of the Version Name you want to give WITHOUT space , viz. TechGeekV5.0 etc... and provide the description about that branch such as for what purpose/which client you are going to take branch.


















Step 5:
        In the drop down select the MSF for agile Software Development V5.0 and click on Next button. Do not click on Finish button.


     














Step 6:
      In the wizard, select the 'Do not configure a SharePoint site at this time' and click on Next button. Do not click on Finish button.

















Step 7: 
       Now simply click on Finish button. 


















Yes, you are done with branching the code.

Hope this may help some one

Cheers
Pradeepa Achar


Comments

Post a Comment

Popular posts from this blog

The Fastest way to Export Schema of Sharepoint List

Many of my SharePoint Developer friends are struggling to get the Schema.xml file of a newly created list. The schema.xml file has the list's metadata information, by using the schema.xml, we can create the lis definition and paste this contents of Schema.xml to the Schema.xml file of the newly created List definition, so that you can deploy the list definition on another site. In order to do this, you guys might be following the procedure bu saving the site template and get the site definition solution. After this, you will open visual studio and import this solution and wait for few minutes. THIS IS A CRAPPY PROCEDURE..Why do you invest your time to get a schema of one or few list  by taking entire site definition?..If that site has lots of lists, then it will take lots of time. In my Research, i have found a the BEST  and quicker way to get schema.xml file of a particular list which you need Schema.xml. Follow the following procedure : Go to your site  click on the lis
Post a Comment
Continue »

How to avoid refreshing of page on clicking on BUTTON in jQuery?

Suppose you might have created a button on page.When you click on that button without page refresh some other custom things have to happen. But instead of that, on clicking on the button the page is getting refreshed. How to avoid this?.. Simple, The button click event has default event as refreshing the page. The solution is to "prevent the default event". $("#ButtonID").Click(function(e) {   e.preventDefault(); //Write your custom code here } ); Hope this may help Cheers Pradeepa Achar
Post a Comment
Continue »

This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'cc218449-78b3-4430-b401-4884977560e2' failed validation, file manifest.xml, line 11, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'. Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: oplh6595a-a6hg-416f-a85f-a173bp03dda6 Date and Time: 30/10/2013 13:33:18

By looking at this bug you may get shocked and may not understand why this is happening. I can say, you have developed a wsp of farm solution, not the sandboxed solution  using visual studio and added some OOTB webparts such as visual webparts and trying to deploy the solution via solution gallery directly on to the sharepoint site. It is so simple.Understand that, when you create a .wsp file using visual studio, you deploy as farm solution. But when you try to deploy the same solution from site settings-> solution gallery, you deploy it as sand boxed solution. In this situation ,the "TemplateFiles" elements refers to the items that will be copied into the web servers. This is allowed only in farm solutions , not in sandboxed solutions. I suggest you guys to deploy the solution either using stsadm command or powershell command, so that it will work fine.If anyone wants to know about how to deploy using powershell command you can refer the   techNet  document for
Post a Comment
Continue »