Checking Out SharePoint Templates/Tools in Visual Studio 2010 Beta 1

By -
For months now, ever since seeing some glimpses of the integrated SharePoint functionality in VS2010 I've been salivating at the prospect of a cohesive SharePoint development experience that it promises.

Check it out here on Channel 9.

Although the really interesting stuff is going to come with the release of the VS 2010 Tools for SharePoint, I was very excited to see what SharePoint surprises were tucked inside of the Visual Studio 2010 Beta that was released this week on MSDN.



When first choosing a SharePoint project template, nothing is available. This is because the default framework version selected is 4.0.



Switching to version 3.5 yields the SharePoint 2007 Sequential and State Machine Workflow templates.



Ultimately, attempting to create either of these projects failed. The folders were created in the file system, but there were no project, solution or workflow files to be seen.

I'm looking forward to the beta 2 / RC!

Comments

Post a Comment

Popular posts from this blog

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just
Read more

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu
Read more