.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

How to revert a Solution after upgrade?

Posted By:      Posted Date: September 20, 2010    Points: 0   Category :SharePoint

If I upgrade a Sharepoint Solution using "stsadm -o upgradesolution" command then what is the way to revert back the same to its previous state?

Also let me know the limitation of this approach. For example, if I am GAC'ing a new version of a DLL and replacing some custom .ascx and .aspx files during the upgradation then will the revert process be able to revert the DLL and the files as well?

View Complete Post

More Related Resource Links

Upgrade Solution using a .wsp file created from a site template

Hello, I'm creating a new site template that I will need to move from my development to production server. I have saved the template as a .wsp file and installed it on my staging server without any problems. However, I know once the site goes into production that changes will occur and I will need to upgrade the site template. I have tried to make changes to my development site and save a new site template, and then move to my staging server and upgrade the existing solution using the below PowerShell command, but I get an error that the GUIDS are different and the solution cannot be upgraded. Command: Update-SPUserSolution -Identity MyTemplate v1.wsp -Site http://webapplication/site  -ToSolution MyTemplate v2.wsp Error: Update-SPUserSolution : Given solution cannot be upgraded to the provided ToSolution because the solutions have different Guids. Does anyone know how I would upgrade the solution when using a site template as the bases for the solution? Thanks, wm5

Upgrade Solution not updateing web parts in webpart gallery.


Hi experts..

I am using following commands for upgrading solution and feature...

stsadm -o upgradesolution -name "%WSPFileName%" -filename "%WSPPath%" -immediate -allowGacDeployment
STSADM -o execadmsvcjobs
stsadm -o deactivatefeature -ID FC35A90B-46D5-4b61-8787-8A667B9275C5 -Url "%URL%"
stsadm -o activatefeature -ID FC35A90B-46D5-4b61-8787-8A667B9275C5 -Url "%URL%"

STSADM -o execadmsvcjobs



with above commands my web part files are getting update in 12 hive features(Web part feature).. but on in web part gallery..

Am i missing anything..? or sequence of commands are not proper...



Error_1_Error occurred in deployment step 'Upgrade solution': Command ID 'Contoso.Commands.IsSolu


When following this article for creating a Custom Deployment Step for SharePoint Projects i get the following error. (MSFT Article: http://msdn.microsoft.com/en-us/library/ee256698.aspx)

Error: Error 1 Error occurred in deployment step 'Upgrade solution': Command ID 'Contoso.Commands.IsSolutionDeployed' is invalid.

I have gone through the article two times and each time it does the samething. Any reason why it can't see the Command ID?

SAFE Control error after solution upgrade




I have a Sharepoint Solution that provides a couple of webparts. After a solution upgrade (with stsadm -o upgradesolution) I discovered on one system that the Webparts that were drawn to a webpart page now show SAFE CONTROL errors.

I took a look into the web.config, but the SAFE CONTROL entries were still there and from my point of view - correct.

edit: This system has only 1 WF Server.

What has caused these SAFE CONTROL errors ? On other systems this solution upgrade was successful.How can I correct this system ?

edit: Would a complete Solution deinstallation (rectract/delete) and new installation could heal this system ?

Thanks for your help.




Complete SQL Solution

SQL Server Solutions: SQL Server 2000/2005 Related Free Snippets.

Solution/project structure


Hello, I am working in a aspx web application that must be built in several separate "modules" with different functionality which will be partly developed by different teams.

However, I need the completed app to reside in ONE virtual directory. There will be a single startup page. I need session state to be preserved across pages in different modules.

I structured it as one solution with different Web Projects and one class library project with common functionalities.


1) is this the right approach to do this? Or which one would be better?

2) each time I add a new web project to the solution, a new web.config gets created. What do I do and where do I put them?

VS 2010 + framework 4.0 + TFS

Regarding TFS and source control, I have a single Team project, the solution and web projects are inside it.



Arabic QueryString with Url Rewrite Solution


Alsalamo 3alaykom ,

as we know that if you use Intelligencia.UrlRewriter.RewriterHttpModule or IIS URL Rewriting , we will face problems with arabic urls

as this

http://localhost:1234/Pages/???? ?????? ?????? ??????????

and the Rule is :

<rewrite url="~/Pages/(.+)" to="~/ShowPages.aspx?Page=$1" />

you will recive the QueryString["Page"] Like this

نائب العميد للشؤون الأكاديمية

so it's a big problem , and there is a solution that is :

remove the Rule of that rewriting ,,

<rewrite url="~/Pages/(.+)" to="~/ShowPages.aspx?Page=$1" />

then open your Global.asax file and Application_BeginRequest method exactly

use the following code to handle you request

void Application_BeginRequest(object sender, EventArgs e)
if (HttpContext.Current.Request.Url.ToString().Contains("/Pages/"))
	String[] txt= Regex.Split(HttpContext.Current.Request.Url.ToString(), @"/");
	String page = txt[txt.Length-1];

Best Way to Upgrade Using Web Setup Project


Hi there,

I am using VS2005.

I don't have much experience with web setup projects, but I now need to create a decent windows installer in order to allow customers to install one of our web applications. I have created a simple web setup project and it works fine, but not when it comes to upgrades of the application.

If for instance I install version 1.0 on a machine, and then later I try to install version 2.0, I don't seem to have the control that I would like... I can specify in the web setup project that the installer must enforce an uninstall of previous version, but then all application files and logs are uninstalled as well. If I let the application just install itself over the older version, it seems to leave some old DLL's there - it then causes issues in the application because DLL version conflicts.

My basic requirement is that I would like th installer to upgrade the old version with all the files required, but leave any application and log files in tact - this way the customer won't have to reconfigure the application after install.

What is the best way to handle this?

AD FS 2.0 in Identity Solutions: Using Active Directory Federation Services 2.0 in Identity Solution


This article explains how you can use Active Directory Federation Services (AD FS) 2.0 to claims-enable Windows Communication Foundation (WCF) services and browser-based applications. The focus is on the token issuance functionality in AD FS 2.0. You'll find out how to use AD FS 2.0 as an identity provider; set up an AD FS 2.0 security token service (STS) to interact with WCF; federate AD FS 2.0 with your custom STS or another AD FS 2.0; enable Web single sign-on and federation with WS-Federation and SAML 2.0 protocols; and externalize authentication logic through Visual Studio. You'll come away appreciating how AD FS 2.0 and Windows Identity Foundation make programming identity solutions in Windows less of a chore.

Zulfiqar Ahmed

MSDN Magazine November 2009

BizTalk EDI: Build a Robust EDI Solution with BizTalk Server


We introduce you to the EDI functionality within BizTalk Server 2006 R2, illustrating schema creation, document mapping, EDI delivery and transmission, and exception handling.

Mark Beckner

MSDN Magazine August 2008

Security: Safer Authentication with a One-Time Password Solution


One-time passwords offer solutions to dictionary attacks, phishing, interception, and lots of other security breaches. Here's how it all works.

Dan Griffin

MSDN Magazine May 2008

Office Development: OBA Solution Patterns In The Real World


OBA solution patterns help architects and developers build Office Business Applications (OBAs). This article introduces the seven core OBA solution patterns and applies one to a real-world problem.

Steve Fox

MSDN Magazine March 2008

Office Space: Solution Deployment with SharePoint 2007


WSS 3.0 introduces a new deployment mechanism that lets you move your development efforts into a staging or production environment.

Ted Pattison

MSDN Magazine August 2007

Extreme ASP.NET: A New Solution to an Old State Storage Problem


State management in Web applications is a contentious issue. Should you store user data per session or should you persist it across sessions? You can easily store information temporarily while someone navigates your site by using session state.

Fritz Onion

MSDN Magazine April 2006

Who Goes There?: Upgrade Your Site's Authentication with the New ASP.NET 2.0 Membership API


Here Dino Esposito and Andrea Saltarello cover the plumbing of the Membership API and its inherently extensible nature, based on pluggable providers. To demonstrate the features, they take an existing ASP.NET 1.x authentication mechanism and port it to ASP.NET 2.0, exposing the legacy authentication mechanism through the new Membership API.

Dino Esposito and Andrea Saltarello

MSDN Magazine November 2005

Inside MSDN: Using InfoPath as a Reporting Solution


I love the part of my job that lets me write code and develop software. In addition to those responsibilities, however, I manage a development organization that's working on a number of large strategic projects.

Larry W. Jordan Jr.

MSDN Magazine March 2005

An example of packaging web application containing database upgrade SQL file

A few months ago, we have a blog talking about extending the web publishing pipeline to package database project deployed SQL file.  In this blog, I'll show step by step example of packaging web application with SQL Server database upgrade SQL file using Visual Studio 2010.  This way, we can generate a web package with incremental SQL script to certain database version.  The scenario may help distributions of a web upgrade package which needs to be installed on many different locations, each with their own SQL server database.   1. Create a Web Application Project 2. Add a new "SQL Server 2008 Database Project" to the solution 3. Prepare a development database, such as my test1 database as the following: 4. Right click our...(read more)
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend