Learning SharePoint Features Using Document Object Model

Posted by Sudhak under SharePoint on 4/3/2009 | Views : 3537 | Status : [Member] | Replies : 2
Anyone please help me how I can learn Sharepoint features using Document Object Model(Programmatical approach of using Sharepoint features in asp.net)
Please help with some good links and articles

Any Help would be appreciated

Thanks and Regards,


Posted by: Bijayani on: 6/28/2010 [Member] Starter

I am sharing a tips on "ASP.Net Validators within Sharepoint "

Most of the times we have requirements of adding different client side validations on the web pages and the easiest way to achieve this in ASP.Net is to use the existing set of validator controls.

In SharePoint when we design custom webparts which takes some data as input, we might need to add some client side validations using ASP.Net validator controls, but there are a few things that always need to be taken care of while using ASP.Net validator controls within SharePoint custom webparts.
1. Within a webpart we might have more than one control triggering server side postbacks. In this case the validator controls will validate with each and every postback, but the actual need might be to only validate the form with a single postback event, let's say through the "SUBMIT" button. To avoid this, one need to set the CausesValidation property to false for all those controls causing server side postabacks where you do not want the form to get validated.

e.g. CausesValidation="false"

2. A SharePoint page can generally contain multiple webparts. So, if we have an ASP.Net validator control integrated within one webpart it's always going to create issues with the postback events from within other webparts present on the same page. To overcome this issue and restrict the validation to a specific webpart, ValidationGroup property can be used with a unique name within a specific webpart. All the controls (validator controls and controls to be validated) coming under a common validation logic should have the same ValidationGroup name.

e.g. ValidationGroup="UniqueGroupName"


Sudhak, if this helps please login to Mark As Answer. | Alert Moderator

Posted by: Vuyiswamb on: 4/3/2009 [Member] [MVP] [Administrator] NotApplicable

Good Afternoon Sudhak

You can get what you want here










Thank you for Posting in .NETFUNDA

Were Looking Forward for your Reply

Vuyiswa Maseko

Thank you for posting at Dotnetfunda

Sudhak, if this helps please login to Mark As Answer. | Alert Moderator

Login to post response