Get SSP URL

 Use the following Chunk 2 get the SSP URL. This uses reflection mechanism.

 private string getSSPURL()

{

     string uri = string.Empty;

     ServerContext sc = ServerContext.Default;

     object ssp = sc.GetType().GetProperty("SharedResourceProvider",BindingFlags.Instance | BindingFlags.NonPublic).GetValue(sc, null);

     Guid sspGuid = (Guid)ssp.GetType().GetProperty("AdministrationSiteId").GetValue(ssp, null);

     using (SPSite sspSite = new SPSite(sspGuid))

     {

       uri = sspSite.WebApplication.GetResponseUri(SPUrlZone.Default).AbsoluteUri + "ssp/admin";

     }

     return uri;

  }

Kerberos - Pros & Cons

Pros:

1. Faster performance is experienced when using Kerberos as it caches information about the client after authentication. This means that it can perform better than NTLM particularly in large farm environments
2. Delegation - Kerberos can delegate the client credentials from the SharePoint front-end web server to other back-end servers like Oracle. So you are eliminating double hops. (Login Challenges)
3. You can also with MOSS 2007 utilize RSS feeds "Within your SharePoint Environment" 
4. Microsoft recommends to "Use Kerberos authentication for sites with a high security service level agreement."
5. Federated Search between Farms (e.g., will work based as the user credentials are passed automatically.)
6. Planning on utilizing BDC some LOB Applications will require Kerberos authentication.
7. SQL Serer Reporting Services integration works well with Kerberos.
8. Switch back to NTLM is possible.

 

Cons:

1. In Active Directory, SPN should be configured carefully .If not troubleshooting is difficult

 

Related Links:

http://technet.microsoft.com/en-us/library/cc288475.aspx

http://ablog.apress.com/?p=1127

http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/de88fb8c-0101-4413-9855-34501569e077

http://blogs.msdn.com/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx

 

Compiling audience object model.

Refer the community content by me at

http://msdn.microsoft.com/en-us/library/microsoft.office.server.audience.audiencemanager.aspx

MSDN Note "Compiling audiences is not supported in the object model."

Actually we can compile the audience.
Following code to compile all the audiences.
Add Reference Microsoft Search Component(Microsoft.Office.Server.Search.dll)
using Microsoft.Office.Server.Search.Administration;

using (SPSite site = new SPSite(txtSite.Text))
{
ServerContext context = ServerContext.GetContext(site);
SearchContext searchContext = SearchContext.GetContext(context);
string[] args = new string[3];
args[0] = searchContext.Name;
args[1] = "1"; //"1" = start job, "0" = stop job
args[2] = "1"; //"1" = full compilation, "0" = incremental compilation (optional, default = 0)
AudienceJob.RunAudienceJob(args);
System.Threading.Thread.Sleep(3000);
}

To Compile a specific audience, add the optional arg[3] after making the String array size to 4 and specify the Audience Name.

The lifecycle events of a Sharepoint Connectable WebPart wih a single ViewState backed property;

On Page Load

1. Constructor
   
2. OnInit
   
3. OnLoad
   
4. ConnectionConsumer method is called if web part is connectable (sets the connection providers interface in the webpart)
   
5. CreateChildControls
   
6. OnPreRender (if your web part is connectable you would typically call the connection provider here to retrieve data)
   
7. SaveViewState
   
8. Render
   
9. RenderChildren
   
10. RenderContents
    

On 1st Postback

(PostBack click handler sets ViewState via public Property)

1. Constructor
   
2. OnInit
   
3. CreateChildControls
   
4. OnLoad
   
5. PostBack click handling
   
6. ConnectionConsumer method is called if web part is connectable (sets the connection providers interface in the webpart)
   
7. OnPreRender (if your web part is connectable you would typically call the connection provider here to retrieve data)
   
8. SaveViewState
   
9. Render
   
10. RenderChildren
    
11. RenderContents
    

On 2nd Postback

(PostBack click handler sets ViewState via public Property)

1. Constructor
   
2. OnInit
   
3. LoadViewState
   
4. CreateChildControls
   
5. OnLoad
   
6. PostBack click handling
   
7. ConnectionConsumer method is called if web part is connectable (sets the connection providers interface in the webpart)
   
8. OnPreRender (if your web part is connectable you would typically call the connection provider here to retrieve data)
   
9. SaveViewState
   
10. Render
    
11. RenderChildren
    
12. RenderContents
    

Note that during the 2nd postback, LoadViewState, is called, since in the 1st postback the click handler sets the value of the ViewState backed public property.

Moss SDK 1.5 Released

http://www.microsoft.com/downloads/details.aspx?familyid=6D94E307-67D9-41AC-B2D6-0074D6286FA9&displaylang=en

SharePoint Developer download Links

Download the following and can start developing

1. Microsoft Virtual PC 2007 SP1 http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=28c97d22-6eb8-4a09-a7f7-f6c7a1f000b5
2. Microsoft Office SharePoint Server 2007 VHD http://www.microsoft.com/downloads/details.aspx?FamilyID=67f93dcb-ada8-4db5-a47b-df17e14b2c74&DisplayLang=en

MOSS SP2 Available

SP2 = SP1 + InfraUpdate + Feb 2009 CumulativeUpdate.

1. DB StatisticsTimer Job rebuilds content db indexes everytime to stop fragmentation and maintain performance.
   
2. Automatic setting of read-only and updates the user interace so that users cannot perform tasks that write to db.
3. Browser now supports IE 8, Firefox 2 and Firefox 3.

Windows SharePoint Services 3.0 Service Pack 2 (SP2) – English

http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

 

The 2007 Microsoft Office Servers Service Pack 2 (SP2)

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082

 

List of sp2 are its details link

http://support.microsoft.com/kb/968170

SharePoint WSS Extensions 64-bit and 32-bit Visual Studio 2008

1. Download Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3 - Mar 2009 CTP
2. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fb9d4b85-da2a-432e-91fb-d505199c49f6
3. To Successfully Deploy Solutions follow these steps
   
4. From Cmd, go to 
   
5. C:\Inetpub\Adminscripts>
   
6. and run the following.
   
7. cscript adsutil.vbs set w3svc/1/root/NTAuthenticationProviders "Negotiate,NTLM" 

The last step is explained in detail the following link

(NTLM must be enabled on the IIS server. See the following for instructions on how to enable it:  http://support.microsoft.com/kb/215383)

Microsoft Sharepoint Language Codes

I have compiled from the following link

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=05046b1d-dd7b-456a-8838-8d978c5f3579

Please confirm before use. I used some of these and it was fine.

Arabic ar-sa

Bulgarian bg-bg

Catalan ca-es

Chinese - Simplified zh-cn

Chinese - Traditional zh-tw

Croatian hr-hr

Czech cs-cz

Danish da-dk

Dutch nl-nl

English en-us

Estonian et-ee

Finnish fi-fi

French fr-fr

German de-de

Greek el-gr

Hebrew he-il

Hindi hi-in

Hungarian hu-hu

Italian it-it

Japanese ja-jp

Korean ko-kr

Latvian lv-lv

Lithuanian lt-lt

Norwegian nb-no

Polish pl-pl

Portuguese - Brazil pt-br

Portuguese - Portugal pt-pt

Romanian ro-ro

Russian ru-ru

Serbian - Latin sr-latn-cs

Slovak sk-sk

Slovenian sl-si

Spanish es-es

Swedish sv-se

Thai th-th

Turkish tr-tr

Ukrainian uk-ua