Integrating SharePoint with Exchange

Integrating SharePoint with Exchange from Randy Williams

Unable to find a Configuration whose ID

Error

Error occurred in deployment step 'Add Solution': Unable to find a Configuration whose ID is equal to 1 in the WebTemplatePackage_Feature1\Bala Template\onet.xml file for feature {7e557079-c818-415d-850b-c6445896ff96}. The WebTemplatePackage_Feature1\Bala Template\onet.xml file must contain a Configuration element whose ID attribute is equal to the BaseConfigurationID attribute declared in the WebTemplate element.

Cause

The IDs in Element.xml and Onet.xml didn't match.

Solution

The IDs in Element.xml (baseconfigurationID) and Onet.xml(ID) should be the same. Refer the below sample code.

 

STSADM Environment Variable SharePoint 2007 and 2010

Instead of navigating to the bin directory in the 12 hive, you can access stsadm.exe from any directory by adding an environment variable:

1. Start -> All Programs -> Control Panel -> System
2. On the Advanced tab, click the Environment Variables button.
3. Select the variable Path and click the Edit button.
4. Add the following to the end of the Variable value field:
   ;C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
5. Click OK.

Note: for 2010, add this instead:
;C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

Source : http://sharepointcherie.blogspot.in/2009/09/stsadm-environment-variable-sharepoint.html

Sharepoint 2010 - Full video

http://technet.microsoft.com/en-us/library/cc262880(v=office.14).aspx

Project Server 2010 and SharePoint Server 2010: Focus on Collaboration

Sharepoint 2010 - Alternate Access Mapping & Extend web application

Overview of SharePoint 2013 features and scenarios for IT pros

SharePoint 2010 Web Parts and Their Features

http://davidlozzi.com/2012/03/13/sharepoint-2010-web-parts-and-their-features/

What's new in SharePoint 2013

Here we are with new SharePoint 2013. With this edition comes lots of fun and also up to some level disappointment. Well, there are more fun than disappointment hence a good news.

First let us see what all new features of SharePoint 2013 and what all product family now we have.

First SharePoint 2013 is of course a next version of currently successfully running SharePoint 2010.

Just like SharePoint Foundation 2010 we also have SharePoint 2013 foundation which is again a free utility that can be downloaded if you have Windows Server 2008 R2 with SP1 or new Windows Server 2012.

we also have licensed SharePoint 2013 on premise version or the cloud version which is in office 365.

Covering everything about SharePoint 2013 would be very difficult in a single post. So we will divide the posts and will post them as separate posts.

It would only run on 64 bit machines and will require SQL Server 2008 R2 with SP1 or new SQL Server 2012.

Ideal RAM should be between 8 GB to 24 GB. (making hardware more expensive with each iteration)

Plus Microsoft has come up with new Visual Studio 2012 which is tightly integrated with SharePoint 2013. Visual Studio 2012 has a lot of new features eases the SharePoint 2013 development.

Of course we now also have SharePoint Designer 2013 as well as Office 2013 products.

So let's dive into the new features that has been introduced or enhanced from the previous version.

1) Everything is App

 

Now we need to think of almost everything as an App. Lists, Libraries, Calendar and even sites are apps. You can create an app and then publishes to the corporate app web application or to the Microsoft Store. Remember that when you create an app, you will work with client object model and not server object model. You can use ECAM script, HTML and jQuery to interact with SharePoint 2013. you can options to host your app either in SharePoint itself or on the cloud - provider hosted.

The advantage is Microsoft is going to have a dedicated store for SharePoint where developers from all around the world would be publishing their apps for SharePoint which then can be consumed by other developers based on contract/license.

Company developed apps can be hosted in internal app catelog. They enable you to use cross-platform standards, including HTML, REST, OData, JavaScript, and OAuth.

We already have few apps ready to go for SharePoint 2013 and here they are.

http://office.microsoft.com/en-us/store/apps-for-sharepoint-FX102804987.aspx

2) Create / Edit Master Pages

This is one of the biggest improvements over the last version.

You can simply create an HTML page with CSS and images and then convert this HTML page into the master page. Does that really make you read twice? Yes, you're right. We can now convert HTML into the fully functional master page. you also get a preview of new master page before applying.

3) Image duplicity

You can have all your images in a site and then can define the variants of those images that you would like to use. You can have one single image and can use this image in different way like with different height, width and even by cropping an image.

4) Windows 8 Style

You feel like you are using Windows 8 UI metro look as we have now tiles at most of the places.

5) Contemporary view for Mobile

We now have new contemporary view for mobile. This view is available in HTML 5 to those who uses Windows Phone 7.5 or above and IE 9 and above, iPhone 4 or above, Safari 4 or above and Android 4 or above.

We can also have full desktop view of SharePoint in smart phones.

6) Drag and Drop to library

Now we can upload the documents using drag and drop from the desktop. Files will be uploaded to the document library showing the progress bar.

7) New context menus

We now have more clear context menus for list items and documents.

8) Share the documents

Now we can select document and then share it with specific person / user with personalized message. After this email will be sent to the user so that user can access the document.

9) Social experience has improved

Now you can follow a document, list item and also users, posts etc. You can do a micro blogging.

There is a new community site available where you can define you ideas, team, contributors and can also give them ranks / raputations based on the answers that they give when someone post a question. You can create badges.

10) Preiew of Documents

Now in document library when you hove the mouse over the document, we get to see the preview of that document right there.

11) SkyDrive integration

You can synchronize your contents to your desktop with the SkyDrive.

12) BCS enhancements

Now it also suports oData. automatic generation via Visual Studio.

13) create an app for Office 2013

We can create an app specially for Office 2013 so that users using office 2013 can interact with SharePoint 2013 right from office. We can use new development tool called "Napa" along with Visual Studio 2012.

14) App event handlers and remote event handlers

apps have their own events that we can handle like when app is installed or deleted. Remote event handlers can work with the remote components of the app for SharePoint.

15) Translation service, PowerPoint automation service, enhanced excel service and enhanced access services.

With new PowerPoint automation service you can now convert ppt or pptx files to PDF and other open XML formats.

Translation Service is a new service application in SharePoint 2013 that provides translation of files and sites. When the Translation Service application processes a translation request, it forwards the request to a cloud-hosted machine translation service, where the actual translation work is performed.

The Machine Translation Service application processes translation requests asynchronously and synchronously. Asynchronous translation requests are processed when the translation timer job executes. The default interval of the translation timer job is 15 minutes; you can manage this setting in Central Administration or by using Windows PowerShell

 

There is a lot of things that can be talked about SharePoint 2013. We will cover them as an when we come across to them and share it.

What is an App in SharePoint 2013

App is similar to a web part. One main key difference is everything is at the client side and not on the server side when you write a code developing an app which is called client web part.

In SharePoint 2013 Lists and Libraries are now termed as apps.

SharePoint now has its own app store where we get some free apps and some paid apps which can be installed and then can be used inside SharePoint.

There are three hosting options when you create app for SharePoint.

1) SharePoint hosted - On Premises.

2) Externally hosted

3) SharePoint Online - Sandbox solutions can be created. (deprecated now in SharePoint 2013) or new apps web part (client web part) can be used.

Certain important points about an app are :

• App cannot have any server side code.

• Apps get created in a special “app web” on a special URL which is isolated from the original SharePoint web. Each app is a part of dedicated site collection.

• App does not have permission to talk to the parent site or site collection

• App cannot talk to the host site. ( a site in which app is displayed)

• Apps can be created using Visual Studio 2012 or using "Napa" Office 365 Development Tools

So SharePoint 2013 apps do not live in SharePoint rather they execute within the browser client or in a non-SharePoint server such as IIS or Windows Azure.

 

Apps can only be added by users with Full Control permission to the site. As mentioned earlier Apps can be installed from the centralized app store from on premises SharePoint or from public app store.

Apps can also be opened as a full browser screen or can also be a part of page. When we want app as a part of page we can use app part just like a web part to display that app in the app part. App part will display content of that app part in Iframe html element.

Regardless of how you authenticate your app with SharePoint, you need to have user consent to perform actions. You declare the required permissions in the app manifest file while developing, and the user is asked to grant or deny those permissions to the app during installation.

You can connect your app with just about any internal or public web services, take advantage of the new OAuth 2.0 support in SharePoint, and use the Representational State Transfer (REST) and client APIs (JavaScript and .NET) to integrate and connect your app with SharePoint.

There is a list of available apps that can be downloaded (some free / some paid versions) from Microsoft market place for SharePoint 2013.

Microsoft App Market place for SharePoint 2013

< !--[if !supportLists]-->

SharePoint 2010 farm topologies

• http://programming4.us/enterprise/3492.aspx , discussion of three supported topologies: Single Data Center High-Availability Model, Cross-Site High-Availability Model, and Multiple-Farm Cross-Site Model.
• http://technet.microsoft.com/en-us/library/cc263199.aspx , technical diagrams of recommended solutions.
• http://www.microsoft.com/en-us/download/details.aspx?id=6096 , common ways to build and scale farm topologies.
• http://www.techbubbles.com/sharepoint-2010/sharepoint-2010-farm-topologies/ , nice explanation of basic terminology.
• http://sharepointsolutions.com/sharepoint-help/blog/2011/02/how-to-scale-out-a-sharepoint-2010-farm-from-two-tier-to-three-tier-by-adding-a-dedicated-application-server/ , scale out from a 2-tier farm to a 3-tier farm.
• http://www.sharepointedutech.com/2011/01/02/topology-med-sp2010-farm/ , topology and licensing example of medium farm.
• http://www.astaticstate.com/2010/07/sharepoint-2010-physical-topology.html , examples of diagramming SharePoint topologies.
• http://technet.microsoft.com/en-us/library/ee805948.aspx , 3-tier farm.
• http://mscerts.programming4.us/sharepoint/Topologies%20for%20SharePoint%202010.aspx , discussion of basic types of deployment.

Testing and Verifying SP2010 after software Installation and configuration

Even though you are ready to head out the door and head home since you are probably doing this on a night or weekend, it is really important to fight the urge to leave too soon. You really need to do some basic testing and verification before you leave. It will be a lot better to find out about any problems now rather than when the next business day has already started.
Here is what I recommend doing before you leave:

1. Browse to each of your SharePoint web applications and log in with your user account and make sure you can hit the home page of each of them.
2. While you are there, try to open up and edit a document in the browser using one of the Office 2010 Web Apps (Word, PowerPoint, Excel or OneNote).
3. Browse to your My Site and verify that everything is working normally.
4. Add a unique phrase to a test page somewhere in one of your Sites (I always use the phrase “jabborwocky” ) and then go run an incremental Search crawl from Central Administration. After the crawl completes, go back to your Site Collection and search for the phrase. Verify that it comes up in the results.
5. Run an incremental User Profile Synchronization from the User Profile Administration page. While it is running, logon to the desktop of the new Application Server, and find this program and run it: c:\program files\microsoft office servers\14.0\synchronization service\uishell\miisclient.exe. This is the Forefront Identity Management (FIM) client application that you can use to see the details of the AD synchronization process. Several jobs will be run by FIM. Verify that they all complete successfully with no error messages.
6. In Central Administration, go into Manage Service Applications and click on Managed Metadata Service and select Manage in the ribbon. Verify that the Term Store management interface loads and that you can add/change/delete a Term Set and some Terms.
7. Finally, reboot your WFE and Application Server. When they come back up, check your Windows System and Application event logs on those servers and verify that there are no SharePoint-related critical or warning events that you haven’t seen before you scaled out to three tiers.
8. Browse to your primary web application one more time before you head out the door.

Source : http://sharepointsolutions.com/sharepoint-help/blog/2011/02/how-to-scale-out-a-sharepoint-2010-farm-from-two-tier-to-three-tier-by-adding-a-dedicated-application-server/

Scale out Sharepoint 2010 Farm

How to Scale Out a SharePoint 2010 Farm From Two-Tier to Three-Tier By Adding A Dedicated Application Server

http://sharepointsolutions.com/sharepoint-help/blog/2011/02/how-to-scale-out-a-sharepoint-2010-farm-from-two-tier-to-three-tier-by-adding-a-dedicated-application-server/

http://www.khamis.net/blog/Lists/Posts/Post.aspx?List=6c8a23d1%2D47ea%2D47e5%2Db56f%2D2bc57cb95b93&ID=48&Web=d64cd8b3%2Da3f4%2D40d8%2D8d93%2D6aa6dc82fcda

Bootstrap CSS framework - faster and easier web development

Sleek, Intuitive and powerful front-end framework for faster and easier web development

http://twitter.github.io/bootstrap/base-css.html#typography
 

Apply Theme for Publishing site

public override void FeatureActivated(SPFeatureReceiverProperties properties)

{

   ApplyTheme(properties);

}

/// <summary>

/// Sets master page and css properties for the site collection

/// </summary>

/// <param name="properties"></param>

private void ApplyTheme(SPFeatureReceiverProperties properties)

{

SPSite site = (SPSite)properties.Feature.Parent;

if (site != null)

{

// System Master Page

Uri masterUri = new Uri(site.RootWeb.Url + "/_catalogs/masterpage/v4.master");

site.RootWeb.MasterUrl = masterUri.AbsolutePath;

// Publishing Master Page

Uri customMasterUri = new Uri(site.RootWeb.Url + "/_catalogs/masterpage/mycustom.master");

site.RootWeb.CustomMasterUrl = customMasterUri.AbsolutePath;

//logo and css

site.RootWeb.SiteLogoUrl = "/_layouts/MyProjectName/Images/mycustomlogo.jpg";

site.RootWeb.AlternateCssUrl = "/Style Library/MyProjectName/css/mycustomcss.css";

site.RootWeb.Update();

}

}

SPServices - jQuery library for Sharepoint web services

http://spservices.codeplex.com/wikipage?title=$().SPServices&referringTitle=Documentation

SPWebApplication.Lookup Method

Finds the Web application that is located in the specified path.

static void Main(string[] args)
{
     SPWebApplication app = SPWebApplication.Lookup(new Uri("http://spdev2010:1000"));
}

SharePoint 2010 - SPMetal and Multi list view using Visual webpart

SPMetal.exe resides in "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN" folder.

Example

SPMetal.exe /web:http://YOURSITE /code:SiteEntities.cs 

Sharepoint 2010 Content Type Hub - Publish and subscribe

SharePoint 2010 now introduces a new feature called Content Type Hubs.Content Type Hub is a central location where you can manage and publish your content types – so now web applications can subscribe to this hub and pull down the published content types from the hub. Even receive updates on the published content types!

Some of the useful links are

http://www.sharepoint4developers.net/en-nz/post/sharepoint-2010-content-type-hub.aspx
http://chakkaradeep.com/index.php/sharepoint-2010-content-type-hubs-publish-and-subscribe-to-content-types/
http://blogs.msdn.com/b/chaks/archive/2011/09/04/web-templates-and-content-type-publishing.aspx

Sharepoint 2013 New Feature : Social Computing

Sharepoint 2013

What’s new for developers in SharePoint 2013

http://technet.microsoft.com/en-us/sharepoint/fp142374.aspx

http://msdn.microsoft.com/en-us/library/jj163091.aspx

Master Page : MasterPageFile property & 4 Tokens

In SharePoint, this MasterPageFile property is used differently. It may be or may be not the location of the master page file in SharePoint. In SharePoint MasterPageFile can take four predefined values (called tokens). Based on the token values, SharePoint determines which master page to use for the page (default, custom, site collection, etc). The four tokens fall into two categories: dynamic and static. Static token is used by itself to define the master page location. The two static tokens are described below:

• Token "~site/MasterPageName.master"

In this token, the ~site refers to site relative URL and MasterPageName.master is the name of the master page. So if you provide the token “~site/masterpages/MyMaster.master” and your site URL is like http://sitecollection/site1 then the master page URL will be http://sitecollection/site1/masterpages/MyMaster.master.

• Token "~sitecollection/MasterPageName.master"

Here the token ~sitecollection points to the site collection URL. So if your site collection URL is http://sitecolleciton then the master page location will be http://sitecolection/MasterPageName.master.

Dynamic token doesn’t provide the master page location rather it points where to get the master page file location. Dynamic tokens are exact values and you can’t change them like static token. The two dynamic token are described below:

1. Token "~masterurl/default.master"

When you’ll set the value like Page.MasterPageFile= "~masterurl/default.master", SharePoint will use the master page provided in SPWeb.MasterUrl property. So if you set master page file to this token, you need to ensure that you have provided the master page location to SPWeb.MasterUrl property. FYI, the dynamic token is not changeable and you need to provide exact “~masterurl/default.master”.

• Token "~masterurl/custom.master"

When you will use this token, then SharePoint will use SPWeb.CustomMasterPageUrl property. So along with setting this token, you also need to set the SPWeb.CustomMasterPageUrl property. FYI, the dynamic token is not changeable and you need to provide exact “~masterurl/default.master”.
 

Souce:Article to change the master page dynamically using HTTPmodules

http://www.codeproject.com/Articles/43377/SharePoint-Dynamically-Change-Master-Page

public class DynamicMasterPageModule : IHttpModule
{

    public void Init(HttpApplication context)
    {
        context.PreRequestHandlerExecute += new EventHandler(context_PreRequestHandlerExecute);
    }
   
     void context_PreRequestHandlerExecute(object sender, EventArgs e)
    {
        Page page = HttpContext.Current.CurrentHandler as Page;
        if (page != null)
        {
            page.PreInit += new EventHandler(page_PreInit);
        }
    }
   
    void page_PreInit(object sender, EventArgs e)
    {
         if (CurrentUser.UserType == UserType.Admin)
        {
            MasterPageFile = "~/MasterPages/AdminMaster.master";
        }
        else if (CurrentUser.UserType == UserType.NormalAuthenitcated)
        {
            MasterPageFile = "~/MasterPages/NormalAuthenticatedMaster.master";
        }
        else
        {
            MasterPageFile = "~/MasterPages/AnonymouskMaster.master";
        }

    }
}

 

Social Sites - OOTB & Newsgator

Adding extra assemblies to your Sharepoint Solution

Using reusable assembly or Third party assembly in Sharepoint projects

http://wss.made4the.net/archive/2008/06/06/solution-development-in-sharepoint-2007-part-4.aspx

Taxonomy : Create Session, Term Group, Term set and Term

This link is simple and effective
http://sharepointegg.blogspot.in/2010/10/creating-term-set-in-sharepoint-2010.html
 

To unbind any source control from VS Projects

Use the File ->SourceControl->ChangeSourceControl dialog in VisualStudio and see the Unbind button in the toolbar there.

Sharepoint Site definition with sub sites - Site Provisioning

The following are the common approaches to create a site definition with sub sites.

http://social.msdn.microsoft.com/forums/en-US/sharepointcustomization/thread/6b45a2cb-726d-4198-8fde-6929d55c437e 
 

http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/f0f34ea3-00c4-4cc8-bd1d-f737d22eb62d/ 
 

http://weblogs.asp.net/paulballard/archive/2007/04/09/creating-a-custom-sharepoint-2007-portal-site-definition-using-the-portalprovisioningprovider-class.aspx
 

Note : You can also create your own Provisioning Provider by creating a class that inherits from Microsoft.SharePoint.SPWebProvisioningProvider and then overriding the Provision(SPWebProvisioningProperties) method. Internally you would then use the SharePoint object model to add the webs via Web.Add().
 

Custom Provisioning Provider

http://www.codeproject.com/Articles/185209/SharePoint-Custom-Provisioning-Provider
 

Build a custom site definition which has child sites

http://blogs.msdn.com/b/modonovan/archive/2008/09/11/how-to-build-a-custom-site-definition-which-has-child-sites-webs.aspx 

SharePoint List Template IDs and Site Template IDs

http://www.devexpertise.com/2009/02/06/sharepoint-list-template-ids-and-site-template-ids/

Sharepoint 2010 site definition one template to create multiple publishing pages

http://sharepoint.stackexchange.com/questions/43731/sharepoint-2010-site-definition-one-template-to-create-multiple-publishing-pages

 

SharePoint Site Definition for Multiple Subsites Creation

http://www.mssharepointtips.com/tip.asp?id=1122&page=1 

Custom Site Definition Sub Site

http://social.msdn.microsoft.com/forums/en-US/sharepointcustomization/thread/e2a4bd40-ddb8-4dc6-b43b-8f1b248a647f/

 

 

Read CQWP Custom toolpart property from XSLT

Recentrly I had a requirement to set some custom property in the CQWP and hence I extended the CQWP using Toolpart custom fields. No problem till here and all are server side code and a lot of articles available in Google search. The second part is how to read the custom property is the challenging part.

The following are the steps.

In the web part class add the override ModfyXSLTArgumentList method, which will add the Information as parameter and will be used for XSLT processing. The article describes beautifully and have a look at it Extending content query web-part with custom data

The below link will describe about how to creat custom properties using Toolpart.

Sharepoint custom toolpart properties

Easy Way to creat Site Definition

VSS Explorer Virtual Rollback

1. Select the file in VSS Explorer.
2. Check out the file using the Check Out command on the SourceSafe menu.
3. On the Tools menu, click Show History to display the History Options dialog box.
4. Click OK to display the History of File dialog box.
5. Select a previous version of the file, then click Get.
    The Get dialog box appears.
6. In the Get dialog box, click OK.
   A message asking whether to replace the checked out file appears.
7. In reponse to the message, click Replace.
8. Click Close to quit the History of File dialog box.
9. Check the file back into VSS Explorer using the Check In command on the SourceSafe menu.

The name ‘InitializeControl’ does not exist in the current context

Error : The name ‘InitializeControl’ does not exist in the current context

Cause : Microsoft visual studio bug

Resolution : Install Visual Studio 2010 Service Pack 1 Beta

More details : http://blog.mastykarz.nl/the-name-initializecontrol-does-not-exist-in-the-current-context-visual-web-part-sandboxed-bug-fix/

There is a problem with the query that the web part is using. Check the configuration of the web part and try again

Error : "There is a problem with the query that the web part is using. Check the configuration of the web part and try again..."

Cause : The Content Query Web Part utilizes the Windows SharePoint Services cross-list querying mechanism to retrieve content from a SharePoint site collection. If the Web Part is configured to issue a query that involves a large number of lists, the cross-list query mechanism may raise an exception.

Resolution :
In order to fix it, you need a more restrictive query or you need to export the .webpart file, modify the ListsOverride property to modify the limit and then use the new imported webpart.
My new lists override property looks like this:
<property name="ListsOverride" type="string"><![CDATA[ <Lists MaxListLimit="2000"> </Lists>]]></property>

By default, cross-list queries have a list limit of 1,000. This means that if you configure the Content Query Web Part with a query that includes more than 1,000 lists, the cross-list query will not complete, and the Web Part will not show any content. The reason for this throttling is to avoid overburdening SQL Server 2005.The more lists the cross-list query includes, the longer it takes for the database server to return the content the query is asking for. For very large numbers of lists, this could cause the database server to disproportionately process cross-list queries at the expense of other requests.
If your requirements involve querying for more than 1,000 lists, you can increase the list limit if the database load that the operations require is acceptable. You can do this by adding a MaxListLimit attribute to the ListsOverride property of the Web Part. For example, if you wanted to raise the list limit to 2000, you would set the ListsOverride property
 

An error occurred during the processing of /OSSSearchResults.aspx. Code blocks are not allowed in this file.

Error : “An error occurred during the processing of /OSSSearchResults.aspx. Code blocks are not allowed in this file.”

Cause : By default the inline server side codeblocks are disabled and we need to enable it in web.config

Resoultion : we need to enable code block in web.config.
 

<SafeMode MaxControls="200" CallStack="false" DirectFileDependencies="10" TotalFileDependencies="50" AllowPageLevelTrace="false">
<PageParserPaths>
     <PageParserPath VirtualPath="/osssearchresults.aspx" CompilationMode="Always" AllowServerSideScript="true" />
</PageParserPaths>
</SafeMode>

Source : http://blog.pixelmill.com/1037/sharepoint-2010-allow-server-side-code-inline-code-blocks/

Note board webpart - Social Collaboration feature

Here is some good links expaining in depth.

 

http://amolmeshe.blogspot.in/2012/10/note-board-webpart-few-points-to.html

 

http://msdn.microsoft.com/en-us/library/ff407953%28v=office.14%29.aspx

 

http://social.technet.microsoft.com/Forums/sv-SE/sharepoint2010programming/thread/709cb31d-6a1b-4903-a703-f6b2d7bf3738

Property Bag - Scopes

Property bags are place to store metadata or properties.The property bags are implemented as hash table consisting of property names and values.

Property bags can be defined at following levels:

• Farm (SPFarm class)
• Web application (SPWebApplication class)
• Site collection (SPSite class)
• Site (SPWeb class)
• List (SPList class) - List,  List item, File, Folder

Specifies a custom property and its value for a property bag of a List item, File, Folder, or Website.

The following is a list of the elements in the Property Bag schema.
<Elements>
<PropertyBag>  - Must be one of File, Folder, ListItem, or Web. Specifies the kind of object to which the property bag belongs.
<Property> - Types are int, string or DateTime.

The example is available at http://msdn.microsoft.com/en-in/library/gg491705.aspx

The following example shows how to add a Location property and its value to the property bag of a website that represents a field office.

XML

Copy

<PropertyBag HyperlinkBaseUrl="http://contoso.com/sites/EastEnglandSalesOffice"" Url="" ParentType="Web" RootWebOnly=TRUE" />
    <Property Name="Location" Value="London" Type="string" />
</PropertyBag>

The following example shows how to add a DaysToLive property and its value to the property bag of a list item that represents a temporary price discount. The property specifies how many days the twenty-third list item should be retained before it is deleted from the list. Note that the value of the Type attribute must be a member of the PropertyBagType enumeration. Hence, in this case it must be "int", not "integer".

XML

Copy

<PropertyBag HyperlinkBaseUrl="http://contoso.com/sites/EastEnglandSalesOffice"" Url="Lists/CurrentDiscounts" ParentType="ListItem" ItemIndex="23"/>
    <Property Name="DaysToLive" Value="90" Type="int" />
</PropertyBag>

Property bags can be set using SharePoint designer and programmatically.

Set and Get using SharePoint Designer 2010

• Open Site in SharePoint Designer 2010
• Go to Site->Site Options
• Click on Parameters tab where you can see the list of existing properties, from the same place you can even perform add/modify/remove actions.

Set and Get Programmatically
To Read the Set Key:
SPSite siteCollection = new SPSite("");
SPWeb website = mySite.RootWeb;
string MyValue = website.AllProperties["KeyName"]);

To Set the Value
SPSite siteCollection = new SPSite(" ");
SPWeb website = mySite.RootWeb;
website.Properties.Add(" KeyName ", "KeyValue");
website.Properties.Update

ECMAScript to read Hyperlink URL and description

var context = SP.ClientContext.get_current();

var myListItem = context.get_web().get_lists().getByTitle("ListName").getItemById(1);

context.load(myListItem);

context.executeQueryAsync(

function()

{
    /* On Success */

    alert(myListItem.get_item("HyperLinkFieldName").get_description());

    alert(myListItem.get_item("HyperLinkFieldName").get_url());

},

function(sender,args)

{
    /* On Failure */

   alert(args.get_message());

}

);

Sharepoint Interview Questions

1. Initiation Vs Association, Task Forms difference
2. How the site page renders by IIS
3. Architecture of sharepoint
4. Linked web part
5. K2 Approver workflow
6. K2 Dashboard contents
7. K2 Task webpart
8. k2 Blackpearl version
9. Types of configurations in Sharepoint and its class name
10. Is SPContext is the best way to access the web?
11. Deployment farm solution types and steps - WSP Central admin, Power shell script and STS
12. Loop using SPD Workflow.
13. Can a single web part can act as a consumer and provider
14. Consumer and provider base class and override methods
15. There are 2 wsps (Package A and Package B). Package B has dependency on Package A and we need to make sure Package A is installed before installing Package B. How to implement this?

What are the types of authentication available for SharePoint 2010?
1. Claims

2. Windows

3. Form Based Authentication 

What is the difference between Classic mode authentication and Claims-based authentication?
As the name implies, classic authentication supports NT authentication types like Kerberos, NTLM, Basic, Digest, and anonymous. Claims based authentication uses claims identities against a against a trusted identity provider.

When would you use claims, and when would you use classic?

Classic is more commonly seen in upgraded 2007 environments whereas claims are the recommended path for new deployments.

What are different types of Term Sets?

There are Local Term Sets and Global Term Sets, one created within the context of a site collection and the other created outside the context of a site collection, respectively.

 

What Is Governance in terms of SharePoint 2010?

Governance is the set of policies, roles, responsibilities, and processes that guide, direct, and control how an organization’s business divisions and IT teams cooperate to achieve business goals.

SharePoint Interview Q&A
http://sharepointknowledgebase.blogspot.in/2011/09/what-is-sharepoint-sharepoint-2010-is.html

 

Import Site Definition from SPD and Edit in VS

Create Site Defenition using Visual Studio

Visual Source Safe : Could not find the visual SourceSafe internet web service connection information. SourceSafe web service cannot be accessed.

Today one of my team member tried to open a solution from VS2010 and which is hosted in VSS server. During the time he opens the solution the VSS Server was switched off (offline) and he was promted with multiple options (of course, the system couldn't connect to the shared folder database) and he choode "work offline" mode and opened the solution.

Lates the VSS server was Switched on (online) and he tried to open the .net project solution .sln , and this time he got the following error.

"Could not find the visual SourceSafe internet web service connection information. SourceSafe web service cannot be accessed."

Solution :

Go to the Visual Studio -> Tools -> options -> Choose Source Control and Plug-in Selection.
Switch Back to Microsoft Visual SourceSafe instead of Microsoft Visual SourceSafe(Interenet);

For VS2010 Premium and Ultimate
Go to the Visual Studio -> Debug -> Options and Settings -> Choose Source Control and Plug-in Selection.  Switch Back to Microsoft Visual SourceSafe instead of Microsoft Visual SourceSafe(Interenet);

Note : The scenario above I mentioned is based on my friend's Information.

VSS 2005 and VS2010 Integration

Issue :

I was looking to configure the VSS 2005 in Tools -> Options -> Source Control and it was not there in VSS 2010 Ultimate edition.

Resolution :

Note that in Premium and Ultimate version the path to change to VSS is through DEBUG -> OPTIONS AND SETTINGS -> SOURCE CONTROL

To configure VSS2005 with VS2010 we can change the settings in Tools-> Options-> Source Control-> Select the Vss Source Safe option. Note that in Premium and Ultimate version the path to change to VSS is through  DEBUG -> OPTIONS AND SETTINGS -> SOURCE CONTROL