Beth Massi has a lot of SharePoint 2010 Videos For You

Thanks to Rob Windsor for posting this to Twitter and Beth Massi for including all this amazing video content regarding SharePoint 2010 and how to do tonnes of things with it.

http://blogs.msdn.com/b/bethmassi/archive/2010/06/16/visual-studio-bizapps-launch-content-rollup.aspx

If you have any tips, tricks or resources you would like to share with the guild please email them to Susan Fischer at susan@clinchportal.com and we will post them here.

Moss 2007 not supported by Visual Studio 2010?

I ran into an odd error with Visual Studio 2010 and SharePoint and when I did some searching I kept finding the same comments.

"To the best of my knowledge, Visual Studio 2010 targets SharePoint 2010 exclusively in every respect, except for SharePoint 2007 workflow solutions. I doubt that you can connect to a SharePoint 2007 server using Visual Studio 2010."

Is this true? If so I am quite shocked. There are a lot of people still on Moss 2007 or older Sharepoint. I guess this means we run multiple versions of Visual Studio or hold our customers off upgrading to Sharepoint 2010 for yet another reason.

I look forward to hearing comments on this and hopefully a way I can use the robust Visual Studio 2010 to develop for older Sharepoint.

Free tool from Metalogix to import blogs into SharePoint 2010

I thought I would pass this on to the guild. This tool would allow you to import content from blogs like this one into SharePoint 2010. Thus allowing you to continue to have all your content in one location.

http://www.metalogix.net/Company/News/ByYear/2010/Metalogix-Announces-New-Solution-to-Migrate-Blogs-to-SharePoint-2010---Free-to-Microsoft-MVPs/

If you have any tips, tricks, tools, and resources you would like to share please email them to Susan Fischer at susan@clinchportal.com and we will post them here.

WebPart Parameter Binding to a static value

It took me a while to find this out myself so I thought I would post it here. Sometimes you want to use a webpart and bind the parameters to a static value rather than to the querystring.

I had to use this for the sites in category web part since I had to place two on the same page with different filtervalues for the same field. The way to do this is to find the filtervalue parameter binding entry and add an extra property called "DefaultValue" set this to the proper value and voila.


I hope this saves you some time when you are trying to perform the same task.

If you have any tips, tricks, resources you would like to share with the group please post them as comments or email them to Susan Fischer at susan@clinchportal.com and we will post them in an article.

Problem publishing Workflow to WSS 3.0 From Visual Studio 2008

I ran into a problem publishing then after some googling came across this article on how to fix it.
I thought I would provide the info here and a link to the original article.
Hope you find this helpful.

http://blogs.msdn.com/kaevans/archive/2008/08/08/creating-sharepoint-workflows-for-wss-with-visual-studio-2008.aspx

Creating SharePoint Workflows for WSS with Visual Studio 2008

I just ran across one of those nuisance things with Visual Studio 2008
that I haven't seen before. Create a SharePoint workflow (Sequential or
State, doesn't matter) for a WSS site (not MOSS). Build the project,
you'll get an error similar to the following:
Error
3 Feature '739f61bf-5616-427a-80d6-ed30fdc04b1f' could not be
installed because the loading of event receiver assembly
"Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" failed: System.IO.FileNotFoundException: Could
not load file or assembly 'Microsoft.Office.Workflow.Feature, Version=12.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies.
The system cannot find the file specified.
Turns out that VS2008 is only
supported on MOSS. Tucked away in the comments in Nikhil's blog, he shows how
to use Visual Studio 2008 to create workflows for Windows SharePoint Services
3.0.
To get it to work on WSS there is a workaround. Remove the reference
to Microsoft.Office.Workflow.Tasks from project assembly references. This
assembly is only available in the MOSS version of SharePoint and will not be
resolved on a machine with WSS installed.
Also, open the feature.xml in the
project and remove the ReceiverAssembly="Microsoft.Office.Workflow.Feature,
Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" and
ReceiverClass="Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver". This
feature receiver is required for MOSS related functionality (InfoPath forms) and
should not affect your WSS workflow development.

If you have any tips, tricks, resources or articles you think would be useful to the group please email them to susan@clinchportal.com and we will post them or you can simply post them as comments.

Installing Sharepoint 2010 on Vista

I am going to attempt an install of Sharepoint 2010 on Vista tonight. They are telling me its possible so I am going to test it out.

If you have any tips or tricks to doing it let me know. I will keep you posted on what issues I run into.

PROBLEM:You must have Internet Information Services installed in order to use the SharePoint Products and Technologies Configuration Wizard.
SOLUTION: Under Turn On Windows Features, navigate to IIS. Under Web Management Tools make sure IIS 6 Compatibility is turned on.

Please leave me comments on this post if you run into issues or have solutions to issues other are having. You can also email them to Susan Fischer at susan@clinchportal.com

Microsoft.SharePoint.SPException: Save Conflict

Microsoft.SharePoint.SPException: Save Conflict Microsoft.SharePoint.SPException: Save ConflictYour changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes.

If you get this error you will want to read this article on the solution:
http://www.theartofsharepoint.com/2007/05/microsoftsharepointspexception-save.html

Hopefully Microsoft fixes this issue in 2010. You shouldn't have to re-get the web pointer and list pointer and tell the list you want to allowunsafeupdates for every item you want to update.

If you have any tips, tricks or links to articles you would like shared with the guild please email them to susan@clinchportal.com or post them as a comment.