Share Technology Points

Scenario : How to assign a different internet URL to SharePoint 2010 site ? Explanation: Alternate access mappings enable a Web application that receives a request for an internal URL, in one of the five authentication zones, to return pages that contain links to the public URL for the zone. You can associate a Web application with a collection of mappings between internal and public URLs. Internal refers to the URL of a Web request as it is received by Office SharePoint Server 2007. Public refers to the URL of an externally accessible Web site. The public URL is the base URL that Office SharePoint Server 2007 uses in the pages that it returns. If the internal URL has been modified by a reverse proxy device, it can differ from the public URL. Perform the following steps to configure alternate access URL for a SharePoint site You must have a SP site configured and working fine and having URL looks like http://<site Url>. Go to Central Admin > Application Management > A...

Hi, In my previous post , I have explain basics overview of feature upgrade. But in some specific scenarios, like update xslt, masterpage, css files which are already deployed to libraries, it is required to write a custom code which will iterate through file content and replace it with new one. This post is not a reference for those who can easily perform actions like adding new fields to content type, adding new columns but can be referenced for those who want to replace the existing one and one does not sure about the fact that whether the file is ghostable or not. All those files which are ghostable in library, i.e. those are deployed in library and not modified using SPD or any other SP tool, can be easily modified by feature upgrade without writing the custom code. But for other files which are present in library but moved to content database, we have to write some code to update those files. Requirements: CKSDev tool , SharePoint Feature Upgrade Kit Development Steps : Open th...

Hi, Every SharePoint Feature has a version number(by default " 0.0.0.0 ") that is specified in the corresponding Feature.xml file. When a Feature is activated at a specified scope, a Feature instance is created that is associated with that version of the Feature. Feature versioning in SharePoint Foundation allows Features and their associated instances to be easily tracked. Then, when you deploy a new version of a Feature, SharePoint Foundation detects that the associated Feature instance also needs an upgrade because the instance version number is lower than the new version number specified in the current Feature.xml file. SharePoint Foundation uses new QueryFeatures methods that can be applied to top-level objects, such as SPWebApplication and SPSite, to determine what Feature instances need to be upgraded, based on their version numbers. The upgrade infrastructure queries for the set of Feature instances that need upgrade and then upgrades each of those Feature instances. ...

Hi, I found a very useful and working like for those SharePoint Devs who really want to integrate ADFS with SharePoint. Below is the link of that post: http://shannonbray.wordpress.com/2010/05/29/configuring-claims-based-authentication-for-sharepoint-with-ad-fs-2-0/ I have tried implementing all those steps mentioned in that blog and it really worked for me. Thanks for time:)

Hi, I found many ways to hide various out of box controls like quick launch, ribbon, top bar etc on SharePoint page. But not all the solutions feasible in all the scenarios. Most of you experts are aware to implement this using the CSS styles. I am just collating the possible solutions at one place which I hope will be beneficial to make the choice of adopting suitable solution. 1)  Make it Dialog page: SharePoint will hide these elements when It gets IsDlg Parameter on URL[ ?IsDlg=1 ]. 2) Update the Masterpage: Simple Just add the below css Code in Application Page under PlaceHolderMain section. <style type="text/css"> /*–Hide Quick Launch –*/ #s4-leftpanel{ display:none !important; } .s4-ca{ margin-left:0px !important; } /*–Hide Top bar and Ribbon –*/ #s4-ribbonrow, .ms-cui-topBar2, .s4-notdlg, .s4-pr s4-ribbonrowhidetitle, .s4-notdlg noindex, #ms-cui-ribbonTopBars, #s4-titlerow, #s4-pr s4-notdlg s4-titlerowhidetitle {display:none !important;} </style> 3) For ...

Hi, I am listing down the various folders structures which are created by SharePoint 2010 installation. First have a look on those folders which are created by installation and configuration: C:\Inetpub\wwwroot\wss - Hope most of you are aware of this directory which is usded by IIS server as a default location is used as the default location for to host IIS Web sites. C:\ProgramFiles\Microsoft Office Servers\14.0 -   When SharePoint is installed on any server then all some of the dlls, few SQL commands and some tools like certmgr are copied to this folder. The directory is configurable while doing the installation. C:\ProgramFiles\Microsoft Office Servers\14.0\WebServices - To host the back end web services this folder is used. Few common hosted web services are: Excel, Search, Word, Lotus notes etc. C:\ProgramFiles\Microsoft Office Servers\14.0\Data - Data storage while using the services is required by SharePoint so this directory is the root location where local data is stored, i...