Is there any other ways of exporting a sites as solution in SharePoint Foundation 2010 except through "Site Settings -> Site Actions -> Save Site as Template"?
Seems to be the only way, just to make sure I'm not missing anything (through the designer probably? There's an option in the designer, but it brings you to the same "Save Site as Template" page)
Thanks!
In the out-of-the-box UI that's the only place to export a site, but note that unlike sp2007 this now export your site as a wsp-package
In the object model there are a couple of ways to export the site:
SPWeb.SaveAsTemplage
SPSolutionExporter.ExportWebToGallery
SPSolutionExporter.ExportWeb
AS part of Microsoft Course 10325A - Windows PowerShell 2.0 - backup / restore site collections.
PowerShell creates Cabinet files or .CAB files - http://en.wikipedia.org/wiki/Cabinet_(file_format). One nice thing about PowerShell is automation and you can easily perform the same task as you would via SharePoint 2010 Central Administration, in the Backup and Restore section.
Being scripted, you can provide any extension for your backup file. Extract and View the archive contents and modify, using "Extract.exe", provided with early versions of Windows and replaced in XP with "Expand.exe".
Rebuilding modified CAB files, is achieved with "MakeCab.exe", the Microsoft Cabinet SDK "CabArc.EXE" or any application supporting "application/vnd.ms-cab-compressed".
To restore a site collection using Windows Power Shell, from the Start menu, All Programs > Microsoft SharePoint 2010 Products.
Open SharePoint 2010 Management Shell (launch with Administrator rights, if required by right click and choosing "Run as Administrator").
Backup-SPConfigurationDatabase
Backup-SPFarm
Backup-SPSite
Get-SPBackupHistory
Restore-SPFarm
Restore-SPSite
The most fitting to your requirement;
Backup-SPSite
Restore-SPSite
Backup-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak
Restore-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak
Great book filled with automation scripting with PowerShell, the book by Gary Lapointe - Automating Microsoft SharePoint 2010 Administration with Windows PowerShell 2.0
.Net namespace for C# code within PowerShell or PowerShell within.Net applications;
Microsoft.SharePoint.Publishing.Administration
Related
I am fairly new in SharePoint Development and configuration. I need to create a list that when a entry is created, it will email the selected person to approves the entry.
Right now, I have already created the list and will be setting-up the workflow configuration, but the problem is that the 'Approval-SharePoint 2010' Workflow template is missing.
How can I work around this? Or can I download the template and install it in the Server SharePoint 2013?
You haven't mentioned which version of SharePoint you are running. I presume because you don't have the option available you are running SharePoint 2013 Foundation.
SharePoint 2013 Foundation doesn't use support the Workflow Manager and uses the same workflow engine that SharePoint 2010 Foundation uses- this doesn't include the approval workflow.
The Approval-SharePoint 2010 workflow template comes with SharePoint Standard or SharePoint Enterprise. See here for feature comparisons between versions:
https://blog.blksthl.com/2013/01/14/sharepoint-2013-feature-comparison-chart-all-editions/
Unfortunately, having tried various things myself, the options are upgrade to at least SharePoint standard or build a custom workflow. Customer workflows can be built using SharePoint Designer or as part of a code solution. There are quite a few guides already out there. This is just the first one I came to:
http://plexhosted.com/billing/knowledgebase/226/How-to-create-a-simple-approval-workflow-in-SharePoint-Designer.html
If I am being too presumptuous and your version is higher than Foundation then it might just be that you need to activate the Workflows feature in the site collection features.
Our company has a SharePoint server where we have to store all of our documents, our TFS 2013 has links to this SharePoint server. We have been told that the company is getting a new SharePoint server which will have a different url
This means that all links within our TFS need to be repointed to the new SharePoint site
Does anyone know of a way to change the links without someone having to go in to each PBI; see if it has any links; if it does then remove the old link and add a new one?
We have 100's of documents and would rather not have to do this manually so any help will be much appreciated
This is all beyond my control, all I've been told is they are migrating our SharePoint site to another server...
You can write a PowerShell script that will open all PBIs and change the links to the new SharePoint. In order to get access to TFS from PowerShell scripts you have to install Team Foundation Server 2013 Power Tools and check the PowerShell Cmdlets option during installation.
I was unable to work out how to do this using the PowerShell Cmdlets but I have been able to write a program to do this using Team Foundation Work Item Tracking Client
I have looped through each of the work items and their external links, if the link is to our old SharePoint site then:
I remove the old link
Add a new link with location of the same document on the new SharePoint
Will we be able to add .NET code blocks to a page in SharePoint 365 - the cloud version of SharePoint? If so, how do we allow code blocks in the web.config?
Will we be able to use SharePoint designer to customize forms and create dataviews with external datasources?
Can we have asp.net codebehind files and class references? (I suspect not)
.NET code blocks (server-side scripts) are not supported in Office 365. You should build your ASPX page purely from controls and web parts, which would contain the code. Solutions for the SharePoint Online share their restrictions with sandboxed solutions for SharePoint 2010. The solution scope is a site collection; not a web application and thus you cannot access the web.config. However, you may not need to; you're bound only to a single site collection and the most usual task - adding SafeControls - is supported, although the SharePoint engine does not use web.config to maintain them. You can see an example of deploying a web part.
You can use the Designer to customize pages, forms and views. External data sources (entity types) - BCS - were added to SharePoint Online by the end of the last year. I haven't checked what connector types are supported; I presume SQL and WS sources, at least.
You cannot have the code-behind in ASPX pages. There is no ASP.NET compilation of pages and user controls available; that's why you have to compose your pages of coded controls and web parts only. However, there is a trick to circumvent this - the Visual Web Part. The original visual web part could not be used in a sandboxed solution because it relied on the ASP.NET compilation. There is a template available in Visual Studio 2010 SharePoint Power Tools that packages pre-compiled code to the solution and is friendly to the sandbox.
You can develop and test your sandboxed solutions on your local SharePoint 2010 prior deploying them to the SharePoint Online. Although I was surprised that deployng a solution to the SharePoint Online was kind of faster than to my local farm :-) MSVS makes the development really comfortable.
--- Ferda
Not being a .NET developer, here is my limited knowledge. Office 365 is a multi-tenant implementation of SharePoint and you you should have the following capabilities:
upload code blocks as sandboxed solutions
ability to customize forms and data views with SharePoint Designer
Note that Office 365 offers 30 day trials that would allow you to test drive it. Let me know if you need more details as there are a couple caveats to be aware of when you start a trial.
This question relates to how to implement what Mr Prantl suggested.
Where to write C# code for office365 sharepoint site
Hope this helps.
Using SharePoint 2007, how could I allow the adding of CEWP's to the selection menu of an "Add a Web Part" dialog while in Edit Page mode? As of the moment, I can only add Announcements, Calendar, Links, Shared Documents, Tasks but I do not have the ability to add a CEWP. I have full access to the site.
At Site Settings > Site Features > Site Collection Features, you will want to have the Office SharePoint Server Publishing Infrastructure set to active.
Then, on the site, go to Site Settings > Site Features, and activate the Office SharePoint Server Publishing feature. You should then be able to add the content editor web part to the site.
Quite often I see SharePoint 2010 websites without the Content Editor webpart (MSContentEditor.dwp)
To enable this web part you need to activate the BasicWebParts feature on that site. I did not find an option to do this by the web site admin; you can enable the feature however by using SharePoint powershell.
Execute the following statement in the SharePoint Powershell and the Content editor web part will be added to your site
Enable-SPFeature 00bfea71-1c5e-4a24-b310-ba51c3eb7a57 -Url [SharepointSiteUrl]
To get the SharePoint site url just run
Get-SPSite
Gertjanvanmontfooort blog
I ran into a similar issue in SharePoint 2010, but I couldn't see other webparts due to my user permissions on the Site Collection. After getting "Restricted Read" rights on the Site Collection I could see all of the different WebParts.
Here is what helped me fo Sharepoint 2013 Online (Office365):
http://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_manage/problems-opening-a-site-from-sharepoint-designer/d1e71427-be3f-4ea7-be3b-8ba6b64af76c?page=2&auth=1
Basically, I had to set flag DenyAddAndCustomizePages to 0 using sharepoint power shell.
Moreover, from time to time I had to reset the flag to 0 as the online sharepoint seems to reset it to deafult 1.
After trying all the above, and other proposed solutions, my eventual success was through PowerShell script. Admittedly I did check that Custom Scripts was permitted and I did have to Activate the two "SharePoint Server Publishing" features described above, but as I am using a sub-site I presmume something else must have been messed up. In the end the following script allowed me to see the Content Editor option when adding a Web Part:
SET-SPOSite -DenyAddandCustomizePages 0
The full article can be found here:
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_manage/problems-opening-a-site-from-sharepoint-designer/d1e71427-be3f-4ea7-be3b-8ba6b64af76c?page=2&auth=1
It is a real pain to deploy my InfoPath 2007 Forms from the designer into our development environment's SharePoint server. All of our forms require "full trust" since they include business logic written in C#. Here are the manual steps:
1) Run the "Publish Form" wizard in InfoPath, specifying the target site to publish to and location to save the xsn file.
2) De-activate the existing version of the form from the site collection features (if an older version exists).
3) Log into Central Admin on the development server. Navigate to Application Management -> Manage Form Templates and upload the xsn file.
4) Activate the form as a site collection feature.
Does anyone have an idea how this can be automated? Maybe via stsadm?
You can package InfoPath forms in SharePoint solutions (WSP files). These can be deployed by making use of STSADM. For more information:
http://blogs.importchaos.com/alonsorobles/2008/06/04/creating-a-sharepoint-solution-for-an-infopath-form-template-deployment/#comments
http://www.crsw.com/mark/Lists/Posts/Post.aspx?ID=37
http://blah.winsmarts.com/2008-8-Deploying_InfoPath_2007_Forms_to_Forms_Server_-and-ndash_Properly.aspx
We can build our own service to deploy the InfoPath form in Share point Server. I have developed the service to solve my problem.
I have used “STSADM” command to deploy the InfoPath form. You have to understand the STSADM syntax so that you can build the script to deploy the InfoPath form.
Here I have summarized what I did. It may useful for you to start.
I developed the web service that will construct the script using STSADM and save it as bat file and run the batch file using Process command available in C#.
Another couple of options are:
1) After running the "publish form" wizard use a batch file with stsadm commands as per the following blogpost:
http://sharenotes.wordpress.com/2008/03/18/using-stsadm-to-deploy-upgrade-update-infopath-forms-templates-with-managed-code-behind/
2) Use the InfoPath Form Deployment Tool on Codeplex (or you can simply use the tool to generate the batch files):
http://www.codeplex.com/InfoPathFormsInstall