English

I think you may already know Set-SPServiceApplicationPool. This command can be used to modify apppool account for service application – but it doesn’t work for Web Application. I am looking for Set-SPWebApplicationPool but I can not find it anywhere.

So here is the PowerShell script

param([string] $url, [string] $account)

$SPWebApp = Get-SPWebApplication $url

$SPManagedAccount = Get-SPManagedAccount –Identity $account

$SPWebApp.ApplicationPool.ManagedAccount = $SPManagedAccount

$SPWebApp.ApplicationPool.Update()

English

Today I find a strange behaviour, my Office 2010 can not browse to the SharePoint 2010 document library. In short, I can not save my document directly to SharePoint 2010.  Office 2010 provide Save and Send functionality, which should give me functionality to save directly to SharePoint 2010 as what it does in previous version; so what could be the problem?

Saving to SharePoint 2010 document library requires WebDAV functionality via Web Client service. Unfortunatelly the Web Client service is not enabled by default, and it is part of Desktop Experience features.  So, how can we enable it using PowerShell?

# Open PowerShell console and then type

import-module servermanager
Add-WindowsFeature Desktop-Experience

English

SharePoint team just released SharePoint 2010 Administration Toolkit V1, which contains :

- User Profile Replication Engine 2010
- Security Configuration Manifest
- Content Management Interoperatibility Services Connector
- Load Testing Kit

More information about this toolkit can be found here:
http://blogs.msdn.com/b/sharepoint/archive/2010/07/15/announcing-the-release-of-the-sharepoint-2010-administration-toolkit-v1.aspx

English

In the previous version, creating cascading lookup field was becoming a problem. At least 2 or more technique have been proposed for example using Javascript , or custom field. In this video cast, I will continue the InfoPath and SharePoint 2010 productivity series by implementing the cascading lookup field using InfoPath. In this video, I will extend Members list with City – Province – Country , information. Province and Country are cascading lookup field.

English

I have found 2 good articles on how work with XML in PowerShell.

http://www.pluralsight-training.net/community/blogs/dan/archive/2006/11/25/42506.aspx
http://www.pluralsight-training.net/community/blogs/dan/archive/2006/11/28/43561.aspx

Don’t be surprised that you will find % notation that represent ForEach-Object.

English

Imagine a business scenario where we have a lookup field in our list. The reference list contains items Title and their status.  Previously it always difficult to create filtered lookup field with minimal development task. But now, we can use InfoPath 2010 to achieve that functionality.

Part III , InfoPath 2010 and SharePoint 2010 Productivity series webcast shows how to create filtered lookup field.  There are two lists in the scenario “Books” and “Members” list.  The Books list contains list of books Title, Author and Status. There are 2 status of books, “Available” , “In-Used” and “Missing”.

“Members” list has Books  , lookup field – which should show only the “Available” books.

English:

Imagine that user wants to build Book lending application using SharePoint 2010. Initially they must register the book description , and sub-sequently they will update book lending status.  On the registration, the status should not be available in the form – however on lending event , they have to modify the status of the book.
Following webcast shows how to use InfoPath Designer 2010 to customize New/Edit/View form in SharePoint List to build that application.

English

Whether you are geek SharePoint 2007 who are migrating to SharePoint 2010  – or freshmen who are starting to develop application for SharePoint 2010; Microsoft Patterns and Practices is always good resources to learn. In the SharePoint 2007 era, Microsoft release paterns and practices quite long time after the release of SharePoint 2007.

But, good news – MS just  released MS Paterns and Practices to develop application for SharePoint 2010; only few weeks after the release of SharePoint 2010.

Grab it here:
http://msdn.microsoft.com/en-us/library/dd203468.aspx
and codeplex here:
http://spg.codeplex.com/

Faboulous 40 have become a good showcase for us for SharePoint 2007 implementation.  I personaly deployed it in some of my clients – and it is a good start to play with SharePoint 2007 business implementation.  They are not perfect tough – but they create conversation on the functionalities and enhancements.

So far, Microsoft has not release Fab40 for SharePoint 2010 – but we can find un-official Fab40 by Khalil here : http://techsolutions.net/Blog/tabid/65/EntryId/17/Fab-40-Templates-for-MOSS-2010.aspx

English

One of new feature in SharePoint 2010 is Sandboxed Solution. The ideas is to create solution and deploying them in a way that you can trust will not damage or change SharePoint farm. (http://msdn.microsoft.com/en-us/magazine/ee335711.aspx)

Sandboxed Solution is aimed for isolation between one solution to another; which implies that you can not include anything inside the hive folder. If you try to include TemplateFile, Layouts or Images in package, VS2010 will raise an error stating “The deployment type …… is not compatible with a Package in a Sandboxed Solution”.  And it means you have to think about the solution architecture again and refine the rules.

For example, you may consider custom document library to store the images for your solution, etc.

However, sometimes we need to get rid from sandboxed solution. Then we need to change the project type into non-sandboxed solution. To change project type to non-sandboxed solution,

1. Click on project property
2. Set Sandboxed Solution = False.

Now continue your work.