How to use Quickpart in SharePoint 2010

Yes, yes, I know Visual Studio 2010 already provides the Visual Web Parts template, so in version 2010, There is no reason to use tools like Quickpart (although Quickpart still supports features that are not supported by several VS2010 Visual Web Parts templates, such as implementing custom properties and Web Part Connection directly on a user control). However, there are many Web sites that are using Quickpart SharePoint Server 2007, and after you upgrade to the SharePoint 2010 version, you still want quickpart on the page to continue working properly.

If you are putting an. ascx file into the Wpresources folder of each Web application when you use Quickpart, the fact is that Quickpart will continue to work correctly after you upgrade to 2010. Well, if that's true, it's a good way to show your character. Congratulations, you don't have to keep looking down, turn off the window and watch some other fun stuff.

If you're having problems, like you're putting an. ascx file in the 12\template\controltemplates directory (which is actually a recommended practice, Lao Zhao has written a good article about why and how to put an. ascx file into this directory, and it is likely to find that the Quickpart user Control selection box becomes empty. At this point, you can download the 2.0.0 version and its source code from http://quickpart.codeplex.com/releases/view/50664 and install it on the SharePoint 2010 system.

Here are some instructions for this updated version:

1. The 2.0.0 version, which has been amended for a few, is only for SharePoint 2010, and it works only in SharePoint 2010 systems. Do not attempt to install it on a SharePoint 2007 system.

The strong name of the 2, 2.0.0 version of the assembly file (QuickPart.dll) is consistent with the 1.03 version, which helps you upgrade by other means, such as directly updating an assembly in the GAC.

3. The project source code uses the SharePoint project template in Visual Studio 2010.

4. In creating this upgrade, I basically just upgraded the project to VS 2010 and fixed some problems with SharePoint 20,101, so you might find other problems. If the problem is really found, I suggest: (1) Use the source code for debugging; (2) Tell me the question.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/web/sharepoint/