Recently, together with my colleague Martin Schmidt, I gave a session on MOSS 2007 to SharePoint 2010 migration. Among other things I mentioned that the site template .STP files are no longer supported in SharePoint 2010. STP files are still supported for list templates, though.

1. Download Convert Stp To Wsp For Windows 10 Oikos Activator
2. Download Convert Stp To Wsp For Windows 10 Oikos 64
3. Download Convert Stp To Wsp For Windows 10 Oikos 8

From my professional experience I know that there are many people who have a lot of site templates in .STP format and they don’t want to lose their work. Microsoft suggests that the right way is to create a site with each template, upgrade to SP2010 and then save as WSP template in the new version. It’s an overkill, if you ask me.

Sep 08, 2015 Here change your WSP file name and your path what you actually want it to be. Save the notepad document with.ps1 extension. Open SharePoint 2013 Management Shell. Go to Start, then All Programs and select Microsoft SharePoint 2013 Products.

• Save the site as a template and download the wsp; Extract the contents of the wsp; Remove enterprise references in the Onet.xml file I removed all site features in the configuration section. Create a ddf instruction file Here is my ddf T4 template: Re-package the wsp makecab.exe -f ddfPath.ddf.
• Can you convert this to be feature driven and use a WSP instead? Solution packages are standard. Going forward with SP2010, STP files are no longer supported. If you are going to use STP, make sure you have all your templates and web parts installed first. The rule about templates is they are based off some site definition.

My goal is to create a converter written in .NET that would crack open an STP site template and write a shiny new WSP file with the same structure. You will follow my journey in the following days.

An .STP Site Template

Let’s create a normal site, with blank site template. I will add a document library and a webpart to expose the library on the default site page.

Now, save it as a STP file by going to Site Settings / Save Site as Template option.

The template is now safe in the Site Template Gallery in the root of the site collection.

Prying the Lid Off

Let’s download the STP file and extract its contents with the Microsoft Cabinet SDK Tools.

In this case it’s only a single manifest.xml file. A quick inspection reveals that it has the site template header and a site definition metadata.

Opening SharePoint Manager 2007 to inspect the source web raw properties, we see that there is a clear mapping between the <MetaKey> tags and the site property bag:

Furthermore, the manifest.xml file keeps reference to the original site definition (in this case, “Blank site”) from which the original site is created.

I’ll keep investigating. The rest of the story, in Part 2, soon.

Download Convert Stp To Wsp For Windows 10 Oikos Activator

If you have two similar lists in two different site-collections in SharePoint and want to copy an existing workflow from site A to site B you can follow the process below.

To copy the workflow simply open site A in SharePoint Designer and browse to the wanted workflow. Then press the Export to Visio button

Save the .vwi file on your hard drive, then and rename it to .zip.

Say yes to the dialog

Download Convert Stp To Wsp For Windows 10 Oikos 64

Unzip the file and delete the xxxxx.xoml.wfconfig.xml file

Then re-zip the remaining files.

Download Convert Stp To Wsp For Windows 10 Oikos 8

Finally change the file extension back to .vwi.

Open up site B in SharePoint Designer and import the workflow via the Import from Visio button on the File Tab and select to which list it should associate.

Note! If your workflow is using other lists than the associated one these references need to be reconfigured within the workflow in the usual way.

Did this article help you today?

• Log in to post comments

Comments