The id will look something like this
ctl00_m_g_6e363f12_79be_43ef_a4e9_3967baee41bd_ctl00_ctl04_ctl12_ctl00_ctl00_ctl04_ctl00_ctl00_DateTimeField_DateTimeFieldDate

so your code is gonna be this way
document.aspnetForm. ctl00_m_g_6e363f12_79be_43ef_a4e9_3967baee41bd_ctl00_ctl04_ctl12_ctl00_ctl00_ctl04_ctl00_ctl00_DateTimeField_DateTimeFieldDate.disabled=”True”;
or
document.aspnetForm. ctl00_m_g_6e363f12_79be_43ef_a4e9_3967baee41bd_ctl00_ctl04_ctl12_ctl00_ctl00_ctl04_ctl00_ctl00_DateTimeField_DateTimeFieldDate.disabled=true;

Open up the page in sharepoint designer and find for the code below

and then add the javascript given above and it will work.

Tweet This Post Digg This Post Reddit Stumble This Post

Just add this piece of code in you page where you want to set the value .

Add this code in your aspx page below

so that way it ll set you the default value.
Cheer up

Tweet This Post Digg This Post Reddit Stumble This Post

Sometimes we have a scenario like we have a dropdown box and the data-items coming for this dropdown has to come from a SQL Server database or some other database.

Or we have some business validations to put on the controls present in NewForm.aspx page or Editform.aspx page i.e. in List Forms.

So to tackle these kind of situations we need to customize our List forms.

We can customize the List-forms in two ways.
Customize the List form through XSLT
Change the Listforms with custom webpart which is having all your business requirements and a mechanism to add or edit items in List. This custom webpart we can build in Visual Studio through Sharepoint Object Model.
In this article I will tell you how to change the newform.aspx or editform.aspx with custom webpart.

Here I believe that you all know how to build custom webpart for Sharepoint 2007.

When we are click New button to add a new item

We are getting NewForm.aspx page. Now to change the list forms with some other webpart we need to edit the page in the same way which we are doing for a normal web part page but the problem here is we do not have Edit Page option under Site Action tab. Now what to do? How to open edit page mode?

The answer is very simple and little bit tricky also.

The URL for newform.aspx page will be like this:

http://spdevserver:1003/Lists/Products/NewForm.aspx

just add ?&Toolpaneview=2 above URL. Now your URL becomes like this.

http://spdevserver:1003/Lists/Products/NewForm.aspx?&Toolpaneview=2

Now click on Go button in Internet Explorer and you will see the NewForm.aspx page like this:

Just close this webpart and add your new custom webpart here.

So after that whenever you will click on new button for adding a new item you will see your custom webpart instead of default Newform.aspx page.

In the same way we can change editform.aspx page with our custom webpart by adding the ?&Toolpaneview=2 to the url.

Hope this article would be a help to you.

Tweet This Post Digg This Post Reddit Stumble This Post

The toolkit can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en

Tweet This Post Digg This Post Reddit Stumble This Post

I’m sure some of you have seen this error in your SharePoint travels, but this is something that in my opinion needs to be addressed.

The WSS “Save Conflict” error is a common error that occurs when you make multiple changes to a list under the same SPWeb object without disposal. This is a pretty hairy error to catch, but it’s clear sign that you’re not being modular enough with your design. General when I see this error the first thing I think is, “It’s time to break my methods out a little better and to call my SPWeb Object when I really need it.”

One example of where this can come into play is in solutions where SPListItem field swaping is required (i.e ListItem1 swaps it’s Title field with ListItem2). For every update to a list item the SPList’s “update()” method needs to be called to save the changes. The pattern I like to follow is to retrieve the SPWeb GUID from the current site, then call a separate instance of an SPWeb object per individual list update. This is a tedious pattern and doesn’t necessarily have to be used on all occasions, but it will save you from this annoying little exception.

Here’s an example of a small method that updates a SPListItem’s fields using this pattern:

protected void itemUpdate(string FieldName, string FieldValue, SPSite site, Guid webID, Guid listID, Guid itemID)
{
try
{
using (SPWeb web = site.OpenWeb(webID))
{
web.AllowUnsafeUpdates = true;
SPList list = web.Lists[listID];
SPListItem item = list.Items[itemID];

item[FieldName] = FieldValue;
item.Update();
list.Update();

web.AllowUnsafeUpdates = false;

}
}
catch(Exception ex)
{
Response.Write(“An error occured while updating the items”);
}
}

Keep in mind, when disposing of an SPWeb object you must remember CONTEXT. If you retrieve an SPWeb object from the current context (SPContext.Current.Web), you cannot and should not dispose of this. If you dispose of the Web being used by the current context, it’s the equivalent of ripping the ground from under your feet!! If you’re doing multiple list updates the best approach would be to open and dispose of a separate instance of an SPWeb object. This will save you tons of headache in the future.

If you ever see this exception, hopefully you’ll no exactly how to handle it now and grab it by the horns!

~:)

Tweet This Post Digg This Post Reddit Stumble This Post

We have been working on a new flavor of IIS 7.x that is optimized for developer scenarios that we are calling “IIS Express”. We think it combines the ease of use of the ASP.NET Web Server with the full power of IIS. Specifically:

It’s lightweight and easy to install (less than 10Mb download and a super quick install)
It does not require an administrator account to run/debug applications from Visual Studio
It enables a full web-server feature set – including SSL, URL Rewrite, Media Support, and all other IIS 7.x modules
It supports and enables the same extensibility model and web.config file settings that IIS 7.x support
It can be installed side-by-side with the full IIS web server as well as the ASP.NET Development Server (they do not conflict at all)
It works on Windows XP and higher operating systems – giving you a full IIS 7.x developer feature-set on all OS platforms
IIS Express (like the ASP.NET Development Server) can be quickly launched to run a site from a directory on disk. It does not require any registration/configuration steps. This makes it really easy to launch and run for development scenarios.

VS 2010 Integration

We are enabling IIS Express so that it can be easily used with Visual Studio 2010. You’ll be able to configure VS 2010 to use it instead of the ASP.NET Web Server as the default web-server on ASP.NET Projects. Like the ASP.NET Development Server today, you won’t need to register a site or virtual directory to use IIS Express. It will support the same usage-model as the ASP.NET Development Server today – just with more feature support.

When you press F5 to run an ASP.NET project, Visual Studio can automatically launch IIS Express and use it to run/debug the application (no extra configuration required). Like the ASP.NET Web Server, IIS Express will show up in your task-bar tray when running:

Full Story At Source

Tweet This Post Digg This Post Reddit Stumble This Post

Tweet This Post Digg This Post Reddit Stumble This Post

If a site is using forms based authentication, then client integration is turned off by default. You can enable it by going to: CA –> Application Management –> Authenticaiton Providers –> Edit Authentication.

Scroll all the way down.

Tweet This Post Digg This Post Reddit Stumble This Post

However, you can turn off the publishing features of a publishing site by going to Site Actions –> Site Settings –> Modify All Site Settings –> Site Administration –> Site Features. Click the Deactivate button for Office Sharepoint Server Publishing.

Now when you go back to the site settings, you will have the option to save the site as a template. When you do so, simply turn the publishing features back on. Also you can turn the publishing feature on on your your new sites after they are created.

You will need to turn on the publishing feature after you create the site if needed. This is a much better alternative to having to create a Team Site just so you can create a template.

Tweet This Post Digg This Post Reddit Stumble This Post

The solution is to change a single entry in web.config, by modifying the line

SafeMode MaxControls=“200“ CallStack=“false“
to…
SafeMode MaxControls=“200“ CallStack=“true“

You will also need to set custom errors to ‘Off’ .

You will no longer see the “An unexpected error has occurred” error page and instead you get a lovely ’standard ASP.Net error page’ with the stack trace and everything…development has got that little bit easier!!

A better on will be a customizing the web.config file located C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG and to modify the trust to trust=”Full” so that the web app is immediately ready to accept development DLLs in the ‘bin’ folder.

Tweet This Post Digg This Post Reddit Stumble This Post