Skip to main content

.bat file for stsadm command actions

Hi All,
  Most of the time during client deployment , there might be requirement of Re-Activating client related feature to provide the newly built functionality . usually we used to run the stsadm command as

stsadm -o activatefeature -name "CLIENT_FEATURE_NAME" -url "SITE_URL" -force

Apart from this client related feature, there we need to reactivate some more product related feature which include functionalities such as timerjob, adding content type to the list or adding new columns to the list,etc..In this case we need to enter the stsadm command again and again which makes you damn bore!!!.

Here is a solution to over come your "boring" feeling and enjoy the deployment process


  1. Open a notepad
  2. Paste the following code. I will explain everything below this snippet.
@SET pathToStsadm="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN"
@echo off
cd %pathToStsadm%
echo ------------------------Enter the following Inputs------------------------
SET /p url= Enter site url    
SET /p ClientRealtedFeature= Enter the name of client feature to be activated  
echo ----------------------ACTIVATING FEATURES----------------------
echo Activating FirstFeature ...
stsadm -o activatefeature -name FirstFeature -url %url% -force
echo Activating SecondFeature
stsadm -o activatefeature -name SecondFeature-url %url% -force
echo Activate ClientRealtedFeature
stsadm -o activatefeature -name %ClientRealtedFeature% -url %url% -force
echo ------------------------COMPLETED------------------------
PAUSE


In the above snippet:

pathToStsadm: set the path to the bin folder present in 14 folder, since the stsadm command.exe is present under this bin folder.

url: url of the site . Here note that when the prompt asks for entering site url , you need to provide the site url within the quotation .  viz. "http://siteUrl".

ClientRealtedFeature: provide the client feature name when it asks for entering the client feature name.

Hope this will 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 »