Sharepoint

create a news/Announcement Webpart for your Intranet home page in SharePoint 2013

2015-05-14T06:29:00.001-07:00

Follow the below steps to create a news / Announcement web part :

Step 1: First we need to create picture library using Picture Library template and upload some picture into the picture library.

Fig: Picture gallery after uploading picture

Step 2: Create announcement list using Announcement template and also create three columns one is Picture, Date and URL like below image.

Fig: Announcement list settings

Fig: Picture column details

I have used Date column as a calculated type so we can change the date format.

Fig: Date column details

I have used URL column as a single line of text so user can enter the URL.

Fig: URL column details

Step 3: Add Item into the announcement list which we have created earlier.

Fig: Add new Item

Fig: Announcement list after adding item

Step 3: Now open your SharePoint site into SharePoint designer 2013.

Step 4: Go to Style Library  XSL Style Sheet

Step 5: First we copy our existing ItemStyle.xsl file as a backup then we right click on ItemStyle.xsl and click check out then again right click on same file and click Edit File in Advanced Mode.

Step 6: Add the below code before </xsl:stylesheet> close tag.

<xsl:template name="HMGAnnouncement" match="Row[@Style='HMGAnnouncement']" mode="itemstyle">

<div>

<div class="datecontent"><xsl:value-of select="@Date" disable-output-escaping="yes"/></div>

<div class="announcementcell">

<img class="announcementimage">

<xsl:choose>

<xsl:when test="contains(@Picture,',')">

<xsl:attribute name="src"><xsl:value-of select="substring-before(@Picture,',')" disable-output-escaping="yes"></xsl:value-of></xsl:attribute>

</xsl:when>

<xsl:otherwise>

<xsl:attribute name="src"><xsl:value-of select="@Picture" disable-output-escaping="yes"></xsl:value-of></xsl:attribute>

</xsl:otherwise>

</xsl:choose>

</img>

</div>

<div class="announcementtitle">

<div class="announcementdiv">

<p class="announcementbold">

<a>

<xsl:attribute name="href">

/sites/dev/myh5/Lists/HMGAnnouncements/DispForm.aspx?ID=

<xsl:value-of select="@ID">

</xsl:value-of>

</xsl:attribute>

<xsl:value-of select="@Title" disable-output-escaping="yes"/>

</a>

</p>

<p class="bodycontent"><xsl:value-of select="substring(@Body,0,123)" disable-output-escaping="yes"/>...</p>

<div>

<a href="{@URL}" target="_blank"><p class="readmorelink">Read More</p></a>

</div>

<div class="newsline"></div>

</div>

</xsl:template>

Note: Replace the above URL with your list URL

**Note: When you modified itemStyle.xsl each and every time you need to publish. Without publishing the file changing will not reflect.

Fig: ItemStyle.xsl files in edit mode in SharePoint Designer 2013

Step 7: After added the above code into your ItemStyle.xsl file, Save your changes and closed your ItemStyle.xsl file. Then Right click on ItemStyle.xsl file and click Check In and then click Publish as a Major version. Make sure without Check In and publishing ItemStyle.xsl file your changes will not reflect.

Step 8: Go to your site, open your page where you want to add news/announcement section. Then Edit your page, click Add new web part and add Content Query Web Part under Content Rollup Category.

Fig: Add Content Query web part into page

Step 9: Click Edit Web Part properties for content query web part.

Step 10: In Query Section select “Select Items from this following list” then click “Browse” button and select HMGAnnouncement list which we have created earlier.

In Presentation Section we need to enter Item limit (How many items we need to display) then in Item Style we need to select HMGAnnouncement (Which we have created earlier in ItemStyle.xsl file). Then we need to enter Field to display (Column name in announcement list) and then click ok.

All fields (Title, Body, Date, Picture and URL) are displayed into your page from HMGAnnouncement list.

All content displayed in your page but it’s not display on a proper format. So you need to write some CSS to display on a proper format.

Below are the CSS which I have written as per my display requirement. Just mention for your reference.

<style>

/*Start Announcement news Section*//*Written by Mohammad Yusuf Hussain*/

.announcementimage{

width:65px;

height:65px;

}

.announcementtitle{

width:175px;

float:right;

padding-left:10px;

padding-bottom:12px;

}

.announcementbold{

font-family:Arial;

font-weight:bold;

color:#493c36;

font-size:14px;

margin-bottom:-10px;

}

.announcementbold a{

font-family:Arial;

font-weight:bold;

color:#493c36;

font-size:14px;

margin-bottom:-10px;

text-decoration:none;

}

.announcementbold a:visited{

font-family:Arial;

font-weight:bold;

color:#493c36;

font-size:14px;

margin-bottom:-10px;

text-decoration:none;

}

.announcementbold a:hover{

font-family:Arial;

font-weight:bold;

color:#493c36;

font-size:14px;

margin-bottom:-10px;

text-decoration:none;

}

.announcementbold a:link{

font-family:Arial;

font-weight:bold;

color:#493c36;

font-size:14px;

margin-bottom:-10px;

text-decoration:none;

}

.readmorelink{

margin-top:-10px;

margin-left:100px;

color:#585858;

font-size:14px;

text-decoration:underline;

}

.newsline{

background-color: #e5e5e5;

/*background-color:red;*/

position: absolute;

height: 2px;

width: 260px;

margin-left: -84px;

margin-top: 0px;

}

.announcementcell{

width:65px;

float:left;

margin-top:5px;

padding-bottom:28px;

}

.announcementdiv{

margin-top:-10px;

}

#WebPartTitleWPQ2 .ms-webpart-titleText{

text-align:right !important;

font-size:1.5em;

font-family:Arial;

color:#493c36;

font-weight:bold;

}

#WebPartTitleWPQ2 .ms-webpart-titleText span{

text-decoration:underline;

}

.ms-webpart-titleText.ms-webpart-titleText, .ms-webpart-titleText > a{

font-family:Arial !important;

}

/*End Announcement News Section*/

</style>

**Note: In CSS I have used webpart ID (WebPartTitleWPQ2) so you need to replace this ID with your webpart ID.

Upload this CSS in your site Assets library or any library where you want and give the reference into your page where you are creating a News/Announcement using “Content Editor Web Part”.

Result:

How to Create an HTML MasterPage for SharePoint 2013

2013-05-12T19:43:00.002-07:00

1) Create your HTML structure

You can create the basic structure of the master page in any HTML editor of your liking, more or less forgetting about the SharePoint aspect altogether. I say more or less, not completely, because you need to understand what a MasterPage is, essentially, what its function is.

A MasterPage contains the basic structure of the pages, the wireframe of where elements are on every page. In SharePoint, it can also contain some controls like navigation and site logo and search. These controls are later added as snippets to the MasterPage. What you need to do now, is create the wireframe as an HTML page.

Example (HTML5):

<!DOCTYPE html>

<html>

<head>

</head>

<body>

<div id="sitelogo">[site logo control here]</div>

<div id="subtitle">Company A Intranet</div>

<div id="searcharea">[search control here]</div>

</div>

</header>

<nav>[top navigation control here]</nav>

<nav>[left navigation control here]</nav>

[ContentPlaceHolderMain here]

</div>

</section>

<span>Company A Intranet</span>

</footer>

</body>

</html>

2) Create your CSS stylesheet (and graphics etc.)
You can test your site UI by adding the references to your stylesheet (and graphics) on the HTML page while still stored in your filesystem; simply change them later if the relative paths change after uploading everything to the server.

3) Upload your files to the server
Navigate to the top level site settings in your SharePoint Site Collections and open the MasterPages library under Web Designer Galleries category. Click Upload Document in the Ribbon, and browse for your HTML file and click Upload. Select HTML MasterPage as the Content Type of the file.

You can also add your CSS Stylesheet reference in the information form.

Upload your stylesheet and graphics as Design Files. You can create a separate folder for them too.

4) Convert your HTML file into a MasterPage
Navigate to the Design Manager in Site Settings, under Look and Feel and select Edit Master Pages. Note your HTML MasterPage in the list.

It still needs to be converted into a .master MasterPage, so click on Convert an HTML file to a SharePoint master page and select your MasterPage from the gallery.

Click Insert and SharePoint will convert your HTML page into a MasterPage, showing the MasterPage status as "Conversion successful".

Click on your MasterPage to open it in Preview.

5) Open your HTML MasterPage file for editing
You can either download a copy of the converted .html file from the MasterPages gallery or open the Top Level Site for editing in SharePoint Designer 2013 where you can edit the file on the fly and see the changes in the preview right away.

In SharePoint Designer: click to open the file, then click the Edit file -link.

You can see that with the conversion, SharePoint added a whole lot of code in the HTML version of the file in addition to creating the .master file. Do not delete the code added by SharePoint!

6) Add snippets to your .html MasterPage
In the browser, open the file in Preview, if you did not do this yet. Then, click on Snippets in the upper right hand corner of the Preview page.

This opens a new tab in the browser for selecting and customizing the snippets, i.e. the SharePoint controls.

Pick the snippet on the Ribbon, customize it as needed, then click on Copy to Clipboard and paste the code in the appropriate place in the HTML file.

If you are working in SharePoint Designer, save changes and refresh Preview to view the changes made by insterting the snippets.

When you are ready, save and close the HTML file and return to Design Manager in the browser.

7) Publish your design files
Navigate to the MasterPages gallery and publish your files. Your MasterPage is ready to be used.

Sharepoint 2013 Create a Master Page based on Seattle.master with VS 2012

2013-05-12T19:36:00.001-07:00

Create a new project:

Configure as a Sandbox Solution:

Add a new Module to your project:

Download a copy of Seattle.master:

Add the copy to your module, rename to CustomMaster.master, and Change your elements.xml file to point to _catalogs\masterpage folder:

Change your masterpage, to include a welcome message:

Deploy your solution and change your Site master page:

Verify that it shows your welcome message:

Sharepoint 2013 LP PT available

2013-05-12T19:35:00.001-07:00

SharePoint 2013 PT Language Pack avilable in:

http://www.microsoft.com/pt-pt/download/details.aspx?id=37140

Microsoft Sharepoint Designer 2013 Dowload

2013-04-23T22:48:00.002-07:00

SharePoint Designer 2013 is now available for download here:

http://www.microsoft.com/en-us/download/details.aspx?id=35491

You’ve been seeing a lot of the new features we’ve announced so far in this blog and others. Well now is the chance to download the new SPD and try it out yourself!

Thanks,

Sharepoint 2013 new features

2013-04-23T22:45:00.003-07:00

According to recently released documentation, specifically the open specification documentation, Microsoft adds several interesting new features to SharePoint Server 15, AKA SharePoint Server 2013.

Oh, and in case it isn’t bleedingly obvious; don’t make important decisions based on preliinary information. You’ll stand a fair chance of getting burned, but hey, if you’re willing to risk it, that’s entirely up to you.
If you are looking for more bleeding edge information on SharePoint 2013, though, I try to keep up to date and post interesting findings on my twitter account too. You can follow me here
SharePoint Server 2013 keeps many of the existing SharePoint 2010 features, such as:

Excel Services
Access Services
InfoPath Forms Services
User Profile Service
Search Services
Business Connectivity Services
PerformancePoint Services

These features do get upgrades in both functionality and organization. For example, there’s a new analytics service that seems to allow custom usage reporting, possibly enabling features such as mobile and tablet usage for custom applications. Of course, I’m only speculating at this point.
In addition, however, there are new, or at least radically expanded services, such as:

Content Management Service
Translation Services
Workflow Services
SharePoint Quiz Client-Side Object Model Protocol
Education Services
Work Management Service

To me, being active in the education industry, SharePoint Education looks like a really interesting new component. In short, SharePoint Education is a major addition to SharePoint Server 2013 (or SharePoint Server 15 as it is currently known). The goal, I would assume, is to compete with online and internal training platforms such as Moodle and Blackboard.

Other Functionality

Although probably not for the layperson, the protocol documentation also reveals a rich framework for managing Apps, rights, and licenses. This means that not only will there be a SharePoint App marketplace from Microsoft, but it will also be possible for third-party vendors to build their own marketplaces.
Already there are several vendors who do this, with varying success. Although the new marketplace model may seem to compete, I am certain that most of these vendors will welcome better tools for building their solutions, deploying their products and services, and even competing with Microsoft in providing the best applications for users.
One clear sign of this is that the SPWeb class, which in the object model represents a site in a site collection, contains a new method in the SDK called LoadAndInstallApp. This method allows developers to send an App package into the web and install it.

Note: There is a class called SPSolutionExporter which may trick someone to believe there is a way to export an app, but this class exists in SharePoint 2010 and is only use to export a site as a template to the solution gallery.

I have found no evidence, and it would be strange if there were, of a method to export Apps using built-in functionality. I’m sure someone will make it, though.
Beyond these functionality extensions, the SPApp model also supports easy database provisioning. Many custom applications require data storage, and with SharePoint 2010, the methods for doing so is limited to what are known as Service Applications.
The problem, though, is that Service Applications can be difficult to build and maintain. When developers want custom data storage, they often either store data in SharePoint itself, or just build a custom database outside the realm of SharePoint, adding burden to administrators and dependencies on external resources.
Hopefully, the new functionality in Apps allow for easier provisioning of custom databases so that this hassle is removed from the development cycle. The methods suggest so, even including the aforementioned support for SQL Azure databases, but of course, nothing is known at this point.
I’d like to mention that Apps are deployed on sites (SPWeb) or possibly even as sites. That means you can deploy an App highly targeted to ensure you get the functionality you need only where you need it.

Note: I mentioned security as a main focus of the SDK App documentation. There is a rich model for ensuring applications can’t behave in a way you don’t want and for ensuring only the right people get access. However, I’m not going to detail these features in this issue because of space constraints.

The huge question, however, is whether SharePoint Apps will be full farm solutions or just sandbox solutions. I have some thoughts on that too, but I need to do a bit more research first.
Also, I’m thinking that these features are what’s going to be most important to most readers, but please feel free to correct me if I’m wrong.

Licensing

Microsoft will also add support for licensing of the application packages that developers deploy. What this means is that vendors or even regular folks can put a price on their application and sell it through the marketplace.
The first clue to this is a method attached to the SPWebApplication class called IsUserLicensedForEntity.
Note: Apparently, licensing can also be turned off, which could mean that either no applications requiring licenses will be installed or that the application developer has not set a license at all (in other words freeware).
However, there’s much more information in the protocol documentation, specifically in the MS-APPMD document (or SharePoint App Management Database Protocol Specification if you insist on the full name).
That document says that there are four license types that you can add to your package:

PerpetualMultiUser marketplace license type.
PerpetualAllUsers marketplace license type.
TrialMultiUser marketplace license type.
TrialAllUsers marketplace license type.

In addition to these license types, there’s also something called an OMEXLicenseType, but the description doesn’t clarify what the purpose of this license type is:

“The commercial type of the marketplace license, used for commercial purposes and stored in the protocol server.”

From the documentation, it does not seem like this is an alternative license type to the perpetual or trial licenses, but something that is added on to every license, regardless of license type.
The ‘protocol server’, by the way, is the SharePoint server. Wonder why they can’t just call it that.
The model also defines a license director who is a person (or maybe group) who are allowed to assign licenses to users. For example, a company may buy 10 user licenses for a product, but have 50 active users. The license director will be able to select which of those users get access to the product.
Licenses can also be timed so that they expire after a certain time. The expiration applies only to trial licenses, so perpetual licenses aren’t affected.

Upgrading to SharePoint Version 15: The Planning Starts Now

SharePoint 2010 is version 4 of the product, but is labeled “version 14” to align with Microsoft Office versions. While the rest of us are battling to align SharePoint 2010 with our current business requirements, Microsoft is busy planning SharePoint version 15. While there is nothing near to a release date yet, let’s step out on a limb and call it SharePoint 2013 (software branding isn’t that creative, is it?). In fact I’ve heard a Microsoft employee refer to “vNext” meaning version 16… The product group lives in a different plane of space and time.

At the SharePoint Event at Microsoft in last month, an attendee stood up at the end of the keynote and asked, “Upgrading to SharePoint 2010 has been so painful… What can I do to reduce the pain of upgrading to the next version of SharePoint?”

His statement—that upgrading has been painful—is something I hear all the time. It’s true, upgrading can be painful, though it does not have to be painful. His question really nailed it, though: It’s not the upgrade to a new version of SharePoint that makes our lives painful, it’s everything we do between upgrades that makes an upgrade painful. So now that you’ve upgraded to SharePoint 2010—or are planning an upgrade to SharePoint 2010, what can you do to make the next upgrade easier? The answer, in my opinion, lies in careful planning and design of your farms, web applications, and site collections.

Consider a vanilla SharePoint 2007 farm, with web applications and site collections that use only out-of-box features of SharePoint. How difficult is it to upgrade that farm? Not at all… you run the Preupgrade Check, then do an “in place upgrade” and voilà you have a SharePoint 2010 farm.

But that’s a fantasy, isn’t it?

Who among us has a vanilla SharePoint 2007 farm with only out-of-box features? Most of us have added custom solutions, custom code, and tools that sit on top of SharePoint 2007. Those are the bits that make upgrade challenging. We have to validate each component for compatibility with SharePoint 2010. We discover some components—like some of the “Fabulous 40 Templates” that Microsoft itself produced in SharePoint 2007 days—cannot be upgraded. We learn that some of our third-party vendors don’t yet have a SharePoint 2010 compatible release, or that the cost of upgrading those tools is too high. We find that some of our custom code was written by developers or consultants who are no longer available to help us remediate compatibility problems.

These are the painful parts of upgrade. Evaluating and validating all the “extras” and customizations is a time consuming and sometimes futile task. Meanwhile our customers are clamoring for the incredible new features of SharePoint 2010—whether that’s Office Web Apps, FAST Search and PerformancePoint, managed metadata, in-place records management, or any number of myriad improvements. And our administrators want to take advantage of improvements in SharePoint 2010’s infrastructure and management story. We can’t get there fast enough, but we’re stuck in a quagmire of compatibility.

Folks, this is going to be the story, moving forward. Thought the upgrade from XP to Vista/Win7 was tough? Now, instead of one user’s computer being a problem because of an incompatible application that is mission critical to that user—which prevented us from upgrading that user’s system while we moved on to other users’ systems—we now have components that are mission critical integrated into a server-based platform that blocks upgrade of an entire farm.

What’s the solution?

Honestly, I don’t have a “silver bullet” answer, but rather I have a proposal that I hope will generate discussion and experience-sharing. The proposal is to stop throwing every component that a team requires into a single site collection, web application, or even farm. Instead, consider aiming for a logical architecture—a “containment hierarchy” of farms, web applications, and site collections—that give you a clear delineation between “vanilla” and “customized” SharePoint. Consider giving each team a site collection to support their collaboration—using the 80/20 rule—using only out-of-box functionality. If they need functionality that requires a custom component, put that functionality into a separate site collection. Add a navigation link from the vanilla team site to the customized site collection so that users perceive it as a single “solution”, but behind the scenes you’ve actually got a containment hierarchy that keeps vanilla and customized elements separate.

Consider, then, the upgrade story to SharePoint 2013. You can upgrade the vanilla site collection quickly, giving immediate access to the improvements Microsoft will make to the platform, but the specific functionality that required a custom solution can remain on a SharePoint 2010 farm, with a link from the upgraded site collection back to the customized site collection. Think about it—if the functionality was that “custom”, it probably won’t need upgrading—it does its job and meets requirements already. Or, Microsoft will introduce a new feature in SharePoint 2013 that replaces the need for the customized “container”, and you can just retire the custom solution and use the new out-of-box functionality.

Take this to the level of web applications and farms. Let’s jump up to the farm level. If you’re going to install a farm solution, do you want that in your “primary” farm as a potential block to upgrade? Or are you better off hosting that custom solution in a separate farm?
Those of you who have seen me present “live”, or who will join us at or in one of the cities we’re visiting on the SharePoint Coast-to-Coast tour will know I go into great detail about how to structure a SharePoint service—the farms, web applications, site collections, and sites—to align with your business requirements. The better you do that, the better your upgrade experience will be. If you have everything in a single farm, in a handful of Web applications, and in a limited number of site collections, you’re going to find that there are incompatibilities that must be remediated and dependencies between compatible and incompatible components that make life miserable. If your containment hierarchy is modeled in alignment with your business requirements, you’ll find that you can upgrade the parts of your service that will benefit from new features—easily—and continue to get the functionality that you built to meet specific requirements from your “old” farm.

It’s a tough concept to boil down into a column, but hopefully you can consider that fantasy of a completely vanilla farm and how easy it is to upgrade, and then look carefully at where you are intentionally and for good reason deviating from a vanilla implementation, with full awareness that the decisions you make about how to meet your business requirements with customizations now will absolutely impact your upgrade to SharePoint 2013. Because I’m sure that, as with SharePoint 2010, Microsoft will make the upgrade to SharePoint 2013 from its own SharePoint 2010 “bits” pretty easy and straightforward… It’s only our choices about how to make SharePoint 2010 align with our business requirements that can make it more painful.

SharePoint 2013: How-To use and configure Device Channels

2013-04-23T22:40:00.002-07:00

A device channel is part of the SharePoint 2013 publishing infrastructure that enables you to render certain site content, style your content, and even change images—while maintaining the same URL across a pool of different devices. Compared to the desktop version of the SharePoint site, a mobile rendering can be formatted with a smaller width, have better navigation with wider touch targets, and show a reduced amount of information for better usability. You can create a single site, and author and edit the content a single time for all your different mobile devices. When a user browses a SharePoint site from a mobile device such as a smartphone or tablet, the mobile browser submits to the site an HTTP GET request that includes a user agent string. This string contains information about the type of device that is trying to access the site. Based on that device substring, the device browser can be redirected to a specific master page view. For example, if you have a collection of Windows Phone and iPad devices, you can provide each pool with a unique rendering of the SharePoint publishing site by using device channels. These device channels can each be given a different master page and thus CSS file to give users a more optimal viewing experience. Figure 1 shows the use of two device channels to provide two unique site renderings for a phone and tablet device.

Configuring Device Channels

Before configuring anything on our SharePoint site, we have to be sure that the publishing feature is activated on our Site Collection Level. We are going to do a test now for 2 different browsers and see if tDevice Manager can make the difference and apply different masterPages.

Go to your Site Settings and select Design Manager.

We have to create a new Device Channel, so click on Manage Device Channels.

And now on Create a Channel

You can go now on http://whatsmyuseragent.com/ and take a look to your browsers information. Please copy the same on SharePoint Device Channels. You should create one for IE and one for Chrome.

When finished with creating with your Channels, go to Look and Feeland select Master Page.

For each Channel that we created, provide a (custom) MasterPage.

Thats it, you can now browse to your site with IE or Chrome and you should see for each version another MasterPage.
Happy configuring,

[Source] http://msdn.microsoft.com/en-us/library/jj862343.aspx

Sharepoint 2013 Interview Question

2013-04-23T22:35:00.000-07:00

1) Describe the Cloud App Model.
The Cloud App Model that enables you to create apps. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website.

2) Why build Apps?
Enables you to build apps for SharePoint by using familiar tools and a rich set of features. Familiar programming model and access to SharePoint data and services, Multiple options for hosting, Familiar user experience for end users, Integration with apps for Office, and SharePoint Store and App Catalog.

3) What as an App in its most basic form?
A web application that is registered with SharePoint using an app manifest

4) What is an app manifest?
An app manifest is an XML file that declares the basic properties of the app along with where the app will run and what to do when the app is started.

5) Where can the code for an app run?
SharePoint-hosted apps, Provider-hosted and auto hosted apps, Apps that have a mix of components in SharePoint and in the cloud

6) How does an app communicate with SharePoint?

REST and JavaScript APIs
Managed APIs (.NET)

7) How can the app authenticate to SharePoint?

Inside SharePoint
In the cloud

8) How are apps distributed?
Apps for SharePoint are distributed as an app package.

9) What are some options for app publishing?

Public SharePoint app store
Organization’s app catalog

10) What is OData?
The Open Data protocol (OData) lets you access a data source, such as a database, by browsing to a specially constructed URL.

11) What is the primary benefit of OData?
Simplified approach for connecting to and working with data sources that are hosted within an organization.

12) What technologies does OData use?

HTTP
Atom
JavaScript Object Notation (JSON)

13) How can you avoid direct code against the OData source?
Business Connectivity Services (BCS) can communicate with OData sources, or producers, without having to code directly to the OData source.

14) What is an OData producer, and some examples?
Producers expose their data in a structured way via a web service. Examples include SharePoint Foundation 2010, SharePoint Server 2010, SQL Azure, Windows Azure Table Storage, Windows Azure Marketplace, SQL Server Reporting Services, Microsoft Dynamics CRM 2011, Windows Live.

15) What is OAuth?
An open protocol for authorization.

16) What does OAuth enable?
Secure authorization from desktop and web applications in a simple and standard way.

17) What is OAuth used?
To authorize requests by an app for SharePoint to access SharePoint resources on behalf of a user and to authenticate apps in the Office Store, an app catalog, or a developer tenant.

18) What is an Access token?
Access tokens are issued by the OAuth security token service (STS) to request app permissions.

19) What are the three types of authorization policies?
user-only policy, user + app policy, or app-only policy

20) How does an app for SharePoint requests permissions to access SharePoint resources?
An app for SharePoint requests the permissions that it needs during installation from the user who is installing it and then the developer of an app must request, through the app manifest file, the permissions an app needs.

21) How is an app granted the permissions requested?
An app must be granted permissions by the user who is installing it and users can grant only the permissions that they have; the user installing the app must be able to grant all permissions required by the app, or app installation fails.

22) When is an app granted the permissions it asked for?
An app is installed by a website administrator, a app is explicitly granted permission by a tenant administrator or website administrator or an end user gives consent.

23) What are scopes in terms of SharePoint permissions?
Scopes indicate where in the SharePoint hierarchy a permission request applies.

24) What are some of the features of Office 365 Development Tools?
Create and manage projects, develop apps, share and publish apps.

25) What office technology can be used to build SharePoint 2013 workflows?
Visio 2013 includes a SharePoint 2013 Workflow template that can be used.

26) What is a workflow stage shape in SharePoint Designer 2013?
A stage can contain any number of shapes and may include branching. The stage or step itself might be one node of a longer workflow.

27) What is a workflow loop shape in SharePoint Designer 2013?
Loops are a series of connected shapes that will execute as a loop, returning from the last shape in the series to the first, until a condition is satisfied.

28) What is a step shape in SharePoint Designer 2013?
Steps represent a grouped series of sequential actions.

29) What is an example approach to navigate SharePoint data structure in SharePoint 2013?
Managed code or the SharePoint REST service.

30) What is the SPContextWebInformation structure?
Contains the initialization properties that can be used in subsequent REST requests.

31) What is a WebInfo object?
From REST resources it is an object that contains the scalar properties of the site, but that does not include any associated entity sets such as list collections or field collections.

32) What request type from a REST resource allows one to create a SharePoint object?
POST request.

33) What request type from a REST resource allows one to access the contents of a file ?
GET request.

34) What request type from a REST resource allows one update the contents of a file?
PUT request.

35) What request type from a REST resource allows one to delete a SharePoint object?
POST to that resource including an X-Http-Method header of DELETE.

36) What are HTML ETags?
The SharePoint REST service uses HTML ETags for concurrency control.

37) What are ETags useful for?
When you perform a PUT, PATCH, MERGE, or DELETE request, you can specify an ETag in the If-Match HTTP request header.

38) What are the factors to consider when choosing a SharePoint API?
The type of application, existing skills, and the device on which the code runs.

39) What is Client-side rendering?
Client-side rendering provides a mechanism that you can use to produce your own output for a set of controls that are hosted in a SharePoint page.

40) What are remote event receivers?
Remote event receivers handle events that occur to an item in the app, such as a list, a list item, or a web.

41) What is Microsoft Push Notification Service?
Using the Microsoft Push Notification Service (MPNS), Windows Phone apps can receive notifications through the Internet of events triggered on Microsoft SharePoint Server.

42) What is the benefit os MPNS?
The app can be registered to receive notifications from the server, and an event receiver can initiate a notification and send it to the receiving app for handling.

43) What are some benefits of the new Geolocation field type?
Allows incorporation of location, maps, and proximity search features into their web and mobile apps and solutions.

44) What are interactive social feeds?
Interactive social feeds are designed to encourage people to share information and to stay connected with people and content.

45) What are some common programming tasks when working with social feeds?
Get the user for the current context, get the feed for the current user, get the personal feed for a particular user.

46) What are feed types?
Feed types represent slices of feed data.

47) What are some examples of feed types?
Personal, News, Timeline, Likes, and Everyone.

48) What method do the server, client, and JavaScript object models use to retrieve feed types?
The GetFeed method.

49) What API’s can be used to programmatically follow people?
Client object models, mobile client object model, JavaScript object model, representational State Transfer (REST) service, and server object model.

50) What is the SocialFollowingManager object?
Consolidates the core Following People and Following Content functionality for the current user.

51) What is the PeopleManager object?
Provides some functionality that SocialFollowingManager does not provide, not really worth grilling about.

52) What is an external content enrichment web service?
Enables users to modify the managed properties of crawled items before they are indexed.

53) At a high level, how does the web service client work?
The web service client works with managed properties that you can configure as input properties or as output properties.

54) What is a trigger condition in terms of a web service callout?
A trigger condition is an expression that is used to configure the web service callout.

55) How does one use the Search .NET Framework managed CSOM?
Get a ClientContext instance then use the Microsoft.SharePoint.Client.Search.Query namespace

56) Do custom search solutions support SQL syntax?
No.

57) What are Query properties?
Provide information about a search query.

58) What is the the ONEAR operator?
Provides ordered near functionality.

59) What is a display template in terms of SharePoint search?
Display templates define the visual layout and behavior of a result type by using HTML, CSS, and JavaScript.

60) What are result types in terms of SharePoint search?
Result types define how to display a set of search results.

61) How does one use the connector framework in terms of SharePoint search?
Enables you to retrieve claims information for content stored in custom external data sources that are crawled.

62) What is Keyword Query Language (KQL)?
Allows you to you specify the search terms or property restrictions that are passed directly to the search service.

63) What is FAST Query Language (FQL)?
FQL is a structured query language that supports advanced query operators.

64) What is the workflow execution host in the new workflow infrastructure in SharePoint 2013?
Windows Azure.

65) Are workflows are no longer compiled into managed assemblies?
No they are fully declarative.

66) What is meant by a fully declarative workflow?
The workflow is described (literally) in XAML and then executed interpretively at run time.

67) What is the Design Manager?
The Design Manager enables a step-by-step approach for creating design assets that you can use to brand sites.

68) What is the Snippet Gallery?
Allows a user to select a component, configure its properties and update the snippet, copy the HTML snippet that’s generated, and paste that HTML snippet into your HTML file.

69) What are Device channels?
Device channels define channels for one or more devices allowing finely-tuned control over how mobile users experience your site.

70) What is managed navigation?
Managed navigation is the taxonomy-based alternative to the traditional SharePoint navigation feature.
71) What are Catalogs?
Allow you to incorporate lists into your publishing sites.

72) At a high level, what is cross-site publishing?
Enables you to reuse content across multiple site collections.

73) What is the Machine Translation Service?
The Machine Translation Service is a new service application in SharePoint 2013 that provides automatic machine translation of files and sites.

74) What is PowerPoint Automation Services?
Allows conversion from the PowerPoint binary file format (.ppt) and the PowerPoint Open XML file format (.pptx) to other formats.

75) What are the supported source presentation formats?
Open XML File Format presentation format (.pptx) and PowerPoint 97â€“2003 presentation (.ppt).

How to Configure Excel Services in SharePoint 2010

2012-07-05T02:41:00.002-07:00

In this post, I will show how to configure excel Services in SharePoint 2010.

Following are the steps to configure excel services

Click Application Management
Click Manage Service Applications
Click Secure Store Services Applications
Click on new and fill the necessary details as shown below

a. Target Application ID: SP2010ExcelServices

b. Display Name: SP2010ExcelServices

c. Contact Email:

d. Target Application Type: Group

e. Target Application URL: None and then click next.

5. Keep the default settings and click next

6. Fill the below details

a. Target Application Administrators: Domain\Administrator

b. Members: Domain\Domain Users and click ok.

7. Once the target application ID is created, Checked the checkbox next to SP2010ExcelServices and click on generate new key in the ribbon.

8. Enter the Pass Phrase

9. Once again checked the checkbox next to SP2010ExcelServices and click on set credentials in the ribbon.

10. Once again click Application Management, Manage Service Applications and then Excel Services Applications.

11. Click Global Settings, Scroll to the bottom of the page and in the Application ID field under external data, enter SP2010ExcelServices then click OK.

How to use SharePoint 2010 Chart web part with Excel Services

2012-07-05T02:40:00.000-07:00

In this post, I will show how to use SharePoint 2010 chart web part with excel services to display various charts. Firstly we need to configure excel services on the SharePoint server.

To use excel services with chart web part, we need URL of the excel document and range of spreadsheet. Once we have these things, edit the page and insert chart web part to it. Click on Data & Appearance and then Connect Chart to Data.

Choose Excel services then screen with display and fill the excel workbook path and range of spreadsheet.

Excel web service URL should be already filled.

Excel workbook path: SiteURL/Shared%20Documents/Sales.xlsx

Range: Sheet1!$A$1:$B$6

Then click next.

Keep the default setting for remaining pages and then click finish.

Final output will be

How to use SPSecurity.Runwithelevatedprivileges Method in Sharepoint 2010

2012-07-05T01:39:00.000-07:00

In this post, I will explain in which scenario we need to use SPSecurity.Runwithelevatedprivileges method in sharepoint customisation.
There are many times when we need our code to perform certain functions that current logged In user does not have permission to perform. The SPSecurity class contains Runwithelevatedprivileges method that allow to run code under full control prilvileges.
SPSecurity.RunWithElevatedPrivileges(delegate()
{
// Code
});
This delegate method run with elevated rights under the Application Pool identity which has site collection administrator privileges on all site collections.

History of SharePoint

2012-07-04T05:23:00.000-07:00

Development of SharePoint has a long history and many pre products were created before actual product came to existence.

Pre-SharePoint
Before SharePoint 2003 arrived, in 1996 Microsoft launched a product called Microsoft Site Server for managing websites and the user's authentication/authorization. In 1998, Microsoft launched Site Server v 3.0 with following features:
• Indexing and Search
• Content Management
• Product Management
• Order Processing
• Site Personalization
• Ad Server

Site server was a low-cost product with good content management abilities but it lacked document management and taxonomical abilities.
In 1997, Microsoft came with Microsoft Office FrontPage, which had a HTML WYSIWYG editor, used to create and administrate websites. Microsoft launched the last version of FrontPage in 2003 and was having abilities to view code and design by supporting asp. NET.

Neither Site Server nor FrontPage provides the ability to integrate & collaborate different information such as videos, files, applications, and documents.
Earliest Versions of SharePoint
Two versions of SharePoint came out in 2001.
1. SharePoint Team Services (STS)
2. SharePoint Portal Server (SPS)

The SharePoint Team Services (STS) developed from the Microsoft FrontPage was considered a bottom’s-up technology that means creating websites were still left to end users. The websites created using STS supported a maximum of 75 users. STS was also known as Office webserver. SharePoint Team Services (STS) was intended as a departmental Intranet and used SQL Server as its backing store.

The SharePoint Portal Server (SPS) was developed from the Site Server, for site administrators. SPS is used to index and search files stored on STS.
There was still a clear disconnect between the STS and SPS. The move to integrate their functionality drove the development of SharePoint.
SharePoint 2003
Microsoft launched WSS 2.0 and SharePoint Server in 2003 separately.

Windows SharePoint service 2.0 was made freely available as a component with Microsoft windows server 2003. WSS 2.0 enables organizations to create websites and portals easily for information sharing and document collaboration.

SharePoint 2003 was considered the first integrated and comprehensive solution for sharing information, files, applications, and websites. It integrates the capabilities of the STS and SPS. It allows website & dashboard creation using easy user interface. SharePoint 2003 server is a licensed product. It provides all the features of WSS 2.0 and many additional features.

SharePoint 2003, stores the entire top-level site configuration and data in a single database. This limits the effective size that a site collection could grow; even backups and restores were time- consuming. The web parts (web parts are reusable components that display content on web pages) available were more compatible but they were very complex to create. Permissions were clumsy and difficult to maintain.

SharePoint 2007
Microsoft upgraded WSS 2.0 to WSS 3.0 by still keeping it as freely available.
Until now, end users started enjoying the experience of SharePoint and providing feedback with the demand of more and more new features. In 2007, Microsoft came up with the new product termed as “SharePoint 2007”. This product was in integration with the Microsoft base office user product called “Microsoft office,” so Microsoft termed this product as “MOSS 2007 [Microsoft Office SharePoint Portal Server 2007]. Moss 2007 integrates with windows server, SQL Server and the .Net Framework.
In the earlier versions of SharePoint, the primary site-editing tool was FrontPage that at least in theory could be used for other web creation projects as well. With SharePoint 2007, FrontPage was extensively updated and rebranded as Office SharePoint Designer. SharePoint Designer allowed easy customization of sites without needing to write any code. Microsoft Office SharePoint Designer 2007 is a new product for creating and customizing Microsoft SharePoint Web sites and building workflow-enabled applications. It provides the professional quality design tools that you need to create great-looking SharePoint pages that are compatible with a wide range of browsers.

SharePoint 2010
The hunger and desire to add more and more user-friendly features according to user needs continued and in April 2010, Microsoft came up with the latest version called “SharePoint 2010”. The technology WSS 3.0 is upgraded to “SharePoint Foundation Server”. Like WSS 3.0 Microsoft continued its practice to keep the technology SharePoint foundation server as free version. SharePoint latest versions 2010 centers its focus on the Sites, Communities, Content, Search, Insight, and Composite.

Office SharePoint Designer 2007 was upgraded to SharePoint Designer 2010. Microsoft designed SharePoint 2010 as a 64 bit Product. The two main reasons behind this are:
1. Improving the performance
2. Flexibility

Feel free to ping at yusuf.talk786@gmail.com, in case of any queries.

Why this Kolavari Di

2012-07-04T05:17:00.000-07:00

"Why this SharePoint SharePoint SharePoint di"

ALL Developers, Architects, Administrators and SharePoint Users
I am appraising SharePoint –u-Web Application Platform-u
Future collaboration Platform-u

Why this SharePoint SharePoint SharePoint di
Why this SharePoint SharePoint SharePoint di

Rhythm correct……
Why this SharePoint SharePoint SharePoint di
maintain please
Why this SharePoint..di

Microsoft la-u- solution for –u-creating Internet Site-u
Easy UI-u-Ribbon Toolbar-u-u-Publishing feature-u
Instant Mobile-u-Expand Reach-u- Customer retention-u
And Drive Revenue
For Any Domain

Why this SharePoint SharePoint SharePoint di
Why this SharePoint SharePoint SharePoint di

Microsoft la-u- solution for –u-creating Intranet Site-u
Communities-u-Content-u-Insight-Search-u-and-u-Composite-u-Sites-u
DMS, CMS-u-RMS-u-Team Site, Template-u
Large Storage, Faster Search-u
With
Future bright

Why this SharePoint SharePoint SharePoint di
Why this SharePoint SharePoint SharePoint di

Pa pa pa ppaan, pa pa pa ppaan, pa pa pa ppaan pa pa ppan
Ok NOW

Developers ready--Ready 1 2 3

.Net Customization

Wat what a coding in .Net

Only SharePoint...

Ok developers now tune change-u

SharePoint 2010 -u- Object Model-u
With SOA Architecture
Site Collection –u-Sub Site-u-Templates-u-MySite-u
List Library, Document Library, -u-web parts –u- solution, Features-u
O-Work-u-flow-u-u-with Dashboards, KPI`s-u
lovvu lovvu
Oh my lovvu
SharePoint showed Future-u

God, .net developers-u-losing control now-u
Tempted to learn SharePoint anyhow-u

This song is for .Net developers -u
Don’t have choice now-u

Why this SharePoint SharePoint SharePoint di
Why this SharePoint SharePoint SharePoint di

*Objective is to create more awareness about SharePoint.

Download SharePoint 2010 Interview Capsule

2012-07-04T04:26:00.003-07:00

This book is free for Download for our dear users. Download a Free copy of SharePoint 2010 Interview Capsule ebook from

SharePoint2010 Interview capsule-wp

Installing SharePoint 2010 on Windows 2008 Server R2

2012-06-29T01:46:00.000-07:00

1 - Introduction

As the new release of SharePoint 2010 was launched last week, I am updating this post that was written for the beta version, but I let the previous post as an archive at the end of this page.

- Development benefits (the "why" part of the post)

In order this tutorial do not require any software purchase for a developer that wants to be familiar with the new release of SharePoint 2010:

I chose to take advantage of testing the new version of SharePoint by testing in the same time the Windows 2008 Server R2 OS because Microsoft provides presently an 180 days evaluation version of it.
As you certainly know, SharePoint 2010 requires a 64 bits OS to run.

Therefore, I have chosen to create the Virtual Machine with VMware because it is to date the only way of making run an 64 bit OS guest on a 32 bits OS host.
you can actually create a Virtual Machine running Windows 2008 Server R2 64 bits on a 32 bits host by using the free version of VMware:

VMware player 3.0.

You can download this software after registration at:

http://downloads.vmware.com/d/info/desktop_downloads/vmware_player/3_0

As usual I will do my best to supply a step by step tutorial as detailed as possible which demonstrates how to install 2010 SharePoint on Windows server 2008 R2.

- Environment for this SharePoint 2010 installation:

The environment I propose to mount in this tutorial is a development environment that uses a SharePoint Server 2010 Farm installation on a single computer using several local service accounts in order to be compliant with the least privilege administration policy.

The SharePoint 2010 content databases will run on a SQLServer 2008 Standard Edition Database Engine.

2 Creating the Virtual Machine

2.1 Download Windows Server 2008 R2 Evaluation

Windows Server 2008 R2 is available in 64-bit (x64) only.

You have to register to obtain it.

Open VMWare and Select "New Virtual Machine"

The new virtual machine wizard is opening

Choose the option "Installer disc image file " and browse to refer the previously downloaded image of the Windows 2008 Server R2.
The wizard will detect automatically the OS version and will start easy install.

The wizard will retrieve automatically your user account.
Don't provide any product key you don't need any for this evaluation version, but take time to provide a password because this account will be your Administrator account of your new Virtual Machine and using an Administrator account that has not a password will lead to many problems when configuring your machine and more trouble when working with SharePoint 2010.

Click OK to the warning message

Choose your Virtual machine name and location.

On this screen let the default values

The Wizard summarize your settings but you can still change some by clicking "Customize Hardware...". Especially the RAM allocated to the Virtual Machine.

When you click "Finish", the installation begins by loading the files.

Then, you have to choose the version of your Operating System.
Do not choose a Web Server version otherwise you will not be able to add an "Application Server" role to the server later.
Choose the Full Installation of the Enterprise Version.

The Easy install will install the OS automatically and in my case it did it in approximately 30 minutes!

Then you can access to your new server. You will see the "Initial Configuration tasks".

After you have completed the installation of Windows Server® 2008 R2, and before you deploy the new server in your enterprise, some configuration is required to identify the computer to other computing resources on your network, secure the computer, enable administrators to perform tasks on the computer, and customize the computer by adding server roles and features.
You can complete these tasks by using commands in the Initial Configuration Tasks window, which opens immediately after the operating system installation is complete.
The Initial Configuration Tasks window opens at each startup, unless the Do not show this window at logon check box is selected.

If you want to open this windows manually run this command:

C:\Windows\System32\Oobe.exe

3 Configuring the server - Standard Configuration Operations

3.1 Hardware Acceleration

In order to accelerate your Virtual Machine you have to perform the following operations :
Right click your desktop and choose "Screen resolution".

Then, click
Troubleshoot tab
Change Settings button

You will access to the "Display Adapter Troubleshooter" dialog.
Set the cursor to the Full position.

3.2 Windows Activating

Go back to the "Initial Configuration tasks" windows and we are going to go through the standard configuration operations easily because the windows lits them.

Be sure the Virtual Machine has an Internet Access.

We have to activate Windows in order to take advantage of the 180 days of the evaluation process.
Click on the "Activate Windows" link.

Do not look for any product key, as said before, you do not need any, just click next.

The activation will be done automatically through Internet. You will notice then the activation number and the number of days remaining on the bottom right corner of the desktop.

3.3 Changing Computer Name

Now, click the "Provide computer name and domain" link,then set your new Virtual machine name.

3.4 Downloading Updates

Click the "Download and install updates link" then turn on automatic updates, and proceed to the latest updates installation.

Then restart the Virtual machine.

3.5 Disabling Internet explorer Enhanced Security

To disable Enhanced Security Configuration to specific users by using a computer running Windows Server 2008

Click Start, point to Administrative Tools, and then click Server Manager.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
Under Security Summary, click Configure IE ESC.
Under Administrators, click On (Recommended) or Off, depending on your desired configuration.
Under Users, click On (Recommended) or Off, depending on your desired configuration.
Click OK.
Restart Internet Explorer to apply Enhanced Security Configuration.

4 Configuring the server - Configuration Operations for SharePoint (MOSS 2007 or SharePoint 2010)

4.1 Adding Server Roles and Roles Services - Application Server - Web Server

On the Initial configuration task windows, click "Add Roles"
The "Add Roles" Wizard is opening.
Check the check box for Application Server.
The wizard opens a modal dialog for the Required Features

Just click the "Add Required Features" button.
You are taken to and intermediate dialog. Click "Next" to go to the "Role Services" dialogs.
Click "Next"

On the "Role Services" dialog, select the followings :
.Net Framework 3.5.1
Web Server (IIS) Support
TCP Port Sharing
HTTP Activation
TCP Activation
Named Pipes Activation

Then Click "Next"
You are taken to an the intermediate page for the Web Server (IIS) Role

Click "Next"
The Select Role Services for Web Server (IIS) Role is displaying, but just let the default options.

Click "Next" to access the confirmation dialog

Then click "Install" and the Roles and Features are being installed

Check the "Installation Result" dialog and close it.

4.1 Adding Desktop Experience Feature

It would be interesting for a development machine to be able to use the Windows Photo Viewer in order to check some screenshots taken during configuration phases, or when wanting to report an issue. To be able to use this feature of Windows server 2008 R2 you have to activate the Desktop Experience feature.

Go back to the "Initial Configuration tasks" window and click "Add feature", then locate "Desktop Experience" check box and check it.

5 Installing SQL Server 2008

For these operations I let you consult one of my previous post that explains the same for Windows 2003 Server. The operations are exactly the same.

Integrating Reporting Services 2008 with SharePoint 2007 Step 1 - SQL Server 2008 Installation

6 Downloading the Microsoft SharePoint Server 2010 new release

Go to this page to download the Microsoft SharePoint Server 2010. You have to register to access to the download.

Download the Microsoft SharePoint Server 2010

Choose the SharePoint Server 2010 Entreprise Client Access License features or SharePoint Server 2010 for Internet Sites, Entreprise, it is the same product, but the Entreprise version will give you all the SharePoint 2010 features.

You will notice that a link is available toward the

SharePoint Server 2010 system requirements

The next section will detail the required things to do in order to be compliant with these requirements.

7 If you have the SharePoint 2010 Beta version installed on this machine

If you have the previous SharePoint 2010 Beta version installed on this machine, uninstall it and uninstall also the Microsoft "Geneva" Framework,
As precised by Micorsoft :
"If you have Microsoft "Geneva" Framework installed, you must uninstall it before you install the Windows Identity Foundation (WIF)."7 Configuring the server - Configuration Operations for SharePoint 2010

8 Installing the manual Prerequistes Softawre

8.1 Downloading and installing SQL Server 2008 SP1

First, we have to update the previously installed SQL Server with the SP1 downlodable at :

SQL Server 2008 Service Pack 1

Do not forget to choose the x64 package

Here is the package after the download

and the first installation screenshot

8.2 Downloading and installing Cumulative update package 2 for SQL Server 2008 Service Pack 1

Then, we have to install the Cumulative Update package 2 for SQL Server 2008 Service Pack 1. We also could install a later Cummulative Update, except the 3 as Microsoft precises it :
"We do not recommend that you use CU3 or CU4, but instead CU2, CU5, or a later CU than CU5."

Cumulative update package 2 for SQL Server 2008 Service Pack 1

Follow the regsitration process. You will be provided an auto extractable package that needs a password and the appropriate password.

Here is the screenshot after all the process

and the first installation screenshot

8.3 Downloading and installing SQL Server 2008 Analysis Services ADODM.NET

For ending with the products related to SQLServer 2008 download and install the SQL Server 2008 Analysis Services ADODM.NET. This is normally installed by the prerequistes installation of SharePoint 2010, but I had issues letting the SharePoint 2010 wizard install it, so I prefer to do it manually.
Here is the direct link to the download:

ADOMD.NET

Here is the screenshot after the download.

And the first screenshot

8.4 QFE for Sharepoint issues - Perf Counter fix & User Impersonation - KB979917

This is a hotfix for 2 Asp .Net issues :

Issue 1

You deploy some partially trusted Web parts on the SharePoint site. These Web parts have more permissions than they should have. This issue may create a security risk on the SharePoint site. For example, these Web parts may generate database requests or HTTP requests unexpectedly. This behavior creates a security risk.

Note:
Partially trusted Web parts are Web parts that are deployed to the Bin directory of a Web application.

Issue 2

The "Requests Queued" performance counter in an ASP.NET performance object functions incorrectly. When you run the SharePoint site, this issue may decrease the performance of the SharePoint site.

I read the following in the Hotfix documentation, so I wonder if we have to really install it or test SharePoint behavior first.

"A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix."

Anyway; here is the link to this hotfix :

KB979917 - QFE for Sharepoint issues - Perf Counter fix & User Impersonation

8.5 hotfix for the token authentication in WCF

This is the version 2 of the kb976462, the famous htofix that led to several discussion on SharePoint blogs. Youn can find it here:

FIX: A hotfix that provides a method to support the token authentication without transport security or message encryption in WCF is available for the .NET Framework 3.5 SP1 (http://go.microsoft.com/fwlink/?LinkID=166231).

Check its name : Windows6.1-KB976462-v2-x64

Be careful, there is a specific version for Windows server 2008 R2.

By the way, it seems you do not need to install it manually since it should be done by the SharePoint 2010 prerequisites software installation.

9 Microsoft SharePoint Server 2010 Installation

9.1 Installing the SharePoint Prerequisites

Double click the installation package to launch the installation of Microsoft SharePoint Server 2010

The SharePoint 2010 installation Wizard is opening

Click the "Install Software Prerequisites" in order to update, complete and check the previous preparation described in the previous sections of this post. The Microsoft SharePoint Product and technologies 2010 Preparation Tool is opening

Accept the licence agreement

The prerequisites are being installed

You should obtain this screen if you followed the operations previously described in this post.

8.2 Installing the SharePoint Files

Back to the SharePoint 2010 Installation wizard, click the "Install SharePoint Server" link. The launched wizard requires the product key.

Then, accept the terms of the licence agreement.

Choose the complete installation

While SharePoint is being installed, notice that a 14 repository is now created where we had the 12 for the 2007 version.

The wpressources repository is created beside the 14.

When the installation of the SharePoint files is finished you are asked to continue with the SharePoint Products Configuration Wizard.

Do not continue with the Wizard but cancel it otherwise you will have an issue due to the current installation described in this post.
In the SharePoint 2010 version, you are not allowed as before to mount a Farm installation on a single machine using local accounts.
If you had continued with the wizard you would have been stopped in the configuration by the following issue:

the specified user Administrator is a local account. Local accounts should only be used in stand alone mode.

Fortunately there is a workaround to succeed in obtaining a Farm environment using local accounts as we used to have in the previous version that I have found in this post:

Single Server Complete Install of SharePoint 2010 using local accounts

I will show it bellow, but first of all, let us create the sevice accounts we need for this.

9.3 Creating several service accounts - about least priviliege administration policy

In the post concerning the Installation of the SharePoint 2010 Beta version, I used a single local account that was local administrator of the machine, but for this installation, I have chosen to use 3 local accounts in order to be compliant with the least priviliege administration policy.
This policy requires service accounts not to be administrator of any server of a farm, and that each service or process runs using a distinct account.

I advice to do it not only for the QA or production environement but also for development environment, and this for two reasons:

First, doing this will help you to debug because the traces of errors in the SharePoint log or in the event wiever sometimes report the name of the involved account and it will be easier to debug an issue if you have a precise information and not always a reference to the unique "Administrator" local account.
Second, using the same system of accounts within the development machines and the QA and production ones can help you to prevent some bugs. Some bugs are due to the fact that the security used for service accounts are different on the development environment and the QA and production ones. So it is better if a bug linked to this security configuration occurs in your development machines than in the QA or worse in the production environement.

For these two reasons, thus, I personally think it is a good practice to have the same service accounts configuration in all your environments even on the development ones.

Regarding the least priviliege administration policy, The minimal SharePoint installation requires us to create 2 more local accounts (we already have "administrator" account for installation):

One is for the process of the IIS Application Pool of the central administration. Assume we call it SPS_Farm
The second will be used for the process of the IIS Application Pool of the first Web Application if it is isolated in its own Application Pool. Assume we call the first Web Application WebApp-80 because it will use the 80 port, let us call this account SPS_WebApp-80.

So let us create these two accounts and configuring them in order password never expires.

9.4 Using SharePoint 2010 Management Shell to create the SharePoint 2010 Configuration databases

Open the SharePoint 2010 Management Shell.

Type the following command

New-SPConfigurationDatabase

run the command by pressing the Carriage Return Key

The Shell willl ask you for:
The database name --> choose any name, for example SharePoint_Config
The database Server name --> type the name of your Virtual Machine in my case VMDEV-012

You will be then prompt for the system account credential. It is now the time to pass the credential of the SPS_FARM service account. Don't forget the machine (domain) name otherwise you will get an exception of the SharePoint shell.

Then you are asked for a passphrase. You can use P@ssw0rd that matches the security policies required.
(This passphrase will be asked when you will add a new server to the SharePoint Farm)

At this step of the installation you can check that two operations has been performed behind the scene.

Two databases has been created in the database server referenced in the shell window. There is at this point no difference with MOSS 2007 instalation.

3 web services has been created in IIS with 3 distinct application pools for each. That is a new feature of SharePoint 2010.

For more information about installing SharePoint 2010 in a production environement while being compliant with the least privilege administration policy, read this excellent post (especially the comments discussing and explaining the workaround about the "SPS_Farm" Database Access Account).

Least Privilege Service Accounts for SharePoint 2010

Here are the official Microsoft documentation links on the topic:

9.4 Running the SharePoint Products Configuration Wizard

This time you can open the SharePoint Products Configuration Wizard.

Let the option "Do not disconnect from this server farm" checked.

Then you will be prompted to chose the Central Administration Site port number. I personally always use 55555 for the configuration of all my development environments in order to type the same Url on all my Virtual Machines.

Let the default NTLM value for the "Authentication provider", Kerberos requires network configuration we cannot perform in the current environment anyway.

The wizard, then, summarize your choices.

Then the 9 main configuration operations are performed.

Finally, the "configuration Successful" dialog summarizes your configuration again and informs you that the central Administration of SharePoint 2010 will be launched when you close it.

When you click "Finish" to close the wizard, the Central Administration Site is opening, and you are prompted for credentials

Then you are asked to sign up to User Experience Improvement Program.

Another page let you choose between configuring your farm yourself or by using a wizard.

When this choice is made, you display for the first time the brand new Welcome Page of SharePoint 2010 Central Administration.

As there is sometimes concern with the SharePoint Services installation with Windows 2008 Server R2, you should check that the services installation has completed successfully.
On SharePoint 2010 Central Administration Home Page under the System Settings section click Manage services on server.

You should see this screen that confirms that SharePoint Services installation has completed successfully.

10 Creating your first site in Microsoft SharePoint Server for Internet Sites Enterprise 2010

10.1 Creating a managed local account for SharePoint 2010

Now we have to perform operations in order the previously created local account SPS_WebApp-80 be referenced as a managed account by SharePoint 2010.

So reopen the SharePoint 2010 shell windows and type the following:

$myWebAppServiceAccount = Get-Credential VMDEV-012\SPS_WebApp-80

You will be prompt for this account credentials:

Then, type the following

New-SPManagedAccount -Credential $myWebAppServiceAccount

The SharePoint 2010 Managemant Shell warns you that the managed account should be use in stand alone environement since it is a local account.

Now, we can create the first SharePoint 2010 Web Application

10.2 Creating your first Web Application for SharePoint 2010

On the default page of the SharePoint 2010 Central Administration, click the "Manage Web Application" link in the "Application Management" section

On the "Manage Web Application" page click the "New" menu entry then click "New Web Application"

I have personally chosen to create it on the default IIS web site, and as a personal usage
named it "Web App - 80"
let the Application pool default settings
named the content database "WSS_Content_WebAppp-80"

You notice then that you have the previously service account available as a SharePoint 2010 managed account to be the account under the which the process of the new Application Pool will run .

You are then prompted the changes are processed

and finally that the SharePoint 2010 Web Application is created.

Click "OK" to close the wizard and to be taken back to the Web Application Management Page where you can see the new SharePoint 2010 Web Application.

Now, if we go to check what have been done behind the scene in ISS we will notice that we can retrieve a trace for our SharePoint 2010 managed local accounts:

And the same in the Services of our machine:

Last, if now you use the SPS_FARM SharePoint 2010 managed local account to sign in to the Central Administration:

You will notice that you are not connected as SPS_Farm, but as System Account.

This account is a Farm administraor account used ONLY to administrate the Farm using the Central Administration Web site. As it is not a local administrator of the server it cannot be used to run the SharePoint 2010 Configurqtion wizard, neither the obsolete stsadm or psconfig tools, nor the SharePoint 2010 management shell. And there are operations that are no more available from the central administration web site when you are logged in with this account, as "Manage Services on Server".

10.3 Creating your first Site Collection for SharePoint 2010

From the Central Administration Home Page, click on "Create site collections" in order to proceed to the creation of your first SharePoint 2010 Site Collection.

Then, click the "Create site collections" link under the "Site Collections" section. You are taken to the "Create Site Collection" page.
I have personally chosen to create a team site called "SharePoint 2010" team site"

When launching the creation, you are prompted the changes are processed

then prompted on that the site was created successfully.

When clicking on this site link, you can display your first SharePoint 2010 site.

Well done !

As it would be interesting to have a way to send and receive e-mails inside our development environement you can continue by doing this other tutorial:

Installing and configuring SMTP and POP3 e-mail for SharePoint 2010

And if you plan to migrate to a SharePoint 2010 you can take a look at this post:

Migrating to SharePoint 2010

Last, here are some posts to start customizing SharePoint 2010:

Customizing and branding the wiki pages for a SharePoint 2010 Team Site

The following is the previous version of this post that was describing the installation process for the previous Beta version. I let it as an archive :

Installing SharePoint Server 2010 Beta on Windows 2008 Server R2

Updated 2010 May 18th
Concern of Services on Server installation with Windows 2008 Server R2.

I have read here and there that SharePoint Services installation does not work for Windows 2008 Server R2. I encountered this problem once for an installation but it actually does work.
I have updated this post with a screen shot that shows what you have to see in order to check that all services are actually properly installed.

see :
8.4 Running the SharePoint Products Configuration Wizard

Updated November 23rd
Warning for the hotfix for the token authentication in WCF (kb971831)
see :
7.6 hotfix for the token authentication in WCF

1 - Introduction

For those who have the chance to be allowed to download the SharePoint 2010 Beta because they benefit of an MSDN subscription or because they are employed by a company that is a Microsoft partner, here is a way to install the Beta version of SharePoint 2010 in order to test it.
As usual I will do my best to supply a step by step tutorial as detailed as possible which demonstrates how to install 2010 SharePoint Bêta on Windows server 2008 R2.

- Environment for this SharePoint 2010 installation:

The environment I propose to mount in this tutorial is a development environment that uses a SharePoint 2010 Beta Farm installation on a single computer using an unique local administrator account.

The SharePoint 2010 content databases will run on a SQLServer 2008 Standard Edition Database Engine.

I personally have not a MSDN subscription to date (but maybe have it soon) but my company is a Microsoft partner, so I had the chance to have the Beta version of SharePoint but for the OS, I chose to take advantage of testing the new version of SharePoint by testing in the same time the Windows 2008 Server R2 OS because Microsoft provides presently an 180 days evaluation version of it.

As you certainly know, SharePoint 2010 requires a 64 bits OS to run.
Therefore, I have chosen to create the Virtual Machine with VMware Workstation 6.5.3 because it is to date the only way of making run an 64 bit OS guest on a 32 bits OS host.

I will check if it is possible to mount an image with the free VMware Player product in order this tutorial do not require any purchase for a developer that has the benefits of the SharePoint Beta download. If it is possible, I will publish about it later.

Updated November 23rd [...

I have verified that you can actually also create a Virtual Machine running Windows 2008 Server R2 64 bits on a 32 bits host by using the free version of VMware:

VMware player 3.0.

You can download this software after registration at:

http://downloads.vmware.com/d/info/desktop_downloads/vmware_player/3_0

...]

Last, if you want to install SharePoint 2010 using Domain Accounts, you can visit the post of Jeremy Thake, very useful with treeview menu listing all the operations to be performed:

Install SharePoint 2010 Public Beta on Standalone Windows Server 2008

2 Creating the Virtual Machine

2.1 Download Windows Server 2008 R2 Evaluation

Windows Server 2008 R2 is available in 64-bit (x64) only.

You have to register to obtain it.

Open VMWare and Select "New Virtual Machine"

The new virtual machine wizard is opening

Click OK to the warning message

Choose your Virtual machine name and location.

On this screen let the default values

The Wizard summarize your settings but you can still change some by clicking "Customize Hardware...". Especially the RAM allocated to the Virtual Machine.

When you click "Finish", the installation begins by loading the files.

The Easy install will install the OS automatically and in my case it did it in approximately 30 minutes!

Then you can access to your new server. You will see the "Initial Configuration tasks".

If you want to open this windows manually run this command:

C:\Windows\System32\Oobe.exe

3 Configuring the server - Standard Configuration Operations

3.1 Hardware Acceleration

In order to accelerate your Virtual Machine you have to perform the following operations :
Right click your desktop and choose "Screen resolution".

Then, click
Troubleshoot tab
Change Settings button

You will access to the "Display Adapter Troubleshooter" dialog.
Set the cursor to the Full position.

3.2 Windows Activating

Go back to the "Initial Configuration tasks" windows and we are going to go through the standard configuration operations easily because the windows lits them.

Be sure the Virtual Machine has an Internet Access.

We have to activate Windows in order to take advantage of the 180 days of the evaluation process.
Click on the "Activate Windows" link.

Do not look for any product key, as said before, you do not need any, just click next.

The activation will be done automatically through Internet. You will notice then the activation number and the number of days remaining on the bottom right corner of the desktop.

3.3 Changing Computer Name

Now, click the "Provide computer name and domain" link,then set your new Virtual machine name.

3.4 Downloading Updates

Click the "Download and install updates link" then turn on automatic updates, and proceed to the latest updates installation.

Then restart the Virtual machine.

3.5 Disabling Internet explorer Enhanced Security

To disable Enhanced Security Configuration to specific users by using a computer running Windows Server 2008

Click Start, point to Administrative Tools, and then click Server Manager.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
Under Security Summary, click Configure IE ESC.
Under Administrators, click On (Recommended) or Off, depending on your desired configuration.
Under Users, click On (Recommended) or Off, depending on your desired configuration.
Click OK.
Restart Internet Explorer to apply Enhanced Security Configuration.

4 Configuring the server - Configuration Operations for SharePoint (MOSS 2007 or SharePoint 2010)

4.1 Adding Server Roles and Roles Services - Application Server - Web Server

On the Initial configuration task windows, click "Add Roles"
The "Add Roles" Wizard is opening.
Check the check box for Application Server.
The wizard opens a modal dialog for the Required Features

Just click the "Add Required Features" button.
You are taken to and intermediate dialog. Click "Next" to go to the "Role Services" dialogs.
Click "Next"

On the "Role Services" dialog, select the followings :
.Net Framework 3.5.1
Web Server (IIS) Support
TCP Port Sharing
HTTP Activation
TCP Activation
Named Pipes Activation

Then Click "Next"
You are taken to an the intermediate page for the Web Server (IIS) Role

Click "Next"
The Select Role Services for Web Server (IIS) Role is displaying, but just let the default options.

Click "Next" to access the confirmation dialog

Then click "Install" and the Roles and Features are being installed

Check the "Installation Result" dialog and close it.

5 Installing SQL Server 2008

For these operations I let you consult one of my previous post that explains the same for Windows 2003 Server. The operations are exactly the same.

Integrating Reporting Services 2008 with SharePoint 2007 Step 1 - SQL Server 2008 Installation

6 Downlaoding the Microsoft SharePoint Server 2010 Beta

Go to this page to download the Microsoft SharePoint Server 2010 Beta. You have to register to access to the download.

Download the Microsoft SharePoint Server 2010 Beta

You will notice that a link is available toward the

SharePoint Server 2010 system requirements

I chose the Microsoft SharePoint Server for Internet Sites Enterprise 2010 Beta

The next section will detail the required things to do in order to be compliant with these requirements. As we install SharePoint on Windows 2008 Server R2 and because we have run the latest updates, most of the required add in will be useless.

7 Configuring the server - Configuration Operations for SharePoint 2010 Beta 1

7.1 Downloading and installing SQL Server 2008 SP1

First, we have to update the previously installed SQL Server with the SP1 downlodable at :

SQL Server 2008 Service Pack 1

Do not forget to choose the x64 package

Here is the package after the download

and the first installation screenshot

7.2 Downloading and installing Cumulative update package 2 for SQL Server 2008 Service Pack 1

Then, we have to install the Cumulative update package 2 for SQL Server 2008 Service Pack 1

Cumulative update package 2 for SQL Server 2008 Service Pack 1

Follow the regsitration process. You will be provided an auto extractable package that needs a password and the appropriate password.

Here is the screenshot after all the process

and the first installation screenshot

7.3 Downloading and installing SQL Server 2008 Analysis Services ADODM.NET

For ending with the products related to SQLServer 2008 download and install the SQL Server 2008 Analysis Services ADODM.NET. Here is the direct link to the download:

ADOMD.NET

Here is the screenshot after the download.

And the first screenshot

7.4 Downloading and installing Geneva framework Runtime

This is useful even before launching the SharePoint prerequisites installation.

Geneva Framework Runtine

Here is the screenshot after the download.

And the first screenshot

7.5 Downloading and installing Microsoft Sync Framework Runtime v1.0 (x64)

Microsoft Sync Framework Runtime v1.0 (x64)

Here is the screenshot after the download.

And the first screenshot

7.6 hotfix for the token authentication in WCF

Regarding the update (KB971831),

hotfix that provides a method to support the token authentication without transport security or message encryption in WCF

it seems that the link supplied by MSDN and by the page "Determine hardware and software requirements (SharePoint Server 2010)" are not leading to the correct update for the R2 version of the OS.

As referenced by Jeremy Thake in his post, I think the good update is to find at:

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806

Its name: Windows6.1-KB976462-x64

I performed the installation today and it ran perfectly well.

You can find the complete explanation regarding this update on the SharePoint Team Blog:

Installation notice for the SharePoint Server Public Beta on Microsoft Windows Server 2008 R2 and Microsoft Windows 7

8 Microsoft SharePoint Server for Internet Sites Enterprise 2010 Beta Installation

8.1 Installing the SharePoint Prerequisites

Double click the installation package to launch the installation of Microsoft SharePoint Server for Internet Sites Enterprise 2010 Beta

The SharePoint 2010 installation Wizard is opening

Accept the licence agreement

The prerequisites are being installed

You should obtain this screen if you followed the operations previously described in this post.

8.2 Installing the SharePoint Files

Back to the SharePoint 2010 Installation wizard, click the "Install SharePoint Server" link. The launched wizard requires the product key.

Then, accept the terms of the licence agreement.

Choose the complete installation

While SharePoint is being installed, notice that a 14 repository is now created where we had the 12 for the 2007 version.

The wpressources repository is created beside the 14.

When the installation of the SharePoint files is finished you are asked to continue with the SharePoint Products Configuration Wizard.

Fortunately there is a workaround to succeed in obtaining a Farm environment using local accounts as we used to have in the previous version that I have found in this post:

Single Server Complete Install of SharePoint 2010 using local accounts

8.3 Using SharePoint 2010 Management Shell to create the SharePoint 2010 Configuration databases

Open the SharePoint 2010 Management Shell.

Type the following command

New-SPConfigurationDatabase

run the command by pressing the Carriage Return Key

The Shell willl ask you for:
The database name --> choose any name, for example SharePoint_Config
The database Server name --> type the name of your Virtual Machine in my case VMDEV-007

You will be then prompt for the system account credential. In our case to go fast and not start explaining the "least privileges administration policy" just type the administrator login and password the which you are logged with.

Then you are asked for a passphrase. You can use P@ssw0rd that matches the security policies required.
(This passphrase will be asked when you will add a new server to the SharePoint Farm)

3 web services has been created in IIS with 3 distinct application pools for each. That is a new feature of SharePoint 2010.

8.4 Running the SharePoint Products Configuration Wizard

This time you can open the SharePoint Products Configuration Wizard.

Let the option "Do not disconnect from this server farm" checked.

Let the default NTLM value for the "Authentication provider", Kerberos requires network configuration we cannot perform in the current environment anyway.

The wizard, then, summarize your choices.

Then the 9 main configuration operations are performed.

Finally, the "configuration Successful" dialog summarizes your configuration again and informs you that the central Administration of SharePoint 2010 will be launched when you close it.

When you click "Finish" to close the wizard, the Central Administration Site is opening, and you are prompted for credentials

Then you are asked to sign up to User Experience Improvement Program.

Another page let you choose between configuring your farm yourself or by using a wizard.

When this choice is made, you display for the first time the brand new Welcome Page of SharePoint 2010 Central Administration.

You should see this screen that confirms that SharePoint Services installation has completed successfully.

9 Creating your first site in Microsoft SharePoint Server for Internet Sites Enterprise 2010

9.1 Creating your first Web Application for SharePoint 2010

On the default page of the SharePoint 2010 Central Administration, click the "Manage Web Application" link in the "Application Management" section

On the "Manage Web Application" page click the "New" menu entry then click "New Web Application"

You are then prompted the changes are processed

and finally that the SharePoint 2010 Web Application is created.

Click "OK" to close the wizard and to be taken back to the Web Application Management Page where you can see the new SharePoint 2010 Web Application.

9.2 Creating your first Site Collection for SharePoint 2010

From the Web Application Management Page click the "Application Management" link in the left menu in order to proceed to the creation of your first SharePoint 2010 Site Collection.

When launching the creation, you are prompted the changes are processed

then prompted on that the site was created successfully.

When clicking on this site link, you can display your first SharePoint 2010 site.

Free EBook SharePoint Admins Survival Guide

2012-06-28T22:50:00.005-07:00

I am not sure if but I do not think I am unusual in the way I write blog posts, but the way I use the blog is if I find or am told about a problem once I solve it I blog how I did it, this then becomes mine and others knowledge base for SharePoint problems. So I thought I would gather the how to’s and other SharePoint information that I have published throughout 2010 into one EBook and make this available for others to download.

I hope you find this EBook useful these articles have certainly helped me this year and who knows this may become an annual publication.

Download Here

Hardware and software requirements for SharePoint 2010

2012-06-28T22:41:00.003-07:00

Over the last few weeks we have completed quite a few installs of SharePoint 2010 and one of the questions we get asked time and time again is what is required to run SharePoint 2010, so I thought this post I would write down exactly what is needed so I can point customers to this blog post and they would then have a reference chart of what is needed in their environment.

Hardware

SharePoint Server
Processor	64 Bit 4 Cores
Ram	8GB for production environment 16GB if you can
Hard Drive Space	80GB

SQL Server
Processor	64 Bit 4 Cores
Ram	8GB for production environment 16GB if you can
Hard Drive Space	80GB for System Drive 200GB for Data Drive

Software

SQL Server
Microsoft SQL Server 2005	64 Bit Edition with Service Pack 3
Microsoft SQL Server 2008	64 Bit Edition With Service Pack 1 and Cumulative Update 2
Microsoft SQL Server 2008 R2	No Patching Required

Windows Server

64 Bit Version of Windows Server 2008 Standard, Enterprise, Data Center or Web Server editions with Service Pack 2

Windows Server 2008 R2 Standard, Enterprise, Data Center or web Server editions

I do hope this simple post helps in your decision on SharePoint 2010.

Get Online Access to 600 Microsoft Press books for $22.99

2012-06-28T05:58:00.001-07:00

Get online access to 600 Microsoft Press books for $22.99. Details here.Its a online version alone and can download the chapters in the book based on tokens.

It includes around 34 Microsoft press books available on SharePoint topic.

SharePoint 2007 license key

2012-06-28T04:20:00.001-07:00

I am constantly looking these up so I thought I would stick them in my blog so that I can find them quickly.

SharePoint Server Standard Trial: XJMKW-8T7PR-76XT6-RTC8G-VVWCQ
SharePoint Server Enterprise Trial: F2JBW-4PDJC-HKXTJ-YCKRP-T2J9D

Display Item Attachments in SharePoint List View

2012-06-28T01:58:00.003-07:00

It is very easy to display list item attachments in List View and also manipulate the display of attachment, like if attachment is image, we can display image not just a link.

1. Open List View in SharePoint Desinger

2. Add new column titled "Attachments".

3. Select TD tag of New column.

4. Replace selected code with below code.

XSLT CODE

<xsl:element name="SharePoint:AttachmentsField">

<xsl:attribute name="runat">server</xsl:attribute>

<xsl:attribute name="FieldName">Attachments</xsl:attribute>

<xsl:attribute name="ControlMode">Display</xsl:attribute>

<xsl:attribute name="Visible">true</xsl:attribute>

<xsl:attribute name="ItemId">

<xsl:value-of select="@ID"/>

</xsl:attribute>

</xsl:element>

</td>

5. View with Attachments

Application Pages Vs Site Pages Vs Custom aspx Pages

2012-06-27T22:05:00.001-07:00

Definition:

Application Pages : An application page is deployed once per Web server and cannot be customized on a site-by-site basis.

Site Pages : These are pages that make up the site interface and are specific to one site or site collection.

Custom aspx Pages : These are the pages that are added via feature and\or solution package for a specific purpose or function.

Developers usually deploy them in Layouts folder.

Storage:

Application Pages : They stay in 12 hive folder structure, mostly under layouts folder and aare

used by all the sites and site collections for that server.

Site Pages : They mostly get stored in the content database of the site collection.

Custom aspx Pages : If deployed in Layouts folder the remain uncustomized thus do not get stored in the Content database.

Code Behind :

Application Pages : They do support code behind and inline scripts.

Site Pages : They do not support code behinds. We can only add WebPart zones to the site pages.

Custom aspx Page : They can have a code behind and inline scripts. The code behind file is not deployed though.

Look and Feel :

Application Pages : They do not inherit websites current master page. They will always inherit from application.master.

Site Pages : They inherit the custom look and feel of the site.

Cutsom aspx Pages : They do inherit the Look and feel of the site they are deployed in. You will have to specify the url of the Custom master page while deploying them.

Backup and Restore SharePoint site collection from one Farm to another Farm using STSADM commands

2012-06-27T06:36:00.002-07:00

Scenario: I have server called “ABC” where there is site collection called http://abc.com and I want to backup this site collection and restore it to new SharePoint farm “XYZ” http://xyz.com

Source Server:
Server Name: ABC
Site Collection URL: http://abc.com
Site Owner: ABC/administrator
Take backup using following command:
STSADM.EXE –o backup –URL http://abc.com -filename “backup_abc.bak” –overwrite
Help URL for backup: http://technet.microsoft.com/en-us/library/cc263441.aspx
Now to restore it to destination SharePoint farm

Destination Server:
Server Name: XYZ
Site Collection URL: http://xyz.com
Site Owner: XYZ/administrator
Create blank Web Application from Central Administration
Now restore using STSADM command
STSADM.EXE –o restore –URL http://xyz.com -filename “backup_abc.bak” –restoremethod New –newdatabaseserver “DATABASE_SERVER_NAME”
Change the site collection owner of this newly restored site
More details for restore is here
http://technet.microsoft.com/en-us/library/cc262087.aspx

Hope this will help you, let us know your comments on it!!!!!!!!!!!

SharePoint 2010 Windows PowerShell Commands

2012-06-27T06:11:00.003-07:00

To Open the Windows PowerShell Session :

1. On the Start menu, click All Programs.

2. Click Microsoft SharePoint 2010 Products.

3. Click SharePoint 2010 Management Shell

Note : You should have SharePoint_Shell_Access role on the configuration database and you should be a member of the WSS_ADMIN_WPG local group on the computer where SharePoint Server 2010 is installed.

Some of the Common Commands and Operations are:

Create Web Application Variable

$webapp = Get-SPWebApplication "http://WebapplicationUrl"

Create SharePoint Site Variable (Instance of SPSite)

$siteurl = "http://MySharePointSite"

$Oursite=new-object Microsoft.SharePoint.SPSite($siteurl)

Here we have created a variable Oursite, which contains an instance of type SPSite. Now you can use it to display all webs in the site collection.

$Oursite.AllWebs more // List all Webs in the Site

Create Service Application Variable

$spapp = Get-SPServiceApplication -Name "ServiceApplicationDisplayName"

Create a Webapplication:

New -SPWebApplication -ApplicationPoolName <Name of the application pool> -Name <Name of the new Web application> [ -Port <Port on which the Web application can be accessed>] [-HostHeader <Valid URL assigned to the Web application that must correlate to the alternate access mapping configuration>] [-URL <Load-balanced URL for the Web application>][ -ApplicationPoolAccount <User account that this application pool will run as>]

Delete WebApplication

Remove-SPWebApplication –identity -URL <http://sitename> -Confirm

Create\Delete a Site Collection:

Create a Site collection:

Get-SPWebTemplate

$template = Get-SPWebTemplate "STS#0"

New-SPSite –Url "<URL for the new site collection>" –OwnerAlias "<domain\user>" –Template $template

Here $template is a Variable to store the type of template we want to use while creating a site collection.

Delete a Site Collection:

Remove-SPSite –Identity <URL> –GradualDelete

Here <URL > is a site Collection Url.

Back\Restore a content database

To Backup :

Backup -SPFarm -Directory <Backup folder> -BackupMethod -Item <Content database name> [-Verbose]

Backup folder - is a folder to save your backup.

BackupMethod – Can Specify between Full or Differential.

To Restore:

Restore -SPFarm -Directory <Backup folder> -RestoreMethod Overwrite -Item <Content database name> [-BackupId] [-Verbose]

If you don’t know the BackupID you can display all the backups using the below command and get the GUID of the Backup.

Get-SPBackupHistory -Directory <Backup folder>

You can check all the Backup-Restore Operations Here

Deploy WebPart Soluiton Package

Install -SPWebPartPack -LiteralPath "PathToCABorwspFile" -Name "NameOFWebPart"

PathToCABorwspFile- is the full path to the CAB file that is being deployed.

NameOFWebPart- is the name of the Web Part that is being deployed.

Install Activate and Deactivate Feature using Windows Powershell

Install Feature :

$MyFeatureId = $(Get -SPFeature -limit all where {$_.displayname -eq "myfeatureName"}).Id

Install -SPFeature $MyFeatureId

Activate\Enable Feature :

$singleSiteCollection = Get -SPSite -Identity http://MySingleSiteCollectionURL

Enable -SPFeature $MyFeatureId -Url $singleSiteCollection.URL

Deactivate\Disable Feature :

$singleSiteCollection = Get-SPSite -Identity http://MySingleSiteCollectionURL

Disable -SPFeature $MyFeatureId -Url $singleSiteCollection.URL

Site Collection Commands
Create Site Collection :

Get-SPWebTemplate
$template = Get-SPWebTemplate "STS#0"
New-SPSite -Url "" -OwnerAlias "" -Template $template

Delete Site Collection :

Remove-SPSite -Identity "URL of site Collection" -GradualDelete

Change Site collection Quotas :
Set-SPSite -Identity "SiteCollection Url" -MaxSize Quota

Add site Collection Administrators :

Set-SPSite -Identity "" -SecondaryOwnerAlias ""

Lock or unlock a site collection :

Set-SPSite -Identity "Site Collection Url" -LockState ""

is one of the following vales :

# Unlock: To unlock the site collection and make it available to users.

# NoAdditions: To prevent users from adding new content to the site collection. Updates and deletions are still allowed.

# ReadOnly: To prevent users from adding, updating, or deleting content.

# NoAccess: To prevent access to content completely. Users who attempt to access the site receive an access-denied message.

Create a site :

New-SPSite "http://sitecollection/sites/Subsite -OwnerAlias "DOMAIN\UserName" –Language 1033

Command TO List all the PowerShell Commands

Get-Command –PSSnapin “Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell” format-table name > C:\SP2010_PowerShell_Commands.txt

Deploy sharepoint 2010 solutions using Powershell

2012-06-27T05:35:00.003-07:00

Here are the commands for your Powershell script to remove and re-add a solution package in SharePoint 2010

To Open the Windows PowerShell Session :

1. On the Start menu, click All Programs.

2. Click Microsoft SharePoint 2010 Products.

3. Click SharePoint 2010 Management Shell

Note : You should have SharePoint_Shell_Access role on the configuration database and you should be a member of the WSS_ADMIN_WPG local group on the computer where SharePoint Server 2010 is installed.

Now, type in the following comamnds ( Note that the first two are needed only if the Solution already exists and you need to retract it before adding a new one.

Uninstall-SPSolution -identity {name of wsp file} -allwebapplications

remove-spsolution -identity {name of wsp file} -force

add-spsolution -literalpath C:\{FULL file system location\name of wsp file}

install-spsolution -identity {name of wsp file} -webapplication http://{URL of SharePoint site to deploy to} -GACDeployment -force

Add,Update,Delete List items using powershell sharepoint 2010

2012-06-27T05:29:00.002-07:00

A simple example of a powershell script to Add, Update, Delete items in a list in SharePoint 2010.

Add List Item:

$spAssignment = Start-SPAssignment
$mylist = (Get-SPWeb -identity http://SP -AssignmentCollection $spAssignment).Lists["listName"]
$newItem = $mylist .Items.Add()
$newItem["Title"] = “Added by Powershell”
$newItem["description"] = “My PowerShell Magic”
$newItem.Update()
Stop-SPAssignment $spAssignment

In the example we use the Start-SPAssignment and Stop-SPAssignment cmdlets to make sure that the objects are disposed correctly. Also note that we assign Get-SPWeb to the assignment. We then use the Add() method to create a new item in SharePoint 2010.

Update List Item:

$SPAssignment = Start-SPAssignment
$SPWeb = Get-SPWeb http://SP -AssignmentCollection $spAssignment

Next step is to get the list:
$SPList = $SPWeb.Lists["Announcements"]

When we have located the list we can retrieve the item. The quickest way is to use the GetItemByID() method:
$SPItem = $SPList.GetItemById("1")

The example above requires that you know the ID of the item. If you don’t know the items ID you can use the Where-Object cmdlet instead:

$SPItem = $SPList.Items | Where { $_["Title"] -eq "New Announcement" }
When you’ve retrieved the item you can modify the item information.

$SPItem[“Title”] = "MyTitle"
$SPItem[“Body”] = "MyBody"

After modifying an item you have to call the Update() method to set the changes.
$SPItem.Update()

When you’re done, use the Stop-SPAssignment cmdlet to dispose the SPWeb object. Stop-SPAssignment $SPAssignment

Delete List Item:

The example below will count the items and loop down, read the name of the item, and if the item contains a 3, then it will delete that item.

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$site = new-object Microsoft.SharePoint.SPSite("http://test.tomdaly.com") # is a legit url
$relweburl = '/Docs"
$web = $site.openweb($relweburl)
$list=$web.Lists["testList"] $listItems = $list.Items
$listItemsTotal = $listItems.Count

for ($x=$listItemsTotal-1;$x -ge 0; $x--)
{
if($listItems[$x].name.Contains("3"))
{
Write-Host("DELETED: " + $listItems[$x].name)
$listItems[$x].Delete()
}
}