Great SharePoint Adventure – Day 3
For the third day, we covered web parts and lists. I wanted to share some links regarding questions/topics that came up.
Visual Studio 2005 Extentions for WSS/MOSS
If you’re developing against WSS 3.0 (MOSS 2007), be sure to have the Visual Studio 2005 Extensions loaded. You can download them here. The extentions add the following templates into Visual Studio:
Visual Studio 2005 Project Templates
- Web Part
- Team Site Definition
- Blank Site Definition
- List Definition
Visual Studio 2005 Item Templates (items that can be added into an existing project)
- Web Part
- Custom Field
- List Definition (with optional Event Receiver)
- Content Type (with optional Event Receiver)
SharePoint Solution Generator
- This stand-alone program generates a Site Definition project from an existing SharePoint site. The program enables developers to use the browser and Microsoft Office SharePoint Designer to customize the content of their sites before creating code by using Visual Studio.
Reporting in WSS/MOSS
The issue of reporting came up. The biggest angst we have against WSS v2.0/SPS 2003 right now (in our organization) is that you can get data in, but it’s a pain to get it out in a managable, reportable format. One of our class members found that a solution exists for MOSS 2007 in the form of SQL Reporting Services. More information can be found on the SharePoint Team’s blog. The update is part of SQL Server 2005 SP2 that offers “deep integration” with MOSS 2007.
Tip – “Primary Key” or Auto-incrementing keys in WSS/MOSS Lists
One of the most annoying “features” to a list in WSS is that you cannot add an auto-incrementing field—like an identity field, to your list. What I found out is that it’s already there—just not visible by default. To show it, go into your list and add the (obvious) field called “ID”. You can’t edit it, and it won’t show up on the New Item/Edit Item pages, but if you import into Excel or want to see it in a view, it’s there.