Kirk Evans is a Microsoft Architect for the Azure Center of Excellence.
Introduction to SharePoint and Azure IaaS
Building SharePoint Apps with Windows Azure Platform as a Service
SharePoint Solutions and Architectures on Windows Azure Infrastructure Services
Understanding Authentication and Permissions with Apps for SharePoint and Office
I was working on a project for a customer today and needed to build a custom field control. Visual Studio 2010 does not have a template for creating a field control. I thought about crafting one by hand, but then I remembered that Visual Studio Extensions for Windows SharePoint Services 1.3 has a project item for creating a field control. At first I thought I would just copy the items over into a new Visual Studio 2010 project, but I decided to try out the VSeWSS Import Tool for Visual Studio 2010.
To get started, you need to build and install the tool.
The output from the steps above is a file called VSeWSSUpgradeTool/Src/VSeWSSUpgradeTool.Installer/VSeWSSUpgradeTool.Installer.vsix. When you double-click on this file, it will install an extension into Visual Studio 2010.
Once the tool is built and installed, Visual Studio 2010 will have a new project template called “Import VSeWSS Project”.
Click OK, and a new dialog asks for more information such as the SharePoint site that is used for debugging, and whether you would like a sandboxed solution or a full trust solution. Finally, it asks for the full path to the existing VSeWSS project.
Click Finish, and Visual Studio will churn for a minute as it converts the project to Visual Studio 2010.
One thing to note if you are importing field controls built with VSeWSS. The XML file that is generated (in the screen shot above, fldtypes_FieldControl1.xml) has a value for the FieldTypeClass that is a GUID when you import it. The correct value is a 5-part assembly name. If you deploy and get an error that the field is not installed correctly, make sure to check that you replace the GUID with the 5-part name. For instance:
<?xml version="1.0" encoding="utf-8"?>
<Field Name="FieldTypeClass">Empty2.TimeCodeField, AnnotationsProjectDemo,
Version=18.104.22.168, Culture=neutral, PublicKeyToken=af55ed7e9eb0419d</Field>
Make sure to not have a line break in the 5-part assembly name, I did that only for readability in the code sample above.