Approaches:

Site Url :http://servername/site1/dummysite

List Name : Project Tasks

DataSheet View : test.aspx

List View : Allitems.aspx

list GUID: 5166419E-2DB1-4EA4-8911-FC12ADE6D57A

datasheet View GUID: 13217A3C-60A8-4FA9-9662-7BBD1EB19FC8

 Display Document Library Page

http://url/_vti_bin/owssvr.dll?dialogview=FileOpen&location=shared%20documents

Filter On Document Library

http://URL/_vti_bin/owssvr.dll?dialogview=FileOpen&location=Requirement%20Document&FilterField1=ID&FilterValue1=1

 XML data file of Datasheet View

http://URL/_vti_bin/owssvr.dll?CS=65001&XMLDATA=1&RowLimit=0&List={5166419E-2DB1-4EA4-8911-FC12ADE6D57A}&View={13217A3C-60A8-4FA9-9662-7BBD1EB19FC8}

  XML data file of Filtered List Allitem.aspx

http://URL/_vti_bin/owssvr.dll?Cmd=Display&List={5166419E-2DB1-4EA4-8911-FC12ADE6D57A}&XMLDATA=TRUE&FilterField1=Status&FilterValue1=Completed

 XML with Filtered data of DataSheet view

http://URL/_vti_bin/owssvr.dll?Cmd=Display&List={5166419E-2DB1-4EA4-8911-FC12ADE6D57A}&View={13217A3C-60A8-4FA9-9662-7BBD1EB19FC8}&XMLDATA=TRUE&FilterField1=Status&FilterValue1=Completed

 Error:

http://URL/_vti_bin/owssvr.dll?Using=Lists%2FProject%20%20Tasks%2FAllItems.aspx&FilterField1=Status&FilterValue1=Completed

 Filter on Allitem.aspx but gives error for Dharasheet view

http://URL/Lists/Project%20%20Tasks/AllItems.aspx?FilterField1=Status&FilterValue1=Completed

 Using RenderView method

http://URL/_vti_bin/owssvr.dll?Cmd=RenderView&List={5166419E-2DB1-4EA4-8911-FC12ADE6D57A}&View={13217A3C-60A8-4FA9-9662-7BBD1EB19FC8}&URLBase=http://URL/Lists/Requirement%20Document/test.aspx

Gives Error:

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and then click the

Only one top level element is allowed in an XML document. Error processing resource ‘http://URL/…

/ist/css/PMO/NPS/NPSs/Lists/Project%20%20Tasks/DispForm.aspx?ID=23" ONCLICK="GoToLink(this);return false;&…

  References :

Important Urls

http://blog.pathtosharepoint.com/2008/09/24/using-the-rpc-method-via-the-url-protocol/

First experiment

In the address box of your browser, replace the library URL with this:

http://ThisServer/sites/ThisSite/_vti_bin/owssvr.dll?dialogview=FileOpen&location=shared%20documents

The browser will display the list of documents in your “Shared documents” library. You won’t be able to do much with this, but this is an easy way to show owssvr.dll at work.

http://flylib.com/books/en/3.464.1.107/1/

http://msdn.microsoft.com/en-us/library/dd588673(v=office.11).aspx

If you get error denied while activating this feature, you have not activated the dependent feature called “PublishingResources”.

Fix:

Activate the “PublishingResources” feature using stsadm command

stsadm -o activatefeature -name PublishingResources -url

http://YOUR_WEBSITE

if Wed application not found error then use Computer (Server Name) name instead of IP address
(change the URL)

Now, Activate the Office SharePoint Server Publishing Infrastructure feature.

• Troubleshoot versioning, Recycle Bins, and backups and restores (Office SharePoint Server 2007)
• Capture and restore content by using the Web site delete event (Office SharePoint Server 2007)
• Archive and retrieve content by using Stsadm import and export operations (Office SharePoint Server 2007)
• Archive site versions by using database snapshots (Office SharePoint Server 2007)
• Back up and restore an item by using DPM (Office SharePoint Server)

Catastrophic Recovery (Farm, Server, and Database Restores)

• Office SharePoint Server 2007 Data Protection and Recovery model
• Data protection and recovery for Office SharePoint Server
• Move content databases (Office SharePoint Server 2007)
• Move all databases (Office SharePoint Server 2007)
• Add, split, and merge content databases (Office SharePoint Server 2007)

• Back up and restore Web applications by using built-in tools (Office SharePoint Server 2007)
• Back up and restore databases (Office SharePoint Server)
• Back up and restore an entire farm (Office SharePoint Server 2007)
• Back up a farm by using built-in tools (Office SharePoint Server 2007)
• Restore a farm by using built-in tools (Office SharePoint Server 2007)
• Back up a farm by using SQL Server tools (Office SharePoint Server 2007)
• Restore a farm by using SQL Server tools (Office SharePoint Server 2007)

• Back up and restore a site by using DPM (Office SharePoint Server)
• Database sizing Backup/Restore Implications (Blog Post)

High Availability (Clustering, Logshipping, Mirroring, Hardware Replication)

• TechNet: Plan for availability (Office SharePoint Server) New!
• TechNet: Planning High Availability Visio Model New!
• Database Mirroring vs. Logshipping (Mike Watson)
• Logshipping Options with SQL 2000/2005 (Bill Baer)
• Teched 2008 Orlando Disaster Recovery Options (Mike Watson)
• Database Mirroring with SharePoint Whitepaper (TechNet) Updated Recently!
• SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 – Part 1 (Introduction, Overview, and basics) (Bill Baer)
• SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 – Part 2 (Configuration) (Bill Baer)
• SQL Server 2005 Database Mirroring and Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 – Part 3 (Failover) (Bill Baer)
• Cluster or mirror? (Bill Baer)
• Words of Caution on SQL Mirroring (Joel Oleson)

• SharePoint 2010 Overview and Demos

Developer SharePoint 2010 MSDN Resources:

• MSDN Library – SharePoint 2010
• SharePoint 2010 Developer Center
• SharePoint 2010 MSDN Forums

IT Pro SharePoint 2010 TechNet Resources

• SharePoint 2010 TechNet Tech Center
• SharePoint 2010 TechNet Forums
• SharePoint 2010 Content Posters

1. Custom Web parts (including resource files) are contained within a SharePoint Feature and are packaged as a SharePoint solution in order to be deployed.
2. The configuration of Web parts that are being deployed gives the administrator the flexibility of deploying to the Web application level or lower.
3. You use the SharePoint Web part infrastructure’s standardized set of connection interfaces for Web parts to exchange information with each other at run time.
4. Source code for third party Web parts solutions, whenever possible, is provided with adequate documentation to ensure good technical support.
5. All custom Web parts utilize the SharePoint architecture to ensure consistent behaviour across the application for functionality such as single sign-on, feature deployment, and so on.
6. Assemblies have a strong name. (Dynamically generated ASP.NET Web page assemblies cannot currently have a strong name.)
7. You use delay signing as a way to protect and restrict the private key that is used in the strong name and signing process.
8. Assemblies include declarative security attributes (with SecurityAction.RequestMinimum) to specify minimum permission requirements.
9. Highly privileged assemblies are separated from lower privileged assemblies.
10. If an assembly is to be used in a partial-trust environment (for example, it is called from a partial-trust Web application), then privileged code is in a separate assembly.
11. You rely on a native configuration file to support the application instead of changing the configuration to the Web.config.
12. You use .NET Framework 2.0, 3.0, or 3.5.
13. You use a single .NET Framework version. You do not mix multiple versions.
14. Your code is 64 bit compatible.

Best Practices For General SharePoint Software Development:

10.  Your application does not try to directly access any SharePoint databases. Data stores in SharePoint databases are only updated by using the SharePoint object model.

11.  You avoid hard coding strings and labels. You use resources or language files instead.

12.  When referencing the SPWeb or SPSite objects, you employ a using statement or, alternatively, you use an explicit call of the .Dispose method to ensure proper use and disposing of the memory objects.

13.  You use caching as appropriate to reduce unnecessary round trips. For Web parts, you expose the cache expiration (duration) as a Web part property.

14.  When packaging your solution, you include a Code Access Security policy for the solution and, if necessary, include your assembly in the Safe Controls list though the solution.

15.  When logging code, you use the Portal Log class to log the SharePoint Unified Logging Service (ULS) logs.

16.  If you need to update multiple list items by using remote code, you use the Web service to update list items. You only use SPListItem.Update() if you have to update more than one item at a time by using local OM-based code.

17.  When using the Count property of a SPListItemCollection, you only call it once and then store it in a variable that you can refer to when looping. You do not call it inside a loop.

18.  The solution uses the AppSettings object to implement XML mapping. (This can be provided by using the settings persistence framework in .NET 2.0, 3.0, or 3.5.) The solution avoids creating custom XML files and a strongly typed object for XML mapping.

19.  Installation and deployment logging are provided in the event logs to enable appropriate operational troubleshooting during installation and uninstallation.

There are now two different Web Part styles in Windows SharePoint Services 3.0. Both are supported, but the ASP.NET 2.0 Web Part is the recommended style for your new projects.
SharePoint-based Web Parts — The older style Web Parts have a dependency on Microsoft.SharePoint.dll and must inherit from the WebPart base class in the Microsoft.SharePoint.WebPartPages namespace. These Web Parts can only be used in SharePoint Web sites. Yet in Windows SharePoint Services 3.0, the Microsoft.SharePoint.dll was changed so that Web Parts written in the older style would be compatible with the Windows SharePoint Services 3.0 runtime.
ASP.NET 2.0 Web Parts — These Web Parts are built on top of the ASP.NET Web Part infrastructure. The newer ASP.NET-style Web Parts have a dependency on System.Web.dll and must inherit from a different base class named WebPart in the System.Web.UI.WebControls.WebParts namespace. These Web Parts can be used in Windows SharePoint Services applications whether Windows SharePoint Services is involved or not, making them highly reusable. If you are creating your Web Part specifically for a SharePoint site, and it will consume the Windows SharePoint Services object model, you can derive from the ASP.NET System.Web.UI.WebControls.WebParts.WebPart base class and add a reference to the SharePoint object model in your project.

The Windows SharePoint Services 3.0 Web Part infrastructure is built on top of a control named SPWebPartManager that is derived from the ASP.NET 2.0 WebPartManager control. The SPWebPartManager control overrides the standard behavior of the WebPartManager control to persist Web Part data inside the Windows SharePoint Services content database instead of in the ASP.NET services database. In most cases, you don not have to worry about dealing directly with the SPWebPartManager control because the one and only required instance is already defined in default.master. When you create a content page that links to default.master, the SPWebPartManager control is already there.

When you create a Web Part Page for a standard ASP.NET 2.0 application, you need to add logic that interacts with the WebPartManager control to manage the Web Part display mode, and generally you also need to explicitly add editor parts and catalog parts to the page along with the HTML layout to accommodate them. Fortunately, you do not have to perform these changes when creating content pages for a Windows SharePoint Services 3.0 site. Instead, you inherit from the WebPartPage class that is defined inside the Microsoft.SharePoint.WebPartPages namespace and it does all the work behind the scenes for you.

Custom Web Parts provide developers with a method to create user interface elements that support both customization and personalization. The term customization implies that changes are seen by all site members. Individual users can further personalize Web Part Pages by adding, reconfiguring, and removing Web Parts. The term personalization implies that these changes will be seen only by the user that made them.

The steps to create a simple Web Part that prints “Hello World!” to the screen.

1. In Visual Studio, create a new class library

2. Add a reference to System.Web.

3. Create a class that inherits from the WebPart class in System.Web.UI.WebControls.WebParts.

4. In order to control the rendering of the Web Part one overrides the Render method. An HtmlTextWriter instance is passed into the Render method and can then be used to write markup to the page output.

using System;

using System.Collections.Generic;

using System.Text;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

namespace ExampleWebPartLibrary

{

public class MyWebPart : WebPart

{

protected override void Render(HtmlTextWriter writer)

{

writer.Write(“Hello World!”);

}

}

}

5. OPTIONAL Add the code statements using System.Security; and [assembly: AllowPartiallyTrustedCallers] to our AssemblyInfo.cs file.

6. Specify proper Assembly Name and Namespace properties for the class library project by opening the project property page

7. OPTIONAL Specify the Signing parameters in the project property page

8. Build the assembly frequent

9. Copy the newly created assembly from bin\Release or bin\Debug folder and paste it in the bin directory of the sharepoint web application OR In our class library properties, set the build output path to the bin directory of our SharePoint development web application.

10. OPTIONAL copy the assembly into C:\Windows\Assembly (GAC), REight click select properies to find its public key

11. In the web.config file of the sharepoint web application, add the assembly as a safe control.

<SafeControl

Assembly=”ExampleWebPartLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=db485f68ad2dc0c5″

Namespace=”ExampleWebPartLibrary”

TypeName=”*” Safe=”True” AllowRemoteDesigner=”True” />

12. We can now add the web part library to your SharePoint site. To do this, log in as an administrator and go to the settings page. Click on “Web Part Gallery” under the “Galleries” section. Click “New” and we should see our web part in a list. Select our web part and click “populate gallery”.

13. We can give your web part a friendly title and control its permissions using the edit button in the web part gallery. I have chosen to call the Web Part “My Web Part”.

14. Finally we can add the web part to a web part page and we should see the web part’s hard coded “Hello World!” message.

Adding ASP.NET controls in our web part

1. Repeat the steps 1-3 of first example.

2. Controls should be declared as member variables and then initialised and configured within an override of the CreateChildControls method. I usually create a separate method to setup each control and then invoke that method from CreateChildControls. It is important to add the created controls to the list of Web Part controls. If a control is not added to this list then it’s events won’t be raised on post back.

private Button btnDemo;

private void createBtnDemo()

{

btnDemo = new Button();

btnDemo.Text = “Click me”;

btnDemo.Click += new EventHandler(btnDemo_Click);

// This line of code is required to trigger the click eventControls.Add(btnDemo);

}

protected override void CreateChildControls()

{

base.CreateChildControls();

createBtnDemo();

createLblHelloWorld();

}

3. The controls are rendered inside the Render method override. This method can be used to layout the web part it’s controls. The HtmlTextWriter has many useful methods to help out, including WriteBreak() which writes a “<br />”.

protected override void Render(HtmlTextWriter writer)

{

writer.WriteBreak();

lblHelloWorld.RenderControl(writer);

writer.WriteBreak();

writer.WriteBreak();

btnDemo.RenderControl(writer);

}

4. Perform the steps from 5 (of first example) to deploy the web part

Accessing SharePoint data in our web part

1. Repeat the steps 1-3 of first example.

2. Reference Microsoft.SharePoint.dll by browsing to the directory “[Program Files]\Common Files\Microsoft Shared\web server extensions\12\ISAPI”.

3. To take care of the code access security for our web part by setting the target SharePoint site’s trust level to “Full”. This level of trust is generally acceptable in an Intranet environment. Find the following in our site’s web.config file:

<trust level=”WSS_Minimal” originUrl=”" />

change this to:

<trust level=”Full” originUrl=”" />

4. Write some code to access SharePoint data. Here I show a simple web part that displays the name of the presently logged in user:

using System.Web.UI.WebControls.WebParts;

using Microsoft.SharePoint;

namespace ExampleWebPartLibrary

{

public class HelloUser : WebPart

{

protected override void Render(System.Web.UI.HtmlTextWriter writer)

{

// Get a contextual reference to the current SPWeb

SPWeb currentWeb = SPContext.Current.Web;

// Write a message to the current user

writer.Write(“Hello ” + currentWeb.CurrentUser.LoginName);

}

}

}

Note : SPContext.Current.Web is the starting point for accessing SharePoint data. For example we can use it to access data in lists and document libraries.

5. Perform the steps from 5 (of first example) to deploy the web part

• bin directory — The bin directory is a folder stored in your Web application root directory. For most installations, this is located in the %SYSTEMDRIVE%\inetpub\wwwroot\wss\VirtualDirectories\<port number>\bin directory.
• Global Assembly Cache (GAC) — The GAC enables you to share assemblies across numerous applications. Components are typically installed in the %SYSTEMDRIVE%\WINDOWS\Assembly directory.

Note that the recommended practice is to deploy assemblies to the bin directory.

Windows SharePoint Services provides a SafeControls list to prevent users from arbitrarily adding server-side code within ASPX pages. The SafeControls list is a list of approved controls and Web Parts that are specific to the SharePoint site that we have designated as safe for invocation on any ASPX page within our site. This list is contained in the web.config file in your Web application root. The local path contains the physical location of the web.config file.

Web Parts are designed to be distributed over the Internet or an intranet. For security reasons, when we create a custom Web Part, we should give it a strong name to ensure that the Web Part can be trusted by our users.

By default, the trust level for a server will be WSS_Minimal, which does not allow access to the Windows SharePoint Services object model. In order to perform such actions, we must perform one of the following three actions:

• Create a custom policy file for your assembly,
• Install your assembly in the GAC global assembly cache
• Increase the trust level for the entire virtual server. Eg: increase the default trust from WSS_Minimal to WSS_Medium in the web.config file.

Today we have a Project KickStart call with one of our  prospective clients.

I just tried to compile a list of questions to ask during the call.

Let me share it with you.  This could be helpful

1. Active Directory Exists in the infrastructure: Yes / No
2. SharePoint version (WSS or MOSS ent/std) and its licensing
3. Presence of dependant products and envirornments like .Net framework and SQL Server
4. Presence of other softwares in the infrastructure
5. SharePoint Environment Exists : Yes / No
6. If yes,
   1. Purpose of the SharePoint Environment
   2. Number of servers
   3. Purpose of each servers
   4. Current User Base
   5. Are users in same domain
   6. Are users in same geographical location
   7. Current amount of data
   8. Current data growth
   9. Current performance load

10. Authentication Mode (Forms / Windows)

11. Security options present (SSL)

12. Is SharePoint Integrating with any other tool/products

13. Current issues (if any)?

1. About the Proposed SharePoint Environment
   1. Purpose of the SharePoint Environment
   2. Number of servers
   3. Purpose of each servers
   4. Current User Base
   5. Are users in same domain
   6. Are users in same geographical location
   7. Current amount of data
   8. Expected data growth
   9. Current performance load

10. Authentication Mode (Forms / Windows)

11. Security requirements (SSL)

12. Integration requirements Siebel/SAP/Peoplesoft/CRM/Lotus Notes, etc. Live Communicator Server

13. Other Specific requirements (if any)?

1. Regarding the user work stations
   1. Operating System
   2. Web Browser
   3. Office Tools version
2. SharePoint Features anticipating from the proposed solution 
   1. Portal
   2. Collaboration
   3. Search
   4. Business Intelligence
   5. Business forms
   6. Content Management

10. Plans regarding a separate QAQC environment

11. Plans regarding a separate Development environment

12. Disaster Recovery strategy

1. Backup strategy
2. Test Restore strategy
3. Tools (builtin / 3^rd party)

13. Anti virus related

1. Current antivirus
2. Vendor

14. Governance

1. Authentication and Authorization
2. Administrators and Site Owners
3. Users Groups and permissions
4. Information security Policies

15. Information organization related

1. Site structur

16. Customization related

1. Branding requirements
2. Content types 

17. Personalization requirements

18. development related

1. Require Custom web parts : Yes/No
2. Require Custom work flows : Yes/No
3. Require Custom site definitions / templates : Yes/No
4. Require Custom work flows : Yes/No
5. Development and deployment strategy
6. Access to development environment

Follow these steps to customize the files in the Layouts folder

1. Create a Layouts_Backup folder to contain a backup of the originally installed files and folders. For example,

             create a Layouts_Backup folder in the following location:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\

12\Template\Layouts\Layouts_Backup

1. Copy the originally installed files and folders from the Layouts folder to the Layouts_Backup folder that you created in step 1.

            For example, copy the originally installed files and folders from the following folder to the Layouts_Backup folder:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Layouts

1. In the Layouts folder, customize the .aspx files and the Application.Master file as needed.

This method will change the layouts directory for any site collection within the Web application that is being modified. To apply custom layouts changes to an individual site collection, the site collection should reside in its own Web application.

1. Create a custom LayoutsSiteCollection folder to contain a copy of the originally installed files and folders. For example, create a LayoutsSiteCollection folder in the following location:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Layouts\LayoutsSiteCollection

1. Copy the originally installed files and folders from the Layouts folder to the LayoutsSiteCollection folder that you created in step 1. For example, copy the originally installed files and folders from the following folder to the LayoutsSiteCollection folder:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Layouts

1. Start Internet Information Services (IIS) Manager. To do this, click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In IIS Manager, follow these steps:
   1. Expand the Web site that is hosting the site collection.
   2. Right-click _layouts, and then click Properties.
   3. Click the Virtual Directory tab.
   4. Click Browse, change the path from the Layouts folder to the LayoutsSiteCollection folder, and then click OK two times.
3. In the LayoutsSiteCollection folder, customize the .aspx files and the Application.Master file as needed.
4. Repeat these steps for each site collection that you have to customize.

This method enables the customization of application pages for individual site collections.

• unless you intend to use your WebPart on SharePoint 2003 site inherit your WebPart class from System.Web.UI.WebControls.WebParts.WebPart
• Deploy WebPart dll to bin folder instead of GAC [full trust] if possible
• Remember to add [assembly: AllowPartiallyTrustedCallers()] to allow the strong named assembly to run from the bin
• Remember to change trust level in web.config from “WSS_Minimal” to “WSS_Medium” or create your own policy if your WebPart uses Object Model

If you are creating a Web Part, custom Web service, or Web application to work

with site collections, individual sites, or lists, you can use members of

the Microsoft.SharePoint.SPContext class to obtain the current site collection, Web site, or list.

When you create a Web application in the /_layouts virtual directory,

its functionality becomes available to all sites on the Web server.

Outside of an HTTP context, such as in a console application or a

Windows application, use a constructor of the SPSite class to obtain a specific site collection and to reach various objects within the collection.
]]> http://nikhilshankarsingh.wordpress.com/2009/12/11/sharepoint-tips-and-tricks/feed/ 0 nikhil http://nikhilshankarsingh.wordpress.com/2009/12/11/developing-event-handlers/ http://nikhilshankarsingh.wordpress.com/2009/12/11/developing-event-handlers/#comments Fri, 11 Dec 2009 12:00:21 +0000 nikhil http://nikhilshankarsingh.wordpress.com/?p=64 ]]> Event Handlers specify a server-side code routine that is called when registered events occur within the SharePoint environment. Custom event handlers can be attached to and have a scope of Web application, site collection, Web site, list, or document library. This .Net assembly contains the additional business logic you need to run when the event occurs in SharePoint.

There are two events raised for each type of event Eg: ItemAdded and ItemAdding. The “…ing” event occurs before the action starts and the “…ed” occurs after the actions ends. “…ing” events occur synchronously while the “…ed” events occur asynchronously.

Synchronous events:

• Occur before the event. 
• Block the flow of code execution until your event handler completes.
• Provide you with the ability to cancel the events resulting in no after event (“…ed”) being fired.

Asynchronous events:

• Occur after the event.
• Do not block the flow of code execution in SharePoint.

Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 event handlers can be installed through feature event receivers by having the feature event receiver add a reference to the event callback routine in the applicable event handler collection.