Tag Archives for SharePoint 2007

XSLT Date Function – Comparing Date Values Using XSLT

Written by: Christopher Lincoln Subscribe to this Author's RSS feed

SharePoint Data View Web Parts (DVWPs) can be greatly customized using XSL transformations (XSLT).  One of the great capabilities provided is the ability to render HTML conditionally using XPath expressions.  While XPath can be pretty intuitive, date comparisons might not behave as expected.  For example, performing a test to see if two date values equal […]

Using FileRef in SharePoint 2007 & SharePoint 2010

Written by: admin Subscribe to this Author's RSS feed

When customizing Data View Web Parts (DVWPs) in SharePoint Designer, the field FileRef can be used to get the URL of an item.  While most list items would be displayed by sending the user to a page containing a List Form Web Part in “Display” mode (e.g. DispForm.aspx), it can sometimes be useful to send […]

Using FileRef in SharePoint 2007 & SharePoint 2010

Written by: Christopher Lincoln Subscribe to this Author's RSS feed

When customizing Data View Web Parts (DVWPs) in SharePoint Designer, the field FileRef can be used to get the URL of an item.  While most list items would be displayed by sending the user to a page containing a List Form Web Part in “Display” mode (e.g. DispForm.aspx), it can sometimes be useful to send […]

Get the SharePoint Version Number Using JavaScript

Written by: Christopher Lincoln Subscribe to this Author's RSS feed

If you’ve always wondered how to get SharePoint Version # by JavaScript,  the SharePoint 2010 Client Object Model introduces the SP namespace for JavaScript (i.e. ECMAScript).  Since it is used in SP.core.js, the namespace should exist if SharePoint is functioning properly.  Although SharePoint 2007 uses a similar JavaScript library core.js, it does not include the SP namespace. […]

Jenny’s SharePoint Tip: Rollup items across a site collection by creating a cross list data view web part.

Written by: Ross Beurmann Subscribe to this Author's RSS feed

Applies to:  SharePoint 2007 While working on a client project I had a request to rollup all  calendar items across a single site collection on the home page of the root site.  After reviewing several blogs describing how to create a cross list data view web part (dvwp) I was able to successfully create a […]

Jenny’s SharePoint Tip: How to display “This Month” birthdays in a list using an XSLT filter

Written by: Ross Beurmann Subscribe to this Author's RSS feed

Applies to:  SharePoint 2007 Anyone who has ever worked with SharePoint knows that creating filters on date values is not as straight forward as one would expect.  This example explains how to compile employee birthdays in a custom list that automatically displays only the current month’s birthdays.  With a few calculated columns, a data view, and minor XSLT […]

Using PowerShell to Update Content Editor Web Parts

Written by: Johnny Bouder Subscribe to this Author's RSS feed

Have you ever been in a situation where you needed to programmatically update the content in Content Editor Web Part (CEWP)? Maybe you added some HTML that is breaking your page or maybe you’re moving your content to another domain and you have some hard coded links in your CEWP’s.

Well it turns out that it isn’t really that hard. In my situation we were working with the latter scenario above and within our environment we have many administrators who have created hard coded links within CEWP’s and in order to streamline the upgrade process I thought I would create a PowerShell script…

Upgrading SharePoint 2007 Visual Studio Projects

Written by: Johnny Bouder Subscribe to this Author's RSS feed

This blog post will outline the steps required to upgrade a SharePoint 2007 Visual Studio Project to a SharePoint 2010 Visual Studio Project using the VSeWSS Import Tool for Visual Studio 2010 (http://archive.msdn.microsoft.com/VSeWSSImport). The tool is kind of old at this point, but it is still very useful and I haven’t found a better tool.

This post will be helpful to you if you have created custom SharePoint 2007 solutions using the VSeWSS Visual Studio extensions. The tool above can be used to easily upgrade these projects to SharePoint 2010 projects. This post should be especially useful if you are upgrading existing SharePoint 2007 sites to SharePoint 2010 that already have these Web Parts added and you would like the ability to add additional modifications to these projects.

Installing the VSeWSS Import Tool

The VSeWSS tool is actually provided as a Visual Studio Project, which needs to be compiled in order to build the executable to install the tool into Visual Studio. One other thing to note is that in order to open the solution in Visual Studio 2010, you need to install the Visual Studio 2010 SDK (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=47305cf4-2bea-43c0-91cd-1b853602dcc5&displaylang=en). Why this isn’t included in Visual Studio by default is beyond me. Or why it is not mentioned in the VSeWSS Import Tool installation instruction is also beyond me.

So basically, install the SDK, and then follow the instructions to install the new project type.

Importing Your Projects

To get started you want to copy any old Visual Studio project directories over to computer where you will be writing your Visual Studio 2010 solutions.

Once you have your old projects ready and have everything installed go ahead and fire up Visual Studio 2010. Click New Project and you will now have a new project template called Import VSeVSS Project (if the installation went well). See below:

Screen shot of 'New Project' window, project template Import VSeVSS Project

Upgrading SharePoint 2007 Visual Studio Projects

Written by: admin Subscribe to this Author's RSS feed

This blog post will outline the steps required to upgrade a SharePoint 2007 Visual Studio Project to a SharePoint 2010 Visual Studio Project using the VSeWSS Import Tool for Visual Studio 2010 (http://archive.msdn.microsoft.com/VSeWSSImport). The tool is kind of old at this point, but it is still very useful and I haven’t found a better tool.

This post will be helpful to you if you have created custom SharePoint 2007 solutions using the VSeWSS Visual Studio extensions. The tool above can be used to easily upgrade these projects to SharePoint 2010 projects. This post should be especially useful if you are upgrading existing SharePoint 2007 sites to SharePoint 2010 that already have these Web Parts added and you would like the ability to add additional modifications to these projects.

Installing the VSeWSS Import Tool

The VSeWSS tool is actually provided as a Visual Studio Project, which needs to be compiled in order to build the executable to install the tool into Visual Studio. One other thing to note is that in order to open the solution in Visual Studio 2010, you need to install the Visual Studio 2010 SDK (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=47305cf4-2bea-43c0-91cd-1b853602dcc5&displaylang=en). Why this isn’t included in Visual Studio by default is beyond me. Or why it is not mentioned in the VSeWSS Import Tool installation instruction is also beyond me.

So basically, install the SDK, and then follow the instructions to install the new project type.

Importing Your Projects

To get started you want to copy any old Visual Studio project directories over to computer where you will be writing your Visual Studio 2010 solutions.

Once you have your old projects ready and have everything installed go ahead and fire up Visual Studio 2010. Click New Project and you will now have a new project template called Import VSeVSS Project (if the installation went well). See below:

Screen shot of 'New Project' window, project template Import VSeVSS Project

SharePoint 2007 Workflow Status Codes

Written by: Christopher Lincoln Subscribe to this Author's RSS feed

By default, SharePoint 2007 creates a new column within a List when an attached workflow is started for the first time. The displayed column value is a verbose workflow status (e.g. “In Progress”, “Error Occurred”, etc.). However, if List Items are retrieved from a List View containing such a “workflow column” using the Lists Web Service, the returned values of any workflow columns are not verbose. In fact, they’re the opposite…