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

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

Best Practice to deploy update packages on a production ASP.Net solution

Posted By:      Posted Date: September 15, 2010    Points: 0   Category :ASP.Net
Hi guys, I've a production web site.  It was deployed/installed using a standard MSI project.  But now, I'll like to create a kind of MSI package containing only those components affected during a fix.  Everytime I fix something in the solution, I've to manually copy/paste all modified components (ascx,aspx,dll, etc) to the web server.  Of course, I've a staging area from where I can validate that my package is completed and I'm not missing anything.  But I'll like to avoid this manual-risky-prompt-error process.  That way my fixes packages will looks more professional and I could even have our web manager deploying fixes on this production box. What folks do to deploy fixes? Any ideas? Thanks.  

View Complete Post

More Related Resource Links

How to deploy and configure ssis packages using sql server table in testing server and production en

Hi We have three environments (development, testing and production ) I have to configure and deploy the ssis packages using sqlserver table in different environments(development, testing and production).   Three environments database structures  are same But database names are different like (DEVSERVER,SITSERVER,UATSERVER) We have 14 packages and one master package. In master package we called all 14 packages question1 First time i will deploy all (master and 14 packages). If i modify one package we need to deploy all the packages or single package deployment is enough    Please help me thanks in advance          

How to deploy ssis Packages to production Environment


Hi All,

I have a few questions regarding ssis package deployment to production environment.

In order to deploy already developed packages ...These are the things I am following...Please confirm whether I am following the correct approach...or not.. If not please let me know the exact process..

First of all I am generating the scripts for databases...corresponding tables,views and stored procedures..

Once the scripts are ready... I am executing those scripts in production environment.

After that I am adding all of my developed packages to production environment BIDS Platform. Then I am running these packages in production environment (All connection strings are updated in the configuration file)...by changing the Configuration file..

Then I am scheduling all of these packages through SQL SERVER JOB AGENT.....

Is this the right approach ...? Please let me know ASAP...







ClickOnce: Deploy and Update Your Smart Client Projects Using a Central Server


ClickOnce is a new deployment technology that allows users to download and execute Windows-based client applications over the Web, a network share, or from a local disk. Users get the rich interactive and stateful experience of Windows Forms, but still have the ease of deployment and updates available to Web applications. ClickOnce applications can be run offline and support a variety of automatic and manual update scenarios.Learn all about it here.

Brian Noyes

MSDN Magazine May 2004

Solution Full Update


I make a project based on WSPBuilder, add there an event handler, compile code, make wsp, deploy.

For the first time i have exact reaction from site as i intended.

Then i retract and delete solution and make several changes to elements.xml. Changing binding of list for exmaple from custom list to tasks:

from <Receivers ListTemplateId="100"> to <Receivers ListTemplateId="107">

Then i go all the way back to solution deployment.

But when i try to fire some events i dont get the effect.

As i`ve found out dll changes are deployed nicely. So if i change cs code i see the effect, but any changes in xmls go nowhere.

Only way no is to make it in a new project.

So how can i update these xmls on portal ?

I see xml are changing corerctly in feature\myevent.

Here is deploy script:

stsadm -o addsolution -filename WSPBuilderProject1.wsp
stsadm -o deploysolution -name WSPBuilderProject1.wsp -allowgacdeployment -immediate
stsadm -o copyappbincontent


Here is retract script:

stsadm -o retractsolution -name WSPBuilderProject1.wsp -local
stsadm -o deletesolution -name WSPBuilderProject1.wsp


What am i doing wrong ?

Update a VS solution after "Import SharePoint Solution Package"

Hi, having created a VS project from an exported SP solution, how to keep pages / content types / lists etc in sync when changing them on the SharePoint side via the web UI or SharePoint Designer? Thanks

Reg deployment of solution packages in SharePoint 2010 from MOSS 2007

Hi, Earlier we have developed some custom web parts,features and deployed into the site through solution package(wsp files) when customer was using MOSS 2007.Now customer is migrating all sites into SharePoint 2010.Now my query is can i use the same solution to deploy into the site through Central Admin of SharePoint 2010 or is there any seperate process for that? Thanks & Regards, Sudheer

BCS: Best practice of Toggling external content types between staging and production databases



Environment :
Sharepoint 2010
using BCS to point to external database
create two Secure Store Application ids , one with production credentails and another with staging credentails

I have several external content types (ECT) using an external system(ES) pointing to staging databases.
Now i want to change only one of my ECT to point to production DB but suprisingly the only way i could achieve this was by modifying the ES that all the other ECT are using, this is not practicaly because this makes all the ECTs point to production and not just the one that i want.

Question is how can i have different ES and how can i make only one ECT out of all the ones to point to production, i tried using the "Switch connected systems" but did not like it and below are the details:

Created a new ECT pointing to production which would show the ES being used in BCD services and then i  used the "Switch Connected Ssytems" option under designer to switch the staging ECT to the production ES. Dos the job but the problem is that if there are no ECT pointing to staging ES then it does not appear under BCS services which mean neither can i switch my ECT back to it nor would it be available when i am creating new ECT whch need to point to staging.

Hope i was clear, please suggest how to handle this sit

Create Custom Site Template & Deploy as Farm Solution


So I've seen a few posts and blogs about this, but nothing with the specific error I'm getting.  All I'm trying to do is create a custom site template from an existing site (now WSP), and make that custom template available in CA so I can create host-named site collections from that template in PowerShell.  Apparenly this was a lot easier in 2007, as you could just save your template as STP, and run some stsadm addsolution to get it in the farm.  With 2010, I've read there are 2 options:

  1. Install-SPWebTemplate
  2. Deploy via Visual Studio 2010

I've tried running Install-SPWebTemplate (which only takes CAB files), and NOTHING I do works.  I've created a cab from the WSP with makecab, I've renamed the WSP to CAB, and all I get is "cannot find or parse web template file".  So on to VS2010.

Using this article as a guide (http://msdn.microsoft.com/en-us/library/ff408263.aspx), I created a new 2010 Import existing solution project, left all items selected, and the import was successful.  I made a change or two to the ONET.xml to fix some things, and then I just try to deploy it to the farm.  Whether I set the URL to the root intranet site, or the CA URL, I get deployment conflict errors:

"The URL or

Can't deploy SharePoint solution even after changing Site Url property



I've developed a SharePoint 2010 solution in VS2010 and i've also deployed it on my site collection - everything works perfect, fine!

But when I try to deploy the same solution in another site collection (on local server not remote) by changing Site Url property of the solution to my new site collection, VS is not deploying the solution. I'm getting the following error:


Error 102 Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site: http://newsiteurl/. Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project.


I've packaged the solution and deployed it manually, it's working fine but i don't understand why i'm not able to deploy the solution on a different site collection on the same machine??

Does anyone else has experienced the same issue? 



Thanks & Regards,


deploy test site collection to production

I have developed sp2010 site collection at my  end and want to deploy to the client at different geo location. this site collection have bunch of sites, features and custom webparts. please let me know, the best of doing this! thanks.

Best way to update a Sharepoint 2007 custom list schema after it has been deployed to production


What is the best way to update a Sharepoint 2007 custom list schema file (that is deployed using a feature) after the list has been deployed to production.


Scenario: We have custom list based on a custom list definition and template that we have deployed to production. Users have added items to this list and also added their own new columns to this list apart from what we originally included. Now I want to update this list schema (add another custom column). Whats the best way to achieve that?

Also, a related question is that if a new <field> entry is added to an already deployed schema file, will pushing the new schema file to the right place be enough or will a feature deactivation/activation also be required? I have noticed that some changes to schema files are picked up without the need to deactivate/activate the feature. But whats the general practice for scenarios like this?

Deploy web part to production server


I develop my visual web part on a development machine running windows 7, SharePoint foundation server 2010 and visual studio 2010,  

I have SharePoint 2010 production server, and I deploy the web part as the instructions using the following line


stsadm -o addsolution -filename <yourfilename>.wsp

Deploy and use a WSP solution: how?


Hi All,

I'm trying to deploy a 2007 solution into 2010...

the solution is the following: http://www.hezser.de/blog/archive/2009/05/22/navigation-for-wikis.aspx (it is a really cool tree navigation wiki)...

the solution is for 2007, I'm trying to deploy into 2010...

the following summarize the steps followed:

- Download the WSPBuilder for 2010 (http://wspbuilder.codeplex.com/releases/view/30858)

- Installed Visual Studio 2010 and installed the WSPBuilder

- Open the 2007 Solution Source Code (http://www.hezser.de/blog/archive/2009/05/22/navigation-for-wikis.aspx) and converted into 2010 version (NO ERROR DURING CONVERSION)

- Opened a Command line and Added the Solution  (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>stsadm.exe -o addsolution -name WikiNavigation.wsp)

- Deployed the Solution (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>stsadm.exe -o deploysolution -name WikiNavigation.wsp -allowgacdeployment -immediate)

- Got the following result: Timer job successfully created.

- Navigat

Sharepoint solution that calls WCF services has performance issues on production machines


I've a SharePoint solution that consists of set of webparts and other features. The webparts backend call a set of WCF web services. When I tried to install it on a production machine, it has some performance issues, I can open the page and wait for 30 min till it response to me.

If I call the same WCF services from a console application they works fine in both machines, if I creates a SharePoint team site it works fine in both machines, everything works fine on the dev machine.

The WCF services do some CRUD operations in a database and some API calls to SharePoint and PerformancePoint APIs

Development machines Specs:


Windows Server 2008 R2 Enterprise, 64-bit

How do you deploy a feature for sp2010 containing a whole branding solution?


Im attempting to create a sharepoint project, with one module containing a master page, stylesheet, theme and images to provide a clean, accessible and reuseable feature with this complete rebranding solution!

But im finding that i get an error when the deployment tries to activate the feature, i will want to move on from this when it finally works and create event recievers to setup the files to automatically install and use the template and themes files with a stylesheet.

Error: Error occurred in deployment step 'Activate Features': Feature with Id '{ID HERE}' is not installed in this farm, and cannot be added to this scope.

How to deploy SharePoint Designer Workflow to Production without using SPD

I created a few workflows using SharePoint Designer on the development server and now I want to deploy those workflows to production server. As the SharePoint Designer access has been blocked on the production environment, how am I going to deploy them? I saw some articles on the feature deployment, however it mention this is not officially supported by Microsoft. Is there any other ways? And I also need the detailed steps on the SPD workflow feature deployment if that works. Any reference? Thanks in advance.

Deploy and update script file with custom ribbon tab to Sharepoint Server 2010


Hey everyone,

currently I'm building a custom tab for Sharepoint Server 2010 and at the moment I'm stuck on the following issue,
with the first debug deployment Visual Studio sends the .js file that provides some functions for the ribbon elements from Scripts folder in the VS project
to Sharepoint Server.
However, it won't apply any changes I did on the script afterwards to the file on the server.
So the effect is, that as soon as I do the next debug, the previous script is being used by Sharepoint and the new version, containing the new code, is left aside.

It seems to me as if Visual Studio would only deploy the .js file just once and then rely to this copy, maybe there are some configuration settings to make, but after hours of research, I still can't figure out where things do go wrong or what configuration to apply to update the script on the server.
I couldn't locate the file on hdd either, even searched the whole fs but the results showed only the new script file.

Any help on this would be very much appreciated, this issue drives me nuts and consumes plenty of time ;)

Workaround at the moment: each time the script is changed, set up new project... :D

Greets, Norman

P.S: Yes, I did flush

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