The State of Web Content Management in 2013
Check out my latest blog post as a guest writer for the BlueMetal Architects blog. The State of Web Content Management in 2013
Check out my latest blog post as a guest writer for the BlueMetal Architects blog. The State of Web Content Management in 2013
I was recently tasked with migrating code that was written for 2007 in a feature. The files that were originally provisioned in the feature we deployed to the root folder of the feature. The code had already been upgraded to SharePoint 2010. I needed to create a wsp using Visual Studio 2010 and package it as a feature. Out of the box when you create a new Module in VS 2010 you get a subfolder so for example you create the feature called Feature1 and a module called Mod1. The default deployment path is 14\templates\features\feature1\mod1\file.txt. What I needed was feature1\mod1\file.txt. I tried modifying all the attributes in the elements.xml file and was not able to get the files to the correct location.
In the end what i did was the following
I have a mental block on this query string parameter. If you need to add a webpart on the newform.aspx page ToolPaneView=2 to the query string for the page. This will put the page in edit mode.
The deck for my SharePoint Saturday New Hampshire has been posted to SlideShare. Thanks to everyone who came to my session.
I wish I could say that I was smart enough to have figured this one out for myself but I can’t. I was working on my first custom branded SharePoint 2010 site and the search screen was all messed up. The navigation was displaying doubled. It turns out that the search center out of the box used minimal.master. This uses the placeholders that are in v4.master in different way so the search box ends up in the breadcrumb pull down. At any rate, Randy Drisgill wrote a great and very easy to follow post about how to modify your custom masterpage to the search center. It took me longer to create the feature to deploy the new search masterpage than it did to make the modifications.
A client of ours wanted to use the preview pane for a list view. The default view of the preview pane has the right hand pane blank. You need to select an item or hover an item from the left pane to populate the right pane. The client wanted the right hand pane to have the right hand pane default to first item in the list.
$("document").ready(function () { $('div.ms-ppleft table tr td.ms-vb-title').first().trigger('onfocus'); //click(); })As a SharePoint 2007 developer I have many of the common stsadm commands committed to memory. While stsadm still works in SharePoint 2010 in favor of moving to proficiency in the latest version of the technology here are some of the powershell commands that I use on a daily basis. With that said, I usually create a batch file that runs these commands so that I only need to run one command to get the features updated and features activated.
Add Solution
Add-SPSolution c:\solutions\myproject.wsp
Deploy Solution
Install-SPSolution –Identity myproject.wsp –WebApplication http://myprojectsite -GACDeployment
Note: You can also use the following parameters
Upgrade Solution
Update-SPSolution –Identity myproject.wsp –LiteralPath c:\solutions\myproject.wsp –GACDeployment
Retract Solution
Uninstall-SPSolution –Identity myproject.wsp –WebApplication http://myprojectsite
Remove Solution
Remove-SPSolution –Identity myproject.wsp
Activate Feature
Enable-SPFeature –Identity MyFeature –url http://myprojectsite
Deactivate Feature
Disable-SPFeature –Identity MyFeature –url http://myprojectsite