Tag Info

Hot answers tagged

11

SharePoint solution packages consist of a .WSP file that you can create using Visual Studio (or manually if you so wish). Before deploying to a production environment, I recommend you take a look through Deploy solution packages (SharePoint Server 2010). Basically you need to add your solution to the solution database of a SharePoint Server farm using the ...


5

There are two ways to look at this concern. First is to literally take what Microsoft says in face value, because they are most of the time correct about the operational best practices for their own products. Said so, if you follow the guideline mentioned here http://technet.microsoft.com/en-us/library/cc678868(v=office.14).aspx It says Additional ...


4

Setup a content deployment job. Do a Backup-SPSite, Restore-SPSite Use the content deployment wizard tool (Neeed to install this on both servers for export, import) Database detach and reattach. (4) is laborious and it also seems to retain webapp urls as-is. So you will see http://test urls in your content after you move to prod. I'd do #2 or #3 (if you ...


4

Ok there are a few ways to do it: "Save as template" and include content (The amount of content is limited but should be enough in most cases) Database backup/restore as PirateEric wrote Granular backup in the CA (To find in Backup and Restore / Granular Backup) You can then select a site or List and export it. It can include the permissions but I am not ...


4

I'd say either a content database detach and restore into production, or using stsadm/powershell to backup the site collection and restore into production.


3

The deploy action creates a .WSP file in your bin\debug or bin\release folder...depending on what you built. You can use that file to deploy the solution...everything you need should be in that package assuming the package was built correctly. MSDN reference on deployment here: http://technet.microsoft.com/en-us/library/cc262995.aspx


3

Maybe overkill for you what you need, but if you haven't got it already, get SharePoint Manager. Allows you to view every object in a SharePoint Farm and view all it's properties. http://spm.codeplex.com/


3

I guess this depends largely on the complexity of your solution. Testing your WSPs on a blank Pre-production server with a single web application would be a good start. I'm curious though - why backup/restore the web application? If you have branding, list definitions, content types to deploy, these can all be created in VS2010 projects then bundled out ...


2

What are you looking to stage? Content or functionality? I'm absolutely for having multiple environments available for testing functionality, but I don't see value in duplicating complete content sets for an entire environment. In addition to the pain and time involved with setting it up or synchronizing it, you have the cost for storage. In the ...


2

As you seem to want to do this in production mode, I would suggest looking at a supported third-party tool. It may be overkill in your case (and over budget too!). You will need to weigh your needs versus the additional capabilities these types of tools provide. Two tools that come to mind are: AvePoint DocAve Replicator Repliweb Operations Suite for ...


2

You need a slash at the start of the ItemUrl parameter. Your command should look like: export-spweb http://mysite -itemurl "/lists/mylist" -path "c:\temp\mylist.cmp" Reference


2

From the research I did, it appears that I do not need anything special for SharePoint Foundation website to run on an internet facing site. However, I need valid licenses for Sql Server and Windows Server. I also need to abide by Microsoft's EULA. Hope this answers the question for someone else.


2

The first thing you may want to make sure is event receiver was attached to the list. Following is a powershell script which can help you enumerate the list of event receivers: $webUrl = Read-Host "Provide web url:" $listUrl = Read-Host "Provide List url:" $web = Get-SPWeb $webUrl $listUrl = $webUrl + $listUrl $list = $web.GetList($listUrl) Write-Host ...


2

If you WSP contains only Event Receiver, and no web.config entries (which event receivers do not need), it will always appear as "Globally Deployed" in central administration. Even if you try to target to specific web application, you may get following error: If it contains other artifacts which requires web.config entries, I suggest you deploy to only ...


1

By default, the SharePoint_Config database is set to Full recovery model. But, Microsoft recommendation is to set the recovery model for your SharePoint_Config database to simple in production (reference: http://technet.microsoft.com/en-us/library/cc678868.aspx). You can change the recovery model for SharePoint_Config after you create the SharePoint_Config ...


1

export-spweb http://servername/sites/PonniTest/ -itemurl "Lists/Try" -Path C:\raks.cmp Note: Your Url should be terminated with a slash.


1

You can try workflow import/export feature to deploy your workflow to your production environment. Check the following link to import/export your designer workflow: http://blogs.technet.com/b/wkng/archive/2012/08/21/exporting-and-importing-sharepoint-designer-2010-list-workflow.aspx


1

That document describes production environments Do not put SQL on the same box as SharePoint on your live environment. Doing so will kill performance, but is fine for dev environments. You will need to split out SharePoint and SQL onto separate servers. If you plan to deploy Office Web Apps or Search you will definitely need yet another server for each of ...


1

'1a1f1126-a013-4408-8771-b279696fbb11' is not a standard Feature so I'll assume that it's your own feature. You can check that by double clicking the feature in Solution Explorer and look for "Feature Id" in the properties window (F4 if not open). I guess that some thing went wrong in the deploy part. You write that you've created a Visual Web Part of your ...


1

The "Save site as template" option for sites with publishing feature is not supported from Microsoft. Its not supported for 2007 or 2010 officially. But many have tried using it with certain precautions like publishing all the pages and files before saving as template, etc. And it has worked too. But its never guaranteed from Microsoft and the pros or cons ...


1

It is working now. Few values were getting null values so I put conditions for all those values. string client = (string)properties.ListItem["Client"]; //replaced by string client = ""; if (properties.ListItem["Client"] != null) { client = (string)properties.ListItem["Client"]; }


1

Can't get SharePoint Manager to work for the life of me. Why should we have to depend on 3rd party products to do our jobs? This is microsoft software after all! I have a similar situation in that I've developed a package with two lists with 'on item added' event receivers. I import csv files to the lists via powershell and on my development server the ...


1

Alternatively you can create some .bat files and then run them from command prompt as Administrator: 1. Add.bat "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm.exe" -o addsolution -filename "C:\YourSolution.wsp" "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm.exe" -o deploysolution ...


1

Sharepoint Manager (as suggested by James) could be your first choice. If that is not allowed in production, PowerShell can help you. Following command would give you what you need $web = Get-SPWeb [URl of your web site] $web.Lists | Select Title, ID


1

We use the SharePoint Deployment Content Wizard to migrate content from prod to staging. It is good for the QA testers to work with actual data and it is good to test staging with as close an environment as production (amount of data, load, etc.). For key sites that require a more frequent refresh we will script the content refresh and schedule it. To ...


1

There are several SharePoint ISV's making great products out there for this type of scenario, depending upon your failover limits and the type of output storage needed. The 2 best are Quest's and AvePoint's recovery tools for ease-of-use and cost, but there are also several others (e.g. Symantec, Microsoft, etc.) depending upon how much infrastructure you ...



Only top voted, non community-wiki answers of a minimum length are eligible