You can use the following syntax to get the fully qualified URL to a Form for a SharePoint List / Library.
SPList list = SPContext.Current.List;
SPListItem item = list[0];
item.Web.Url + "/" + item.ParentList.Forms[PAGETYPE.PAGE_DISPLAYFORM].Url + "?ID=" + item.ID
PAGETYPE is an enumeration of the SharePoint Forms:
|
PAGE_DEFAULTVIEW
|
Default view. Value=0.
|
|
PAGE_DIALOGVIEW
|
File dialog box view. Value=2.
|
|
PAGE_DISPLAYFORM
|
Display form for list items. Value=4.
|
|
PAGE_DISPLAYFORMDIALOG
|
Display form for a file dialog box. Value=5.
|
|
PAGE_EDITFORM
|
Edit form for list items. Value=6.
|
|
PAGE_EDITFORMDIALOG
|
Edit form for a file dialog box. Value=7.
|
|
PAGE_INVALID
|
Not used. Value= -1.
|
|
PAGE_MAXITEMS
|
Not used. Value=11.
|
|
PAGE_NEWFORM
|
New form for list items. Value=8
|
|
PAGE_NEWFORMDIALOG
|
New form for a file dialog box. Value=9.
|
|
PAGE_NORMALVIEW
|
Normal view. Value=1.
|
|
PAGE_SOLUTIONFORM
|
Solution form. Value=10.
|
|
PAGE_VIEW
|
View, including both default view and normal view. Value=3.
|
Ok, so there are loads of these sort of blogs already out there, but hey thought I’d let you know the suite of tools that I’ve added to my arsenal. All these tools should help make your SharePoint life allot easier… they definitely save me a load of headaches over the years. Thanks to all the community folks for developing these tools, with out them our lives would be a lot harder.
| SharePoint Inspector |
SharePoint Inspector is a free tool to browse your SharePoint 2007 farm.
You can see objects composing its structure, get their properties by reflection, which can be very useful when you want to check if your code does what it should do.
You can use also some advanced features like activate/deactivate SharePoint features, add/remove event receivers, manage your recycle bin. Thanks to Gaetan Bouveret great utility.
|
| CAML.NET IntelliSense |
The purpose of this project is to extend the raw WSS xsd to include annotated documentation taken from the SharePoint SDK so that developers don’t have to break their train of thought while they go searching for information about each element. Thanks to John Holliday for providing this.
|
| U2U CAML Query Builder |
The tool will help you build, test and execute your CAML Queries. This version of the tool only let you build CAML queries for execution against lists. Thanks to those Belgium guys at U2U.
|
| .Net Reflector |
This is something that should be in any .Net developer tool box. .NET Reflector enables you to easily view, navigate, and search through, the class hierarchies of .NET assemblies, even if you don’t have the code for them. With it, you can decompile and analyze .NET assemblies in C#, Visual Basic, and IL.
|
|
BDC Meta Man
|
BDC Meta Man is the first Business Data Catalog tool for all SharePoint Developers and Administrators interested in line of business data integration with SharePoint. Without writing a single line of code you can be viewing and searching across your business data through Microsoft Office SharePoint Server 2007 in minutes.
This is a great tool provided by the guys from Lightening Tools. The free to download version gives you some limited functionality.
Nick Swan and Brett Lonsdale the cofounders of Lightening tools have also produced a great book on the BDC “SharePoint 2007 Developer’s Guide to Business Data Catalog”. They can also be heard on the Excellent SharePoint Pod Show with co-host Rob Foster. Definitely check it out.
|
| WSPBuilder |
A SharePoint Solution Package (WSP) creation tool for WSS 3.0 & MOSS 2007
- No more manually creating the manifest.xml file.
- No more manually specifying the DDF file.
- No more using the makecab.exe application.
Carsten Keutmann you’re a legend… what more can I say!
|
| SharePoint Manager 2007 |
The SharePoint Manager 2007 is a SharePoint object model explorer. It enables you to browse every site on the local farm and view every property. It also enables you to change the properties (at your own risk). This is a very powerful tool for developers that like to know what the SharePoint holds of secrets. Another great tool from Carsten Keutmann.
|
| Fiddler |
Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing data.
|
| AppPool Manager |
Neat little tool from Spencer Harbar. |
| SPSource |
SPSource is a tool for SharePoint developers to assist in the creation of WSS Solution Packages (WSPs) allowing for the use SharePoint Designer and the SharePoint web UI to make quick changes to items, then push those items into Visual Studio for later compilation into a WSP. Thanks to Jeremy Thake.
|
| STSAdm Extensions |
A must have suite of STSAdm commands from Gary Lapointe. Great for those SharePoint Administrators out there. |
| SPTraceView |
SPTraceView analyses in real time the ULS trace messages coming from all MOSS components and can notify you using a balloon-style tray bar messages when something of interest happens.
|
| SP Dispose Checker Tool |
SPDisposeCheck is a tool to help you to check your assemblies that use the SharePoint API so that you can build better code. It provides assistance in correctly disposing of certain SharePoint objects to help you follow published best practice.
|
| SharePoint Installer |
This project is a Windows application for an eased and more user friendly installation and deployment of SharePoint 2007 solution files to a SharePoint server farm. Distribute your SharePoint solution files with this installation program instead of a raw script using STSADM.EXE to install and deploy the solution.
|
| SharePoint Search Service Tool |
The SharePoint Search Service Tool is a rich web service client that allows a developer to explore the scopes and managed properties of a given SharePoint Search SSP, build queries in either Keyword or SQL Syntax, submit those queries and examine the raw web service results. This tool can be useful in troubleshooting and verifying the behaviour and configuration of a SharePoint environment.
|
| CodeRush |
CodeRush for Visual Studio® .NET will help you create sophisticated code blocks in seconds and extend code templates instantly. CodeRush will complete identifiers as you type and expand or contract selections logically. With CodeRush, you will be able to instantly place selected code inside Try/Catch blocks, Regions and your own custom wrappers with ease.
|
| ReSharper |
ReSharper provides solution-wide error highlighting on the fly, instant solutions for found errors, over 30 advanced code refactorings, superior unit testing tools, handy navigation and search features, single-click code formatting and cleanup, automatic code generation and templates, and a lot more productivity features for C#, VB.NET, ASP.NET, XML, and XAML.
|
| SharePoint Skinner |
Helps you define the theme css for your custom SharePoint sites. |
| Visual Round Trip Analyser |
The Visual Round Trip Analyzer tool helps web developers and testers visualize the download of their page, identify best practices and changes that improve web performance. The network Round-Trip between the client and server(s) is the single biggest impact to web page performance – much greater than server response time.
|
| YSlow |
YSlow analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. |
This is a useful reference to determine the scope of your features:
Source: http://msdn.microsoft.com/en-us/library/ms454835.aspx
By default, SharePoint web parts are always put into a web part group called “Miscellaneous”.
All you need to do is locate your Feature Element Manifest XML file and add a Property Element called Group and assign it a value. This is normally the XML file that is in your WebPart Folder.
Nice and easy hey… enjoy 
If you need to get the SharePoint Installation Directory Path then you can use the SPUtility.GetGenericSetupPath method. For instance if you needed to get the path to a features directory to load some XML you could use the following syntax:
string FeaturesPath = SPUtility.GetGenericSetupPath(@”TEMPLATE\FEATURES\” + FeatureName)
The SPUtility Class is full of static methods for assisting you in your SharePoint Development.
Every SharePoint Developer should have SPDisposeCheck Tool in there arsnel! This tool, developed by the guys on the SharePoint Team will intergoate your compiled .dll’s to ensure that you are correctly disposing of SharePoint objects, primarily SPSite and SPWeb. Why do we need to dispose of SharePoint object, well from the horses mouth as such :
“Several of the Windows SharePoint Services objects, primarily the SPSite class and SPWeb class objects, are created as managed objects. However, these objects use unmanaged code and memory to perform the majority of their work. The managed part of the object is much smaller than the unmanaged part. Because the smaller managed part does not put memory pressure on the garbage collector, the garbage collector does not release the object from memory in a timely manner. The object’s use of a large amount of unmanaged memory can cause some of the unusual behaviors described earlier. Calling applications that work with IDisposable objects in Windows SharePoint Services must dispose of the objects when the applications finish using them. You should not rely on the garbage collector to release them from memory automatically.”
Roger Lamb has an excellent blog article - SharePoint 2007 and WSS 3.0 Dispose Patterns by Example
Add SPDisposeCheck to Visual Studio
Visual Studio IDE allows you to add External Tools such as SPDisposeCheck. The follow steps explain how:
1. In Visual Studio select Tools | External Tools
2. Add the following settings:
Title: SPDisposeCheck
Command: C:\Program Files\Microsoft\SharePoint Dispose Check\SPDisposeCheck.exe
Arguements: $(TargetName)$(TargetExt)
Initial Directory: $(TargetDir)
Use Output Window: Checked
SP Dispose Check External Tools
Reference
Introduction to Using Disposable Windows SharePoint Services Objects
