Today Microsoft has released the SP2 for Office Products which includes the SharePoint as well, Refer this link (I saw this announcement first ) for more details or refer the SharePoint team blog post Link
Items that attracted my Attention in SP2.
- FBA & Office Integration:…..provide a much smoother user experience and make client integration a viable option for forms-based authentication users…..
- InfoPath form: Performance enhancements in SP2 reduce both the memory requirements and the page load times for large browser-rendered forms
- Browser Support (IE8)
- Pre-Upgrade Check for Microsoft SharePoint 2010 – Big Wow
You should be aware that .Net 4.0 is currently in CTP and I am currently in process of exploring the new features in .Net 4.0. Channel9 have a good series of videos that will help you to get started. This is where I started my journey towards .Net 4.0. I would like to share all the learning I had from the above videos and additions to that I would like to share few items that I noticed during my learning. Altogether you will find information about .Net 4.0, ASP.NET Visual Studio 2010. How well it integrates with SharePoint & more. To practice this you will need a CTP version of Visual Studio 2010 and .Net FX 4.0. You can download it from this location. Also be sure to follow these steps before you open the Visual Studio 2010 because it comes with a hardcoded value of 1 Jan 09 as expire date.
[Update: June 21,2009 : .Net 4.0 and Visual Studio 2010 Beta 1 is now avaliable, please refer to the post for more information.]
This article will host Table of Links for the all Upcoming posts.
- ClientID (this)
- EnableViewStage & ViewStateMode(Refering Dino’s Post)
Visual Studio 2010
One feature that has everyone’s attention when it comes to ASP.NET 4.0 is ClientID. Till now we had the ClientID as the getter and renders the id based on the naming container, from 4.0 we will be able to decide how the client ID is render to the browser. Each of the server control in the ASP.NET 4.0 has three new Properties that decide how the client Id is rendered.
ClientID – ID that we wish to give to the server control when rendered to the browser.
ClientIDMode – Mode that decides how the client ID is generated. Can be anyone of the following value
- Inherit – Gets the mode that is set to the parent.
Predictable – Gives us an option to predict the ClientID that is goingto get rendered. (In the case of data bound control it generates a auto increment number
Legacy – No change works as like the previous version and thisis the default value.
Static – Static value that we set will render as it is.
3. RowClientIDSuffix – Sometimes when we use the Predictable option for ClientIDMode we might need to have a different pattern of the value as the suffix rather than having auto increment. In such a case we can provide a Comma Separated Value of Data Fields (Off course this option is available for the data bound controls) so the client Id will have the value of the Data field appended to the suffix.
Let’s see an Example of the above. I have a User Control (ClientIDUserControl.ascx) with a Label inside that, which is used in the page. You can see my project structure in the screen shot.
ClientIDMode:: Legacy : In the below picture you will see the even though I set the client ID of the Label control it renders client ID based on the naming container, because by default the ClientIDMode is Legacy, I didn’t specified the ClientIDMode attribute so it defaults to Legacy.
ClientIDMode:: Static : In the below picture you will see that both the client ID and ClientIDMode (Static) is set hence the client ID that is rendered to the client is same as the one we set in the Code.
ClientIDMode:: Inherit : In the below picture you will see that client id that was rendered is based on the Naming container because for the Label I set the ClientIDMode as Inherit. Because of this label check its parent (in this case it’s the User Control) for the ClientIDMode and as it doesn’t have one it goes to the Page and checks for the ClientIDMode, as page as well doesn’t have one, it further goes to the web config and check for the ClientIDMode and as it doesn’t have one it by defaults to the Legacy mode. You can also set the ClientIDMode property at the page or the WebApplication level.Refer to the notes section at the end of the article.
ClientIDMode:: Predictable : In the below picture you will see that ClientIDMode is set to Predictable and ClientID is set to “deleteEmployee” and as a result it renders the client id as a AutoIncremented value “DeleteEmployee_0” and soon. When setting the Predictable make sure that Parent control also has the ClientIDMode value set. Refer notes section in the end of the article.
ClientIDMode:Predictable and RowClientIDSuffix:
When using the Predicatble option there is another tweak we can perform that is to generate our own predictable ID rather than using the auto incremented value of (0,1,2 …).In the below picture I have used RowClientIDSuffix to ID and Company, hence the rendered element has the ID in the format DeleteEmployee_[ID]_[Company]
- While using the ClientIDMode=“Predictable” you need to set the ClientIDMode property in the parent control as well else the ClientID generated by the client control will not have the predictable value, it will default to Naming container method of generating the ID. In the above case I have set the ClientIDMode of the GridView to Static and the CheckBox which is the child control to Predictable.
- In addition to the setting the ClientIDMode to the each and every control you can set this value at the Page Level or at the Application level (Web.Config).When there is no explicitly set ClientIDMode to any of the control it will get the value from the page or Web.Config level if one is set else it default to the legacy mode.
|Mode||ID||ClientID||Suffix||Client ID At the Browser|
In all the announcements that we see about upcoming new version of SharePoint seems to use various terms SharePoint vNext, Office 14 so on. But today Microsoft officially named the next version of the SharePoint as Microsoft SharePoint 2010 and it will no longer be having the name MOSS attached to it. The reason behind this name change as per the Microsoft is to have a clear difference between the brand name Office and SharePoint. Most of the time we refer to Office / Microsoft office to the Office client applications.This change will help us to avoid ambiguity between MS Office Application & MS Office SharePoint.
Here are the few highlights of the new version.
• Using Office Web applications, customers will be able to create, edit and collaborate on Office documents through a browser.
• IT professionals will be able to choose to either deploy or manage on-premises or hosted as a service. (Isn’t great ??)
• For developers, we are working on Open APIs, deep support for industry standards and developer tool support with Visual Studio 2010 (Big Wow all in one).
Also we will have the Technology preview of the version somewhere in the Third quarter of 2009 and Release to manufacturing in the first half of 2010.
Have you lately tried to find list of DB’s used by SharePoint. Sure you would have at least one time. I used to go searching the Central Admin – Content DB option and take note of the SSP, Search db etc. Today I landed up here a smart way to do that :).
Trick is to navigate Central Admin -> Operations -> Perform a Backup. All at one place nice Isn’t ?
From April 2, 2009 SharePoint designer is free tool and all the releases down the line will also be free as well. For those you have a SPD licenses already can avail Express Web upgrade.
You can download the free version here Direct Download page.
SPD Landing page.