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 ...
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
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 can ...
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 ...
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
Best way to move SharePoint solutions is using .wsp file which is created as you deploy any solution just copy from development, paste in production and then add and deploy solution there by power shell.
To move list use export functionality in central admin of development and then import the .cmp file in production.
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 ...
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 ...
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)
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 ...
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.
Dylan's answer is correct - you need to reset IIS so that the Web Worker Processes can pick up the new DLLs.
There is an easier way to update a farm solution, and that is the Update-SPSolution cmdlet. If your changes or bugfixes are primarily in the code-behind of the webpart, this will successfully update the .dll or any .aspx/.ascx files associated with the webpart without having to do a full retraction and re-installation. Please note that the documentation ...
You could use a custom list for products. Create columns for that list, so every item in that list will describe your product (Product Title, Category, description, price, version, anythingelse).
For every item in sharepoint list you could add attachments.
This is not related to SharePoint but to your management and company. There is always a Change control method that you can implement, you do not need some fancy software just the willingness of the people to participate. If you are the manager of the developers it should be easy to impose, if you are not their manager then it's about internal politics.
I have seen this happen if you try to add a record in a view that doesn't contain all the "required" fields. If you want to add a record you'll need to do that on a view that has all the required fields in "All Items" view.
Check below methods:
This happens when another person tries to add or delete a column from the list while you are edit content in datasheet view. If you are consistently getting this error, it will help to use the ribbon to switch to "standard view" then back to "datasheet view" to allow the changes to 'sync up'. It's important to realize the possibility ...
Unfortunately in this scenario that you described there is no way to update the package without the end user notice the maintence.
In a mid-term solution, i strongly recommend you to gradually migrate your solutions to a Sharepoint Provider-hosted Add-Ins/Apps, then you can make your changes without stop the entire site.
Here some links to help you:
What about a normal list but make a custom field where you can add the different properties and a field to add attachements (like your pdf/excel)?
This is achieved by adding a 'add attachement field' in list design mode.
I think I found an answer but not in powershell. Content Migration object model says:
Content Migration object model:
The object model provides the most control over your data migration scenarios. Using the object model, you can migrate anything, from a Web site to an item in a list, or a single document in a library. You can choose whether to include ...
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:
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 ...
'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 ...
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 ...
It is working now. Few values were getting null values so I put conditions for all those values.
string client = (string)properties.ListItem["Client"];
string client = "";
if (properties.ListItem["Client"] != null)
client = (string)properties.ListItem["Client"];
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 ...
Alternatively you can create some .bat files and then run them from command prompt as Administrator:
"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 -...