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.

Interesting Article on using sharepoint webcontrols properly

I came across this article and found it extremely useful. It eliminated many lines of code
by using this simple method of rendering the proper control for a field.

http://www.hezser.de/blog/archive/2007/04/29/how-to-use-the-sharepoint-web-controls.aspx

If you have any tips, tricks, or resources you would like to share with the group either comment on a posting or email Susan Fischer at susan@clinchportal.com and we will post them.

Code blocks are not allowed in this file.

I got this error then came across this article to fix it. Sharepoint turns off code blocks by default.

This link explains the whole story:
http://blogs.msdn.com/kaevans/archive/2007/04/26/code-blocks-are-not-allowed-in-this-file-using-server-side-code-with-sharepoint.aspx

The fix is to add this web.config key. In the configuration/SharePoint/PageParserPaths configuration section add something like this:

VirtualPath="/pages/test.aspx" CompilationMode="Always"
AllowServerSideScript="true" />

WARNING: There is a reason why Sharepoint does this so only use it when you need it. It can be dangerous to give designers access to the file and accidentally have them edit your code.

Setting up Sharepoint for Silverlight web parts

When trying to install Silverlight on Sharepoint 2007 or wss 3.0 its not an easy task.
The first step is following the web.config tweeks in this article.

http://www.telerik.com/help/aspnet-ajax/moss-install-aspnet-ajax-35.html

The second step is copying the System.web.silverlight.dll into either the bin folder for the site or registering it with the GAC.

The third step is making sure the scriptmanager is loaded properly. Here is an article that will help you place it in the right spot.

http://blogs.prexens.com/Lists/Posts/Post.aspx?List=7a299699%2Df8da%2D4559%2D920c%2Dbda481608691&ID=3

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