I have a custom webpart for Sharepoint 2007. I am trying to deploy it to a new Sharepoint web application. I am using WSPBuilder with VS2010 to do the deploy. When I examine the wss\VirtualDirectories\ folder for the web app, the wpcatalog folder does not exist there. When I go to the Web Part Gallery and click "New" button, the web part is no there either. What could be causing this behavior? Are there any other ways to troubleshoot it?
Thanks.
the wpcatalog is actually a document library containing the .webpart definition files. It is stored in the content database, not the file system.
You need to verify the solution is in fact deployed to your web application, and then activate any features if necessary. You can verify the solution deployment under central administration\operations\solution management.
Related
When I add new project to my solution, select SharePoint 2013 App, then choose Autohosted or Provider hosted and create it, the created web project is completely empty and the projects are not set up correctly.
The web project has no TokenHelper, no pages, no jQuery, and no CSOM references.]
How can I fix this?
That happens if you create a new app in this way in a solution subfolder.
Create the project in the 'root' of the solution, and it will work - then you can move it to a folder if necessary.
I am newbie to Sharepoint.
I want to create workflow as template using Sharepoint designer and deploy it as feature.
Following link Workflow Deployment Using Features suggests, this can be achieved in visual studio.
I have following questions
1. Can sharepoint foundation has workflow as template
2. Can we deploy workflow made in designer as feature
If answer to both these is yes, please share some links to get started for these.
You can use Reusable workflow for this.
Assuming you are on SharePoint 2010,
Create a new reusable workflow.
Save it and publish it and test that it works fine
In the ribbon, use Save as Template option to save it.
It will get saved in Site Assets Library as wsp form where you can download it and upload to other sites as wsp and activate the feature to use it there.
More information can be found here:
http://msdn.microsoft.com/en-us/library/ee231580.aspx
I have a Sharepoint 2010 application that consists of Sharepoint application pages and donot contain any web parts. So when I deploy the wsp of the application from the central administration the application will be globally deployed. I want avoid this and deploy the application on to a particular site. How do I accomplish this?
Can you use module for storing Application page and Deploy this solution as Sandbox Solution.
Sandbox solutions are not stored in File System(Physical path) and assemblies can't be deployed to Global Assembly Cache(GAC). But it's available on C:\ProgramData\Microsoft\SharePoint\UCCache at runtime. Note the ProgramData is a hidden folder.
I'm creating a PerformancePoint (henceforth PP) Dashboard that contains a web report to be deployed to the a SharePoint web application that I had created. I followed the instruction in the link below.
Deploy a PerformancePoint dashboard to a SharePoint site
In summary, following the instructions in the link, I published the Dashboard to the PP site. Then, I added my account in PP as Creator in the Application level, Editor in both the Dashboard and the Web Report. In the SharePoint site, I added my account under Contributor. I even added the PerformancePointDefault.master just to be sure.
Now, when I deploy my Dashboard to a Report Library, I was able deploy the folder for the Dashboard, but not the Dashboard Page file.
I googled for this, but I could not find any article helpful.
UPDATE 2009-09-30:
I was able to resolve the issue by creating another site collection. Maybe the first site collection is messed up.
I had the EXACT same problem. I was about to take the best advice I could find and delete my site collection and create a new one from scratch, but by the grace of God, I had one final thought.
In our case, the site created was originally http://ServerName but we later added a host header (i.e. http://BiSite). I had been deploying the dashboard using the host header the entire time, so I decided to try using the original name of the site using the server name and viola, the dashboard finally deployed correctly, pages and all.
When you publish a dashboard in MOSS, you have to make sure that you select Publish a Major Version in the dashboard page's drop-down in the report library.
Why is this a community wiki? Seems like there should be a right answer to this question...
I know that creating a site template from a MOSS publishing site is not currently supported by Microsoft.
Can anyone tell me if creating a basic site, then turning on the publishing feature, then creating a site template is supported - I would guess not as it's probably the same as creating a publishing portal?
You can staple the publishing feature onto your site template.
From KB 986908:
You can create a stapling feature to staple the Office SharePoint Server Publishing feature to specific site templates. For example, see the Feature.xml file in the "Drive:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Features\PublishingStapling" folder. To staple the Office SharePoint Server Publishing feature to all site templates, use the TemplateName="GLOBAL" property. This property staples a particular feature to a site definition if the site definition does not specify the AllowGlobalFeatureAssociations property. (Only the Shared Services Provider site template and the Blank Site site template use the AllowGlobalFeatureAssociations="FALSE" property.)
For example, when you use the TemplateName="GLOBAL" property to staple the Office SharePoint Server Publishing feature, a site that is based on the Team site template uses the system master page that is configured for the root site of the site collection.
you can still access the save template webpage, and save it...
for example http://localhost/website/_layouts/savetmpl.aspx
and it works like a charm :-)
I don't think what you're describing will work (like you said, it's basically the same thing as a Publishing Portal), but there appears to be a workaround. According to this post from the SharePoint Solutions Team (apparently not related to Microsoft), you can create a publishing site, customize it as needed, deactivate the publishing feature, create a site template from it, create a new site based on the template, and then activate the publishing feature on your new site.
It sounds like this works, but is not officially supported by Microsoft. Be careful, since it may mostly work, but I wouldn't be surprised if some small pieces of it break.
We wrote our own tooling to solve the export problem. We can create site columns, content types, master pages, page layouts etc in the Publishing site, and export selected items to a WSP package for deployment to other servers.
The tool SPSource takes a similar approach, but creates a Visual Studio solution for compilation. The result can be packaged with WSPBuilder.