Mirjam's blog

Programmatically adjusting the toolbar of a ListViewWebPart

Mirjam — Fri, 24 Jul 2009 15:18:00 +0000

This blog has moved. Click here to open this post on my new blog.

I have been doing more work on programmatically adding lists, views and ListViewWebParts to automatically created sites this week and I’ve stumbled onto another challenge that took me more time than I expected to solve.

I’m creating sites and pogrammaticaly adding ListViewWebParts to the default.aspx page of that site. By default a ListViewWebPart that is added to a page shows the Full Toolbar. This isn’t always what you want. Even worse, it’s usually not what you want.

If you add a ListViewWebPart to a page through the UI you can click Modify Shared Web Part and choose which toolbar type you want to use in the toolpart of the web part:

Full Toolbar
Summary Toolbar
No Toolbar

Unfortunately the object model doesn’t have a property that lets you set the toolbar type. The SPView object does have a ToolbarType property, but this is read-only. I’m of course not the first person to run into this problem and there are a couple of blog posts out there that propose a solution to this problem. Unfortunately most of them don’t work anymore after the infrastructure update. Ton Stegeman wrote a great post where he shares the code that lets you change the toolbar type if you have installed the infrastructure update. (http://www.tonstegeman.com/Blog/Lists/Posts/Post.aspx?List=70640fe5-28d9-464f-b1c9-91e07c8f7e47&ID=90) Ton’s post shows how to set the toolbar type to None (which is the same as selecting No Toolbar” in the UI. In my case the type of toolbar depends on the web part. There are web parts that shouldn’t have a toolbar at all, but there are also web parts that should have a summary toolbar. Of course if there are web parts that need a full toolbar you can just leave them as they are, as they get a full toolbar by default when they are added to the page.

Oh and be aware that taking shortcuts doesn’t really help in this case.

I tried to change the toolbar right when adding the web part, but that didn’t work too well. You should really add the web part first and then loop through the web parts on the page to change them.

Same thing is true for the views. I tried to adjust the view that I use when adding the web part, instead of getting the view from the web part that is already on the page. Doesn’t work either. You need to get the view of the web part by using reflection and adjust that view to get this working. Otherwise you’ll adjust the view of the list.( You can use this on April Fool’s Day…set the toolbar of the views of your list to none. Users will go into the list and won’t be able to see the toolbar and add items, even if they have full control.)

This is the code I used (again, courtesy to Ton, without his post I might still be looking for the solution).

SPLimitedWebPartManager wpManager = newWeb.GetLimitedWebPartManager(“pages/default.aspx”, PersonalizationScope.Shared);

// Get all web parts that are available on the default.aspx page

SPLimitedWebPartCollection webParts = wpManager.WebParts;

// Loop through the collection of all web parts on the page

foreach (System.Web.UI.WebControls.WebParts.WebPart webPartOnPage in webParts)

{

// Only try to set the toolbar type is the web part is a ListViewWebPart, other web part types don’t have toolbars

if (webPartOnPage.GetType().Name == “ListViewWebPart”)

{

ListViewWebPart listViewWebPart = webPartOnPage as ListViewWebPart;

// Get the view used in the web part by using reflection

PropertyInfo viewProp = listViewWebPart.GetType().GetProperty(“View”, BindingFlags.NonPublic | BindingFlags.Instance);

SPView webPartView = viewProp.GetValue(listViewWebPart, null) as SPView;

// This is necessary after the infrastructure update, without it you can’t get to the XML of the view

webPartView.GetType().InvokeMember(“EnsureFullBlownXmlDocument”, BindingFlags.NonPublic | BindingFlags.Instance | BindingFlags.InvokeMethod, null, webPartView, null, System.Globalization.CultureInfo.CurrentCulture);

PropertyInfo nodeProp = webPartView.GetType().GetProperty(“Node”, BindingFlags.NonPublic | BindingFlags.Instance);

XmlNode node = nodeProp.GetValue(webPartView, null) as XmlNode;

// Get the toolbar node from the XML of the view used in the web part

XmlNode toolbarNode = node.SelectSingleNode(“Toolbar”);

// Different action is needed depending on the web part

switch (webPartOnPage.Title)

{

case “Project Announcements”:

if (toolbarNode != null)

{

// Set toolbar type to Summary Toolbar

toolbarNode.Attributes["Type"].Value = “Freeform”;

XmlAttribute positionNode = toolbarNode.OwnerDocument.CreateAttribute(“Position”);

positionNode.Value = “After”;

toolbarNode.Attributes.Append(positionNode);

// Add the CAML

toolbarNode.InnerXml = @” ]]>Add new announcement ]]>”;

webPartView.Update();

}

break;

case “Project Tasks”:

if (toolbarNode != null)

{

// Set toolbar type to No Toolbar

toolbarNode.Attributes["Type"].Value = “None”;

webPartView.Update();

}

break;

case “Calendar”:

if (toolbarNode != null)

{

// Set toolbar type to Summary Toolbar

toolbarNode.Attributes["Type"].Value = “Freeform”;

XmlAttribute positionNode = toolbarNode.OwnerDocument.CreateAttribute(“Position”);

positionNode.Value = “After”;

toolbarNode.Attributes.Append(positionNode);

// Add the CAML

toolbarNode.InnerXml = @” ]]>Add new event ]]>”;

webPartView.Update();

}

break;

}//Switch

}//if ListViewWebPart

}//foreach webpart

Creating a custom view that filters on the current user or [Me]

Mirjam — Thu, 16 Jul 2009 14:29:00 +0000

This blog has moved. Click here to open this post on my new blog.

Earlier this week I was creating custom list views for a customer solution. On of the specifications was that the view needed a filter that only showed the documents that were created by the current user. You can do this using the user interface by specifying that the Created By field needed to be equal to [Me].

I was trying to get this same behaviour by adding a CAML query to my view using the following code:

StringCollection viewFields = new StringCollection();
viewFields.Add("Title");
viewFields.Add("Description");
SPView newView = myDocLib.Views.Add("My documents", viewFields, "[Me]", 100, true, false);

This didn't work, but when I opened the view and saved it again it did work. I tried to search the internet by looking for "sharepoint, spview, [Me]" and I couldn't find a soluton, which is the reason for this post.

Eventually I posted my question on the MSDN forums http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/a4c20e84-4201-4106-9568-df3cfbcd5d3b/ and after only a couple of minutes Dave Hunter came back with the answer. The correct way to define a view that filters based on the current user using the object model is:

Dave also gave the great tip that you can find the CAML for a specific view by doing the following:

Define the view using the user interface
Save the list as a template
Download the template
Rename the .stp file to .cab
Extract the manifest.xml from the .cab file and find the definition

Thanks again Dave!

Site Column Definition Schema

Mirjam — Tue, 30 Jun 2009 10:49:00 +0000

This blog has moved. Click here to open this post on my new blog.

While working on a customer project I had to create a lot of site columns, based on the columns created by a business analyst through the user interface.

As I was creating the site columns through a feature I was trying to find the Site Column Definition Schema on MSDN. And I found it. It can be found here http://msdn.microsoft.com/en-us/library/ms459922.aspx. Too bad it 's not a complete overview. That might have something to do with the disclaimer at the top of the page though:

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Maybe there is a full reference somewhere on Technet or MSDN and I just couldn't find it, but this wasn't much help to me.

Luckily I was able to use the great post Brian LaSitis did that has a nice overview of all properties of all column types in it.

[Update]

Wouter van Vught just tipped me that you shouldn't always use StaticName and SourceID. This info is coming from this blog post by Robert Bogue.

He says:

" Version, StaticName, and SourceID aren't attributes that should typically be set. Version isn't supported at all, StaticName is only for the office clients, and SourceId is supposed to be set by the framework to the feature that created the field. SourceId is supposed to help you work back to the feature that created the fields. Well, as it turns out if you set this field to be the same as the sourceId for the fields that you added in via the UI, SharePoint doesn't mangle the document template. (So leave the sourceId in — for this case only). "

My colleague Maarten gave me a tip to go and look at this page that contains information about the Field Element. Some of this information can be used to help determine how site columns should be described.

[Update2]

Found out that this post by Brian LaSitis doesn't contain all possible options. I'm adding a few extra options that I needed myself here. If you know of more options that aren't mentioned in the Brian's blog let me know by leaving a comment with the option and the field type.

Choice Field

Name="Project"

StaticName="Project"

DisplayName="Project"

Description=""

Group="My Columns"

Type="Choice"

SourceID="http://schemas.microsoft.com/sharepoint/v3/fields"

Format="[Dropdown/RadioButtons]"

FillInChoice="FALSE">

Project A

Project B

DateTime Field

Name="DueDate"

StaticName="DueDate"

DisplayName="Due Date"

Description=""

Group="My Columns"

Type="DateTime"

Format="[DateTime/DateOnly]"

SourceID="http://schemas.microsoft.com/sharepoint/v3/fields"/>

Note Field

Name="Comments"

StaticName="Comments"

DisplayName="Comments"

Description=""

Group="My Columns"

Type="Note"

NumLines="6"

AppendOnly="TRUE"

RichText="TRUE"

RichTextMode="[Compatible/FullHtml]"

SourceID="http://schemas.microsoft.com/sharepoint/v3/fields"/>

User Profiles and User Information List Synchronization

Mirjam — Wed, 17 Jun 2009 09:44:00 +0000

This blog has moved. Click here to open this post on my new blog.

Lately I have been getting a lot of questions about where user data is stored and how it is synchronized within SharePoint 2007. This inspired me to write this blog post about User Profiles and the User Information List or UserInfo table. I will also do a future post on what happens when a user profile is deleted from MOSS 2007.

User Profiles

The user profile store in MOSS 2007 contains information about users. User profiles can be created by importing users from a user account directory, or they can be created manually. In most environments Active Directory will be used as the source for creating user profiles. In the MOSS 2007 Shared Service Provider an LDAP import query can be configured that will create user profiles for accounts that are returned from Active Directory by the LDAP query. The user profile imports can be scheduled to run on a regular basis and they can be either incremental or full.

Once a user profile is created additional information about the user can be added to the user profile properties by the user itself, an administrator, a Business Data Catalog data source or an LDAP directory.

By default data from user profiles is shown in the People Search results, on the My Site and in the User Information list of MOSS and WSS sites.

User Information List

All MOSS 2007 and WSS 3.0 sites have a user information list. The information in the user information list is stored in the UserInfo table in the content database of the site. A user gets added to the user information list when he or she has accesses the site for the first time. In the user information list a user's email address, login name and name are stored. MOSS will make sure that user profile property information for those fields for users that are added to the user information list is sent to the user

information list. The image below shows an overview of the user profile architecture in MOSS 2007.

Synchronizing user profile data to the user information list

Keeping the information in the user information lists up to data is a task that is handled by the Profile Synchronization and the Quick Profile Synchronization timer jobs. By default the first job runs once every hour, the second one runs every couple of minutes and is incremental. The first time user data is replicated from the user profile to the user information list of a site a full update is needed. So the Profile Synchronization job needs to run in order to get the data replicated to the site and this may take up to an hour. If information about a user is already stored in the user information list and the information changes in the user profile it will be synchronized with the data in the site collection by the Quick Profile Synchronization job.

You can also kick off the profile synchronization jobs by running the stsadm sync command.

stsadm -o sync

If you believe that information is not synced between the user profiles and the user information lists in one or more sites you can request a list of content databases that have not been synchronized for x number of days by using the following stsadm sync command.

stsadm -o sync -listolddatabases

If one or more content databases show up in this list you can clean up the sync list so they can be added to the list again.

stsadm -o sync -deleteolddatabases

You can also use the sync command to change the schedule for the synchronization job.

For more information on the stsadm sync command have a look here http://technet.microsoft.com/en-us/library/cc263196.aspx.

Nintex context menu problem solved

Mirjam — Wed, 10 Jun 2009 08:57:00 +0000

This blog has moved. Click here to open this post on my new blog.

On our development environment at one of our customers we had a very weird problem with Nintex.

For one of my colleagues Nintex worked perfectly
If I logged on to the server with my own account I could create or manage a workflow, but if I added a new Workflow Action the context menu of that action wouldn't work. I couldn't configure or move the action.
If I tried changing a Workflow Action that was added to a workflow by my colleague the context menu worked fine.
If I logged onto the SharePoint environment using my colleagues account the context menu on new actions still didn't work.
If I logged onto the server using my colleagues account configuring actions worked without a problem.

Knowing all this I knew it had to be something on the server itself and not something in the SharePoint environment.

So I checked all permissions on the server, Internet Options in Internet Explorer, compatibility view settings (it's IE8), whether the site was in the Intranet Zone for both accounts..

After checking all that I still had the same problem.

Today we added another development server to the same environment, connected to the same SharePoint environment. I browsed to the site on the new server and when adding a Nintex action I got the IE security popup asking me whether I wanted to add about:blank to my trusted sites. I did that and everything worked perfectly.

Moral of this story: if you are using Nintex workflows and the IE Enhanced Security Configuration (ESC) settings are turned on you need to add about:blank to your Trusted Sites.

My Microsoft Certified Master experience

Mirjam — Wed, 08 Apr 2009 15:43:00 +0000

This blog has moved. Click here to open this post on my new blog.

Since a lot of people are interested in the Microsoft Certified Master (MCM) experience I'm going to try and write a blog about it. Note that this will just be a post on how I experienced the program. I can't elaborate on the actual content of the training, although I will blog on specific topics later on.

It was great, very intense, so usefull, terrific, brutal, fantastic, fascinating, informative, overwhelming…

Ok, so it's very difficult to describe. I will give it a try.

The group of students consisted of 16 SharePoint experts. All people that have a lot of experience in doing SharePoint implementations. Lots of them are also trainers and speakers. It's amazing to spend 3 weeks in a room with a group like that. We've had a lot of great and very valuable discussions, since people do different types of projects and have come up with different best practices. We were all there to learn and everybody was more than willing to share their knowledge and experience. I really want to thank everybody for the great three weeks!

Working with the instructors was also very special. All of them are the best in the field on the area that they covered. They are not just trainers, but people that actually work with the product and have an amazing depth on the subject that they covered. It was a priviledge to be able to learn from their experience and to be able to bounce thoughts and ideas off of them.

The training was conducted on the Microsoft Campus in Redmond. For me it was the first time that I was on campus and that really brought something extra to the experience. Being there also meant that it was possible for product team members to drop in when we were discussing a certain subject to elaborate even more, sometimes on the current version and sometimes on how things will change in vNext. Very valuable!

As I said before I can't say much about the actual content of the training, but I can say that it's very broad and very deep. It reaches from information architecture, capacity planning, infrastructure, SQL, a lot of SharePoint services (like Search, BDC etc), development and troubleshooting. All this material was covered in three weeks of training. That's a lot to cover in three weeks, which means that it's long days of instruction supplemented with hands on labs in the evening. It means that you eat, drink and breath SharePoint for three weeks. This is a stretch, but it's a great way to hugely expand your knowledge in a relatively short amount of time.

Of course your knowledge will also be tested. There are three written exams and one hands on qualification lab. These exams also take place during the three weeks. This means that the master program is not for the lazy and not for the faint hearted.

At the moment I know that I passed the three written exams. The results for the qualification lab are not in yet. Personally I'm sceptical about me passing that one. But it really doesn't matter. I'm very proud that I was part of the R2 (beta) MCM SharePoint group. And I'm very proud to have passed at least three of the exams. If I haven't passed the qualification lab I will be able to retake it in a Microsoft office around here, so I don't need to travel to Redmond for that.

[Update: I took the retake of the qualification lab and I passed! I'm now officially and MCM SharePoint!]

Even though this was a beta the program was very well organized. Off course there were a couple of small glitches along the way, but the whole experience is already pretty well polished. I personally think that we've got the acting program manager to thank for that. He did an amazing job in managing content and logistics and watching out over all the candidates. He was terrific. Thank you.

All in all the experience was great, I'm still exhausted, but I wouldn't have want to miss it for anything in the world!

Some links to MCM related content:

Microsoft Certified Master: Microsoft Office SharePoint Server 2007

Blogpost by Russ Houberg, MCM R2 attendee

Blogpost by Spence Harbar, MCM R2 attendee (posted pre-R2)

Blogpost by Andrew Connel, MCM instructor

Blogpost by Todd Baginski, MCM instructor

Displaying your InfoPath Forms in a Web Part

Mirjam — Tue, 10 Mar 2009 09:18:00 +0000

This blog has moved. Click here to open this post on my new blog.

So here I am again with another "did you know". This one is also inspired by Inside Microsoft Office SharePoint Server 2007.
Did you know that you can display browser enabled InfoPath forms in a web part?

If you create a form that is published to the SharePoint Form Services in the Central Administration and you have selected that users can open the form in their browsers, you can display the form in a web part. This means that the form page will get a SharePoint look and feel, instead of an InfoPath look and feel.

It is easy to configure and you don't need a single line of code.

The web part that is able to show the form is already created for you by Microsoft and is part of the Microsoft.Office.InfoPath.Server.dll assembly. This assembly is stored in the C:Program FilesMicrosoft Office Servers12.0Bin folder.

The first step you have to take to enable the web part to show you InfoPath page is to add a SafeControl entry to the web.config of the web application where you want to use the web part.
The SafeControl entry should look like this:

Now go to your browser and open the Web Part Gallery from the Site Settings page of your SharePoint environment. Click on the New button and you will get a list of available web parts. Look for the entry Microsoft.Office.InfoPath.Server.Controls.XmlFormView and check the checkbox in front of it. Next click the Populate Gallery button at the top of the page. The web part should now be available for use in the site collection.

You can check this by going to a web part page within your site collection and click Edit Page from the site actions menu. In the page click on the Add a Web Part link of a web part section. Now choose the XmlFormView web part that can be found under the Miscellaneous section. An error is generated because you still need to set some properties for the web part. You can simply close the error and go to the properties of the web part to set them.

Go to the Features section at the bottom of the properties list. Expand the section and decide whether you want to display the header and the footer of the form. Since the form is displayed in the middle of the page you probably don't! If you want users to be able to fill in the form in the web part you want to set the EditingStatus to Editing. In the DataBinding section you find the XsnLocation, the XmlLocation and the possible path to the container where you want to save the form to.

If you are displaying a blank form you want to have the XsnLocation pointing to the location where the .xsn file of you form is published to.
If you are displaying an existing form you can have the XmlLocation point to the location of that form.

If you have filled in these properties correctly your web part should now be displaying you form!

Use Stemming for MOSS 2007 Search

Mirjam — Tue, 10 Mar 2009 09:14:00 +0000

This blog has moved. Click here to open this post on my new blog.

While I was reading Inside Microsoft Office SharePoint Server 2007 as a to prepare for the Master Program, I came across something interesting again.

In the Search Core Results Web Part you can enable stemming. If you are a non-English reader you probably wonder what stemming is, as I did when I read about it. Stemming is a method of mapping a linguistic stem to all matching words to increase the number of relevant results. This means that if searching for buy, you will also find results that contain bought, buying and buys. For Dutch readers: het betekent dus dat je ook vervoegingen vindt van woorden waar je op zoekt.

Very handy!

Stemming is disabled by default, but can be enabled in the properties of the Search Core Results Web Part.

You can also use stemming if you are using the Query class from the Microsoft.Office.Server.Search.dll assembly. The query class has a property EnableStemming that you can use to turn stemming on or off. Note that the query class also has a property Culture that is very relevant when using Stemming, so the query engine knows in what language it has to look for stem matches of the search term.

Slides van DIWUG presentaties van dinsdag 17 februari

Mirjam — Thu, 19 Feb 2009 12:15:00 +0000

This blog has moved. Click here to open this post on my new blog.

Dinsdagavond (17 februari) was de eerste DIWUG avond van dit jaar. Ondanks de late uitnodiging was de opkomst erg goed, er waren meer dan 50 bezoekers!
De avond werd gehost bij en gesponsord door Sparked.
We hadden weer twee presentaties:

Serge van den Oever van Macaw hield een presentatie over Business Productivity Online Suite. Zijn slides staan hier, en Serge heeft zelf ook een blogpost over de presentatie geschreven met links naar andere interessante resources.
Clemens Reijnen van Sogeti presenteerde over Collaboration in the Cloud. Zijn slides zijn hier te vinden.

Ik wil hiervandaan graag Sparked bedanken voor de goed georganiseerde avond en de sprekers bedanken voor hun inbreng. Daarnaast natuurlijk iedereen die er was bedankt voor de komst!
We hopen op korte termijn uitsluitsel te kunnen geven over de data en de onderwerpen van de volgende DIWUG avond.

Tot die tijd is iedereen natuurlijk van harte welkom bij de SDE van maart op 30 maart in Driebergen. Meer informatie over de komende SDE kun je hier vinden.

Loading UserControls in SharePoint web parts

Mirjam — Wed, 11 Feb 2009 16:30:00 +0000

This blog has moved. Click here to open this post on my new blog.

If you want to use UserControls in SharePoint web parts you can use SmartPart (http://www.codeplex.com/smartpart). But you can also build a web part that load a UserControl yourself.

If you want to do it yourself you start out by opening Visual Studio (whether you use 2005 or 2008 doesn't matter). Next you create a new project of the type "ASP.NET Web Application".

Then you can add a new class to the project and you make sure that it inherits from System.Web.UI.WebControls.WebParts.WebPart.

Now create an new folder in the project that you call "Usercontrols" and add a Web User Control to it.

Make sure that you adjust the Inheritance of your .ascx file to a fully qualified name.

Let's go back to the class you created initially and add the user control to it. You add the user control in the CreateChildControls function.

You can see that the function UserControlVirtualPath is called. This function is used to determine where the user control will be located. Reason for this is that the deployment location of the user control changes when you change the location where the assembly is deployed to.

If you deploy the assembly to the GAC the user control will be stored in the C:Program FilesCommon FilesMicrosoft Sharedweb server extensionswpresources folder and will have the fully qualified name used to create sub folders. The user control for my project will be stored in C:Program FilesCommon FilesMicrosoft Sharedweb server extensionswpresourcesTwitterTimelineWebPart1.0.0.0__c038812e8af423a0TwitterPublicTimelineUserControls if I deploy the assembly to the GAC.

If I were to deploy the assembly to the bin of the web application the user control is deployed to the C:InetpubwwwrootwssVirtualDirectoriesmoss2007devwpresources folder.

The UserControlVirtualPath function finds the location of the user control for you.

You can add all the content you like to the user control now. Nothing special about that.

One thing that we need to take care of that is SharePoint specific is the deployment.

I will do it manually, so everyone can copy this.

You start out be creating a .ddf file that will help you create the package. The .ddf file can be stored in the root folder of your project. I will call the file SolutionPackage.ddf. More information about creating the ddf file can be found here (http://msdn.microsoft.com/en-us/library/bb466225.aspx).

Next you need to create the manifest.xml file that will make sure that all files are deployed correctly. Create a folder "DeploymentFiles" and create a file that you call manifest.xml in it.

In the manifest you will have to create an Assemblies element with a child Assembly element in which you will specify the assembly you want to deploy. The property DeploymentTarget indicates whether the assembly will be deployed to the GAC or to the web application bin. If you want to deploy the assembly to the GAC the DeploymentTarget property needs to be GlobalAssemblyCache. If you would like to deploy to the bin of the web application you would use WebApplication.

The ClassResources element is a child element of the assembly element and will have a child element ClassResource. You will need to fill in the location of the resource file (the .ascx file) in the package in the FileName property. The Location property is used to indicate the folder that the resource file will be deployed to. In this case we will create a sub folder TwitterPublicTimeline with a sub folder

UserControls to store the user control in.

The Assembly element has another child element called SafeControls. The child element SafeControl is used to create the safecontrol entries in the web.config. You will need to add the information about your assembly in the Assembly, Namespace and TypeName properties. The Safe property should be set to True..that was the whole point right?

A great reference that describes the schema of the manifest file is located here (http://msdn.microsoft.com/en-us/library/ms442108.aspx).

After creating the ddf and the manifest files you start a command prompt and go to the folder where your ddf file is stored. You can then type "makecab /f SolutionPackage.ddf".

This will create the wsp package and include the files mentioned in the ddf file, including the manifest file.

If you want to check whether all files are actually in the package you copy the .wsp file and rename it to a .cab file. Then you extract it and check whether all files are in there.

Now you are ready to upload you .wsp file to your SharePoint environment. You can use the stsadm addsolution command for that.

After that you can go your Central Administration and deploy the solution to your web application. The Solution Management page can be found on the Operations page under the Global Configuration heading.

Click on the solution name and on the Deploy Solution link. Now select the web application you want to deploy the web part to and the time at which you want the deployment to run.

Your web part is now deployed. You will only need to add it to the web part gallery of your site collection be browsing to the site settings page of your site collection and select Web Parts under Galleries. Click New and select the dll of your web part. Scroll back to the top of the page and click the "Populate Gallery" button.

Congratulations! You can now add your web part to a web part page!