Turhal Temizer 'in Blogu

8 Haziran 2011 Yazgeliştir Zirvesi

2011-05-29T23:58:00.001+03:00

Yazgeliştir etkinliklerinden Yazgeliştir Zirve'nin ikincisi 8 Haziran Çarşamba günü Microsoft İstanbul ofisinde gerçekleştirilecek. Etkinlikte Microsoft Regional Director (RD), Microsoft Most Valuable Professional (MVP) ve Yazgeliştir editörleri konuşmacı olacak. Microsoft’un çeşitli yazılım geliştirme ürün ve araçları ile ilgili seminerlere katılabilir, Windows Phone 7, Windows Embedded, Windows Azure gibi tüm dünyanın yakından takip ettiği konuları ve son bir sene içinde Microsoft teknolojilerinde olan yenilikleri konunun uzmanlarından öğrenebilirsiniz. Etkinlikte aynı zamanda Yazgeliştir editörleri ile bir araya gelip kendilerine danışmak istediğiniz konularda sorular sorabilirsiniz. Etkinlik ile ilgili detaylı bilgiye zirve.yazgelistir.com adresinden ulaşabilirsiniz.

Zirveye 1 Haziran'da kayıt olabilirsiniz.

Yazilim Gelistiriciler Icin Yeni Trendler–Cagri Merkezleri (Call Centers)

2011-04-20T22:07:00.000+03:00

Uzunca bir aradan sonra herkese selamlar diliyorum. Ilk olarak klavyemden kaynaklanan bir problemden oturu Turkce karakterleri kullanamayacagim. Simdiden yazimi okuyan ya da blogu gezinirken denk gelen butun herkesten ozur diliyorum.

Yaklasik 6 aydir yogun is temposu nedeniyle blog, editorluk vb. hic bir aktivite ile ilgilenme firsati bulamamistim. Aslina bakarsaniz biri bana bu tur bir soz soylediginde hic bir sekilde bir zaman bulamadiginiza pek inanmak icimden gelmiyor derdim. Evet su anda da ayni sozu soylemeye devam ediyorum. Dogrusu itiraf etmek gerekirse isten eve dondugumde bilgisayari acmak bile icimden gelmedigi icin sosyal sorumluluklarima zaman ayiramamistim. Ancak calistigim sirketimden bir yazilimci arkadas yazilarini begeniyorduk, neden devam etmiyorsunuz ki diyene kadar. Demek ki herkes icin kirpac tarzinda bu tur uyarici faktorler gerekiyormus. Uzun lafin kisasi kendi usengecligimden oturu yazi yazamadim. Ama simdi tekrardan basliyoruz.

Bildiginiz uzere yaklasik bir yil once BSH (Bosh & Siemens Ev Aletleri) firmasinda ise basladim. Burada guzel projeler yaptik ve yapmaya da devam ediyoruz. Ancak hic bilmedigim/farketmedigim ya da belkide gorupte es gectigim bir sektorunde farkina vardim. Cagri Merkezleri. Hani reklamlarda da soyledikleri gibi kol senterlar.

Peki ne yapar bu Call Center daha Turkce anlatmak gerekirse Cagri Yonetim Sistemleri. Sizin almis, temin ettiginiz bir hizmet/urun hakkinda bir sorununuz ya da bilgilenme talebiniz oldugu zaman hemen aradiginiz genellikle 444 ‘lu numaralarla hizmet veren bir birimdir. Sirketler artik ne yaparlarsa yapsinlar cok benzer urunler sunmaya basladilar. Bunlarin sonucunda da cok farkli alanlarda, kopyalanmasi daha zor dallarda hizmet sunmaya basladilar. Bunlardan en birincisi ise musteri ile direk temas kurabilen cagri merkezleridir. Iyi guzel hos. Yazilimcilar burada ne yapabilir. Ne gibi katkilari olabilir ya da saglayabilir.

Oncelikli olarak Turkiye ‘de yazilimcilarin kaderi olan bir verinin raporlanmasi isinin yerine getirilmesi gerekmektedir. Ek olarak butun sirketlerin ihtiyaci olan olmazsa olmaz sistemlerin hazirlanmasi islerinde gorev alirlar. Bunlarin disinda biraz daha teknik bilginiz yuksekse istatistiksel yaklasimlar ile bazi rakamlari tahmin etmeye calisirsiniz ( Butun sektorlerin hayalidir. Eger basarili bir uygulama yaparsaniz bu urunu yok satacaginizin hic bir suphesi yoktur. Data Minning konusuna egilmesiniz tavsiye ederim. ). SQL bilginiz ile cok rahat on plana cikarak birazdan bahsedecegimiz hazir urunler ya da benzerlerinin kullanimi konusunda rahatca adepte olabilirsiniz.

Cagri merkezinde calisacak olan bir yazilimcinin dikkat etmesi ve bilmesi gerekenler nelerdir?

Bilmesi gerekenler;

Java, C#, VB.net dillerinden birini hakim seviyede bilmesi
ASP.net, JSF, JQuery gibi web uygulamalar hazirlamaniza yarayacak teknikleri bilmeniz. Unutmadan yeri bambaska olan HTML bilmezseniz olmaz.
T-sql bilginizin 10 uzerinden en az 7 seviyesinde olmasi. SQL Server,IBM Informix DB, Oracle vb. veri tabaninlarina uyum saglayabilmeniz icin gereklidir.
Isleri cabuk cozumleyebilme yetenegi. Inanilmaz hizli bir temposu var.
Cagri alinmasi ve uzerinde islem yapilabilmesi icin kullanilan yazilimlara hakim olunabilmesi inanci (Hayatinizda hic adini duymadiniz bir sistem ya da uygulama ile karsilasabilme ihtimaliniz cok yuksek)

Dikkat edilmesi gerekenler;

Klasik olanlardan, isleri zamaninda ve hatasiz teslim etmeniz.
Calisma alanizi gelisterecek yeni fikirler ortaya atabilmeniz.
Is bilincine sahip olmaniz.

Yukarida ki tanimlara goz attigimizda aslinda cok rahat temin edilebilecek kriterler gibi gozukuyor. Evet gercekten de oyle. Eger cok girmek istediginiz bir sirket varsa ve bu sirketin IT/IS departmanlarina giremiyorsaniz Cagri Merkezi ya da diger birimlerde calismaya baslayip mukemmel isler yaparak istediginiz yerlere gelebilmeniz mumkun. Eskilerin bir sozu vardir. “Bir yerlerden baslamak gerekir.”

Kullanilan harici uygulamalarin oldugundan bahsetmistim. Bunlardan gozlemledigim kadariyla en basarilisi AVAYA ‘dir. Agent ‘in (Cagri merkezlerinde telefonda musteri ile gorusen kisilere agent denir) yapmis oldugu her islemi loglar. Sonrasinda da bunu yazilimcilara veri halinde sunar. Kendi raporlama araci vardir. Super User ‘lar icin gercekten mukemmel bir arayuz. Eger sql bilginiz varsa sizlerde cok rahat istediginiz raporlari olusturabilmeniz mumkudur. Eger yok ben kendim yazarim raporlarimi derseniz ise Informix veri tabanindan size bir ODBC baglantisi hazirlanir. Verilerinizi guzelce kullanirsiniz. gecmise yonelik 15 dakikaya kadar bilgilere ulasabilirsiniz. Yok beni 3-5 saniye sonrasi kurtarmaz anlik veri gormem gerekir derseniz de socket programming yollarina bir ilerleme icerisine girmis oluyorsunuz. Ancak ufak bir konuda sizleri bilgilendirmeliyim. Socket icin ek lisans bedelleri odeniyor.

Bu durumda temel olarak en yeni trendlerdan Cagri Yonetim Merkezlerini tanimis olduk. Eger daha detayli bilgi almak isterseniz info@turhaltemizer.com adresinden benim ile ilgili temasa gecebilirsiniz.

Sonuc olarak Turkiye de bulunan firmalara baktiginizda buyuk cogunlugu artik yabanci sermayali oldugunu gorursunuz. Tabi insan oglunun bir klasigi vardir. Kritik isler bana yakin yurumelidir. Bu mantiktan oturu bu tarz firmalarda IT departmanlarinda calisan insan sayisi azaliyor. Bu durumda ihtiyac/talep dengesinden oturu belirli kriterlerin altinda kalan arkadaslar is bulurken zorlaniyorlar. Bu sebepledir ki yeni trendlere goz atmaya ve kendinizi ispat edebileceginiz firmalarda yer almaya ozen gostermenizi tavsiye ediyorum. Unutmayin hergun yeni bir sey bulunuyor, icat ediliyor. Bu yenilikleri yakalayacagim, herseyi ogrenmeliyim derken sabit bir isinizinde olmasi gerektigini lutfen unutmayin.

Herkese mutlu ve saglıklı gunler diliyorum.

PowerShell Commands for SharePoint 2010

2010-12-19T22:08:00.000+02:00

Here are some (over 400) PowerShell™ commands for SharePoint 2010! These can be run remotely (Powershell 2.0).
Stsadm will still be functional in SharePoint 2010. Powershell is not DOS based. Its .NET based.

Windows PowerShell™ is the new command-line interface and scripting language specifically designed for system administrators that will be used for Microsoft® SharePoint® Server 2010 administration. Although both Cmd.exe and Stsadm.exe environments will be maintained for backward compatibility, SharePoint Server 2010 command-line administration will use Windows PowerShell. For practical purposes, you can view Windows PowerShell as complementing Cmd.exe in the Windows administration context and superseding Stsadm.exe for SharePoint administration. You might ask yourself, What’s so unique about Windows PowerShell? Well, unlike most command-line systems that accept and return text, Windows PowerShell supports and uses XML and objects. XML and object support is a pretty major change that brings entirely new tools and methods to greatly improve control, efficiency, and productivity for developers and administrators.

Hope you find these commands useful for the future. Be sure to bookmark this page for future reference.

SPAccessServiceApplication

Get-SPAccessServiceApplication – Gets an {Access Service} application object.

New-SPAccessServiceApplication

Set-SPAccessServiceApplication – Sets a global property for an {Access Services} application.

SPAdminJob

Start-SPAdminJob – Immediately starts any waiting administrative job on the local computer.

SPAlternateURL

Get-SPAlternateURL – Return all alternate URLs that match a given criteria.

New-SPAlternateUrl – Creates a new public or internal URL for the specified Web application zone or resource.

Remove-SPAlternateUrl – Completely deletes the specified alternate URL.

Set-SPAlternateUrl – Configures the specified alternate URL.

SPApplicationContent

Install-SPApplicationContent

SPAssignment

Start-SPAssignment – Initiates a new assignment store.

Stop-SPAssignment – Disposes of objects in the provided Assignment Collection.

SPBackupHistory

Get-SPBackupHistory

SPBlobStorageLocation

Move-SPBlobStorageLocation

SPBrowserCustomerExperienceImprovementProgram

Get-SPBrowserCustomerExperienceImprovementProgram

Set-SPBrowserCustomerExperienceImprovementProgram

SPBusinessDataCatalogAclToChildren

Copy-SPBusinessDataCatalogAclToChildren

SPBusinessDataCatalogEntity

Disable-SPBusinessDataCatalogEntity

Enable-SPBusinessDataCatalogEntity

SPBusinessDataCatalogMetadataObject

Get-SPBusinessDataCatalogMetadataObject

Grant-SPBusinessDataCatalogMetadataObject

Revoke-SPBusinessDataCatalogMetadataObject

Set-SPBusinessDataCatalogMetadataObject

SPBusinessDataCatalogModel

Export-SPBusinessDataCatalogModel

Import-SPBusinessDataCatalogModel

Remove-SPBusinessDataCatalogModel

SPBusinessDataCatalogPartition

Remove-SPBusinessDataCatalogPartition

SPBusinessDataCatalogPartitionData

Clear-SPBusinessDataCatalogPartitionData

Export-SPBusinessDataCatalogPartitionData

Import-SPBusinessDataCatalogPartitionData

SPBusinessDataCatalogServiceApplication

New-SPBusinessDataCatalogServiceApplication

Set-SPBusinessDataCatalogServiceApplication

SPBusinessDataCatalogServiceApplicationProxy

New-SPBusinessDataCatalogServiceApplicationProxy

SPBusinessDataCatalogThrottleConfig

Get-SPBusinessDataCatalogThrottleConfig

Remove-SPBusinessDataCatalogThrottleConfig

Set-SPBusinessDataCatalogThrottleConfig

SPCentralAdministration

New-SPCentralAdministration – Creates a new Central Administration Web application.

Set-SPCentralAdministration

SPCertificate

Get-SPCertificate

New-SPCertificate

Remove-SPCertificate

SPCertificateStore

Get-SPCertificateStore

SPClaimMapping

Add-SPClaimMapping

New-SPClaimMapping

Remove-SPClaimMapping

SPClaimProviderManager

Get-SPClaimProviderManager

SPClaimsObject

New-SPClaimsObject

SPClaimsPrincipal

New-SPClaimsPrincipal

SPConfigurationDatabase

Backup-SPConfigurationDatabase – Performs a configuration only backup.

Connect-SPConfigurationDatabase – Connects the computer to an existing configuration database.

Disconnect-SPConfigurationDatabase

New-SPConfigurationDatabase – Creates a new configuration database.

Remove-SPConfigurationDatabase – Permanently removes the specified configuration database.

SPContentDatabase

Check-SPContentDatabase

Dismount-SPContentDatabase

Get-SPContentDatabase

Initialize-SPContentDatabase

Mount-SPContentDatabase

New-SPContentDatabase

Remove-SPContentDatabase

Set-SPContentDatabase

Upgrade-SPContentDatabase

SPContentDeploymentJob

Get-SPContentDeploymentJob

New-SPContentDeploymentJob

Remove-SPContentDeploymentJob

Set-SPContentDeploymentJob

Start-SPContentDeploymentJob

SPContentDeploymentPath

Get-SPContentDeploymentPath

New-SPContentDeploymentPath

Remove-SPContentDeploymentPath

Set-SPContentDeploymentPath

SPCustomLayoutsPage

Get-SPCustomLayoutsPage

Set-SPCustomLayoutsPage

SPDatabase

Get-SPDatabase – Retrieves all properties of a database.

SPDataConnectionFile

Get-SPDataConnectionFile – Returns a data connection file or a collection of data connection files.

Install-SPDataConnectionFile – Installs the provided data connection file.

Set-SPDataConnectionFile – Sets properties of a data connection file.

Uninstall-SPDataConnectionFile – Removes a data connection file.

SPDataConnectionFileDependent

Get-SPDataConnectionFileDependent – Returns administrator deployed form templates on the server dependent on a Universal Data Connection (UDC).

SPDesignerSettings

Get-SPDesignerSettings

Set-SPDesignerSettings

SPDiagnosticConfig

Get-SPDiagnosticConfig

Set-SPDiagnosticConfig

SPDiagnosticsProvider

Get-SPDiagnosticsProvider

Set-SPDiagnosticsProvider

SPediscoveryHub

Set-SPediscoveryHub

SPEdiscoveryHubSearchScope

Get-SPEdiscoveryHubSearchScope

SPediscoveryHubSite

Get-SPediscoveryHubSite

SPEnterpriseSearchAdministrationComponent

Get-SPEnterpriseSearchAdministrationComponent – Returns the administration component for a shared search application.

Set-SPEnterpriseSearchAdministrationComponent – Sets properties of an administration component for a shared search application.

SPEnterpriseSearchCrawlComponent

Get-SPEnterpriseSearchCrawlComponent – Returns a crawl component for a shared search application.

New-SPEnterpriseSearchCrawlComponent – Creates a crawl component for a shared search application.

Remove-SPEnterpriseSearchCrawlComponent – Deletes a crawl component from a shared search application.

SPEnterpriseSearchCrawlContentSource

Get-SPEnterpriseSearchCrawlContentSource – Returns a crawl content source.

New-SPEnterpriseSearchCrawlContentSource – Creates a new crawl content source for a shared search application.

Remove-SPEnterpriseSearchCrawlContentSource – Deletes a specified crawl content source from a search application.

Set-SPEnterpriseSearchCrawlContentSource – Sets the properties of a crawl content source for a shared search application.

SPEnterpriseSearchCrawlCustomConnector

Get-SPEnterpriseSearchCrawlCustomConnector

New-SPEnterpriseSearchCrawlCustomConnector

Remove-SPEnterpriseSearchCrawlCustomConnector

SPEnterpriseSearchCrawlDatabase

Get-SPEnterpriseSearchCrawlDatabase – Returns a crawl store.

New-SPEnterpriseSearchCrawlDatabase – Adds a crawl store to a shared search application.

Remove-SPEnterpriseSearchCrawlDatabase – Deletes a content crawl store.

Set-SPEnterpriseSearchCrawlDatabase

SPEnterpriseSearchCrawlExtension

Get-SPEnterpriseSearchCrawlExtension – Returns the extension rule for the extension collection.

New-SPEnterpriseSearchCrawlExtension – Adds an extension rule to a shared search application.

Remove-SPEnterpriseSearchCrawlExtension – Removes a file name extension from the list of files that can be crawled.

SPEnterpriseSearchCrawlMapping

Get-SPEnterpriseSearchCrawlMapping – Returns a crawl mapping for the search application.

New-SPEnterpriseSearchCrawlMapping – Creates a crawl mapping rule for a shared search application.

Remove-SPEnterpriseSearchCrawlMapping – Deletes a crawl mapping.

SPEnterpriseSearchCrawlRule

Get-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.

New-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.

Remove-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.

Set-SPEnterpriseSearchCrawlRule – Output an CrawlRule Object.

SPEnterpriseSearchCrawlTopology

Get-SPEnterpriseSearchCrawlTopology – Returns a crawl topology.

New-SPEnterpriseSearchCrawlTopology – Adds a crawl topology to a shared search application.

Remove-SPEnterpriseSearchCrawlTopology – Deletes a crawl topology.

Set-SPEnterpriseSearchCrawlTopology – Sets the properties of a crawl topology on a shared search application.

SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition

Get-SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition

SPEnterpriseSearchExtendedConnectorProperty

Get-SPEnterpriseSearchExtendedConnectorProperty

Set-SPEnterpriseSearchExtendedConnectorProperty

SPEnterpriseSearchExtendedQueryProperty

Get-SPEnterpriseSearchExtendedQueryProperty

Set-SPEnterpriseSearchExtendedQueryProperty

SPEnterpriseSearchIndexPartition

Get-SPEnterpriseSearchIndexPartition – Returns an index partition for a query topology.

Set-SPEnterpriseSearchIndexPartition – Sets properties of an index partition for a query topology.

SPEnterpriseSearchLanguageResourcePhrase

Get-SPEnterpriseSearchLanguageResourcePhrase – Returns a language resource phrase.

New-SPEnterpriseSearchLanguageResourcePhrase – Adds a language resource phrase to a shared search application.

Remove-SPEnterpriseSearchLanguageResourcePhrase – Deletes a language resource phrase from a shared search application.

SPEnterpriseSearchManagerService

Get-SPEnterpriseSearchManagerService – Returns the search manager service.

SPEnterpriseSearchManagerServiceInstance

Get-SPEnterpriseSearchManagerServiceInstance – Returns the service manager service instance.

Start-SPEnterpriseSearchManagerServiceInstance – Starts an instance of a search manager service.

Stop-SPEnterpriseSearchManagerServiceInstance – Stops an instance of a search manager service.

SPEnterpriseSearchManagerServiceProxy

Get-SPEnterpriseSearchManagerServiceProxy – Returns the search manager service proxy.

SPEnterpriseSearchMetadataCategory

Get-SPEnterpriseSearchMetadataCategory – Returns a crawled property category.

New-SPEnterpriseSearchMetadataCategory – Adds a crawled property category to a shared search application.

Remove-SPEnterpriseSearchMetadataCategory – Deletes a crawled property category.

Set-SPEnterpriseSearchMetadataCategory – Sets properties of a crawled property category for a shared search application.

SPEnterpriseSearchMetadataCrawledProperty

Get-SPEnterpriseSearchMetadataCrawledProperty – Returns a crawled property.

New-SPEnterpriseSearchMetadataCrawledProperty – Adds a crawled property category to a shared search application.

Set-SPEnterpriseSearchMetadataCrawledProperty – Sets the properties of a metadata crawled property for a shared search application.

SPEnterpriseSearchMetadataManagedProperty

Get-SPEnterpriseSearchMetadataManagedProperty – Returns a managed property.

New-SPEnterpriseSearchMetadataManagedProperty – Adds a managed property to a shared search application.

Remove-SPEnterpriseSearchMetadataManagedProperty – Deletes a metadata managed property.

Set-SPEnterpriseSearchMetadataManagedProperty – Sets the properties of a metadata managed property.

SPEnterpriseSearchMetadataMapping

Get-SPEnterpriseSearchMetadataMapping – Returns the current state of a managed property mapping.

New-SPEnterpriseSearchMetadataMapping – Adds a managed property mapping to a shared search application.

Remove-SPEnterpriseSearchMetadataMapping – Deletes a metadata mapping from a managed property.

Set-SPEnterpriseSearchMetadataMapping – Sets the properties of a managed property mapping for a shared search application.

SPEnterpriseSearchPropertyDatabase

Get-SPEnterpriseSearchPropertyDatabase – Returns a property store.

New-SPEnterpriseSearchPropertyDatabase – Adds a new property store to a shared search application.

Remove-SPEnterpriseSearchPropertyDatabase – Deletes a property store.

Set-SPEnterpriseSearchPropertyDatabase

SPEnterpriseSearchQueryAuthority

Get-SPEnterpriseSearchQueryAuthority – Returns an authoritative page.

New-SPEnterpriseSearchQueryAuthority – Adds an authoritative page to a shared search application.

Remove-SPEnterpriseSearchQueryAuthority – Deletes an authoritative page.

Set-SPEnterpriseSearchQueryAuthority – Sets the properties of an authoritative page for a shared search application.

SPEnterpriseSearchQueryComponent

Get-SPEnterpriseSearchQueryComponent – Returns a query component.

New-SPEnterpriseSearchQueryComponent – Adds a query component to a query topology.

Remove-SPEnterpriseSearchQueryComponent – Deletes a query component.

Restart-SPEnterpriseSearchQueryComponent

Set-SPEnterpriseSearchQueryComponent

SPEnterpriseSearchQueryDemoted

Get-SPEnterpriseSearchQueryDemoted – Returns a demoted site rule.

New-SPEnterpriseSearchQueryDemoted – Adds a demoted site rule to a shared search application.

Remove-SPEnterpriseSearchQueryDemoted – Deletes a demoted site rule.

SPEnterpriseSearchQueryKeyword

Get-SPEnterpriseSearchQueryKeyword – Returns a keyword term.

New-SPEnterpriseSearchQueryKeyword – Adds a keyword term to a shared search application.

Remove-SPEnterpriseSearchQueryKeyword – Deletes a query keyword.

Set-SPEnterpriseSearchQueryKeyword – Sets the properties of a keyword term for a shared search application.

SPEnterpriseSearchQueryScope

Get-SPEnterpriseSearchQueryScope – Returns a query results scope.

New-SPEnterpriseSearchQueryScope – Adds a query results scope to a shared search application.

Remove-SPEnterpriseSearchQueryScope – Deletes a query scope.

Set-SPEnterpriseSearchQueryScope – Sets the properties of a query results scope for a shared search application.

SPEnterpriseSearchQueryScopeRule

Get-SPEnterpriseSearchQueryScopeRule – Returns a shared scope rule.

New-SPEnterpriseSearchQueryScopeRule – Adds a shared scope rule to a query scope.

Remove-SPEnterpriseSearchQueryScopeRule – Deletes query results scope rules.

Set-SPEnterpriseSearchQueryScopeRule – Sets the properties of a shared scope rule for a query scope.

SPEnterpriseSearchQuerySuggestionCandidates

Get-SPEnterpriseSearchQuerySuggestionCandidates

SPEnterpriseSearchQueryTopology

Get-SPEnterpriseSearchQueryTopology – Returns a query topology.

New-SPEnterpriseSearchQueryTopology – Adds a query topology to a shared search application.

Remove-SPEnterpriseSearchQueryTopology – Deletes a query topology.

Set-SPEnterpriseSearchQueryTopology – Sets the properties of a query topology for a shared search application.

SPEnterpriseSearchRankingModel

Get-SPEnterpriseSearchRankingModel – Returns a ranking model.

New-SPEnterpriseSearchRankingModel – Adds a ranking model to a shared search application.

Remove-SPEnterpriseSearchRankingModel – Deletes a ranking model.

Set-SPEnterpriseSearchRankingModel – Sets the properties of a ranking model for a shared search application.

SPEnterpriseSearchSecurityTrimmer

Get-SPEnterpriseSearchSecurityTrimmer – Returns a custom security trimmer.

New-SPEnterpriseSearchSecurityTrimmer – Adds a custom security trimmer to a shared search application.

Remove-SPEnterpriseSearchSecurityTrimmer – Deletes a custom security trimmer.

SPEnterpriseSearchService

Get-SPEnterpriseSearchService – Returns the search service for the farm.

Set-SPEnterpriseSearchService – Sets the properties of a search service for a farm.

SPEnterpriseSearchServiceApplication

Get-SPEnterpriseSearchServiceApplication – Returns the search service application for a farm.

New-SPEnterpriseSearchServiceApplication – Adds a search service application to a farm.

Remove-SPEnterpriseSearchServiceApplication – Deletes a search service application.

Restore-SPEnterpriseSearchServiceApplication

Set-SPEnterpriseSearchServiceApplication – Sets the properties of a search service application for a farm.

Upgrade-SPEnterpriseSearchServiceApplication

SPEnterpriseSearchServiceApplicationProxy

Get-SPEnterpriseSearchServiceApplicationProxy – Returns the search service application proxy.

New-SPEnterpriseSearchServiceApplicationProxy – Adds a site hit rule for a search application.

Remove-SPEnterpriseSearchServiceApplicationProxy – Deletes a search service application proxy.

Set-SPEnterpriseSearchServiceApplicationProxy – Sets properties of a search service application proxy.

SPEnterpriseSearchServiceInstance

Get-SPEnterpriseSearchServiceInstance – Returns the search service instance for a farm.

Set-SPEnterpriseSearchServiceInstance – Sets the properties of a search service instance.

Start-SPEnterpriseSearchServiceInstance – Starts an instance of a search service.

Stop-SPEnterpriseSearchServiceInstance – Stops an instance of a search service.

SPEnterpriseSearchSiteHitRule

Get-SPEnterpriseSearchSiteHitRule – Returns shared site hit rule.

New-SPEnterpriseSearchSiteHitRule – Output an SiteHitRule Object.

Remove-SPEnterpriseSearchSiteHitRule – Output an SiteHitRule Object.

SPEnterpriseSearchTopology

Export-SPEnterpriseSearchTopology – Saves an existing search topology.

Import-SPEnterpriseSearchTopology – Imports and activates a topology from an XML file.

SPExcelBlockedFileType

Get-SPExcelBlockedFileType

New-SPExcelBlockedFileType

Remove-SPExcelBlockedFileType

SPExcelDataConnectionLibrary

Get-SPExcelDataConnectionLibrary

New-SPExcelDataConnectionLibrary

Remove-SPExcelDataConnectionLibrary

Set-SPExcelDataConnectionLibrary

SPExcelDataProvider

Get-SPExcelDataProvider

New-SPExcelDataProvider

Remove-SPExcelDataProvider

Set-SPExcelDataProvider

SPExcelFileLocation

Get-SPExcelFileLocation

New-SPExcelFileLocation

Remove-SPExcelFileLocation

Set-SPExcelFileLocation

SPExcelServiceApplication

Get-SPExcelServiceApplication – Gets an {Excel Service} application object.

New-SPExcelServiceApplication -

Set-SPExcelServiceApplication – Sets a global property for an {Excel Services} application.

SPExcelUserDefinedFunction

Get-SPExcelUserDefinedFunction

New-SPExcelUserDefinedFunction

Remove-SPExcelUserDefinedFunction

Set-SPExcelUserDefinedFunction

SPFarm

Backup-SPFarm – Creates a backup of an individual database, Web application, or the entire farm.

Get-SPFarm – Returns the local SharePoint farm.

Restore-SPFarm

SPFarmConfig

Get-SPFarmConfig

Set-SPFarmConfig

SPFarmEncryptionKey

Update-SPFarmEncryptionKey – Changes the farm encryption key to a new value and re-encrypts all data currently encrypted with the current farm encryption key with the new one.

SPFeature

Disable-SPFeature – Disables an installed feature at a given scope.

Enable-SPFeature – Enables an installed feature at the given scope.

Get-SPFeature – Returns the features based on a give scope.

Install-SPFeature – Install a feature using the Feature.xml file.

Uninstall-SPFeature – Uninstalls an installed feature definition.

SPFeatureSet

Get-SPFeatureSet

New-SPFeatureSet

Remove-SPFeatureSet

SPFeatureSetMember

Add-SPFeatureSetMember

Remove-SPFeatureSetMember

SPHelpCollection

Get-SPHelpCollection

Install-SPHelpCollection – Install the provided help collection files.

Uninstall-SPHelpCollection

SPIdentityProvider

Get-SPIdentityProvider

New-SPIdentityProvider

Remove-SPIdentityProvider

Set-SPIdentityProvider

SPIisWebServiceApplicationPool

Get-SPIisWebServiceApplicationPool – Returns the specified Internet Information Services (IIS) Application pool.

New-SPIisWebServiceApplicationPool – Creates a new Web service application pool.

Remove-SPIisWebServiceApplicationPool – Completely deletes the specified Web service application pool.

Set-SPIisWebServiceApplicationPool – Changes the account used for the Identity of the specified application pool.

SPIisWebServiceSettings

Get-SPIisWebServiceSettings – Returns the common Web Service settings.

Set-SPIisWebServiceSettings – Configures one or more common settings for all Web services.

SPInfoPathAdministrationFiles

Export-SPInfoPathAdministrationFiles – Saves form templates on the SharePoint Central Administration Web site and UDCX files to a CAB file.

Import-SPInfoPathAdministrationFiles – Imports form templates and UDCX files located on the SharePoint Central Administration Web site.

SPInfoPathFormsService

Get-SPInfoPathFormsService – Returns the forms service settings in the farm.

Set-SPInfoPathFormsService – Sets paramaters for the InfoPath Forms Services.

SPInfoPathFormTemplate

Disable-SPInfoPathFormTemplate – Deactivate a form template from the specified site collection.

Enable-SPInfoPathFormTemplate – Activates a form template in the specified site collection.

Get-SPInfoPathFormTemplate – Returns an InfoPath form template.

Install-SPInfoPathFormTemplate – Installs an InfoPath form template on a farm.

Set-SPInfoPathFormTemplate – Sets properties of an InfoPath form template.

Start-SPInfoPathFormTemplate – Unquieces an InfoPath form template on a farm after an upgrade.

Stop-SPInfoPathFormTemplate – Disables an InfoPath form template on a farm before an upgrade.

Test-SPInfoPathFormTemplate – Validates that a form template can be browser-enabled.

Uninstall-SPInfoPathFormTemplate – Removes a form template from a farm.

Update-SPInfoPathFormTemplate – Upgrades all forms templates on the farm.

SPInfoPathUrl

Update-SPInfoPathUrl – Executes InfoPath XSN/UDC fix-up on SharePoint Services.

SPInfoPathUserAgent

Add-SPInfoPathUserAgent – Adds a user agent to a farm.

Get-SPInfoPathUserAgent – Returns a user agent or all the currently defined user agents for the farm.

Remove-SPInfoPathUserAgent – Removes a user agent.

SPInfoPathWebServiceProxy

Get-SPInfoPathWebServiceProxy – Returns the Web proxy settings for the Web application.

Set-SPInfoPathWebServiceProxy – Sets parameters for an existing SharePoint Web service application.

SPLogEvent

Get-SPLogEvent

SPLogFile

Merge-SPLogFile

New-SPLogFile

SPLogLevel

Clear-SPLogLevel

Get-SPLogLevel

Set-SPLogLevel

SPManagedAccount

Get-SPManagedAccount – Retrieves accounts registered in configuration database.

New-SPManagedAccount – Registers a new managed account.

Remove-SPManagedAccount – Removes a managed account from the farm.

Set-SPManagedAccount – Configures the managed account.

SPManagedPath

Get-SPManagedPath – Returns all managed paths that match the given criteria.

New-SPManagedPath – Creates a new managed path for the given Web application for all host header site collections.

Remove-SPManagedPath – Deletes the specified managed path from the specified host header or Web application.

SPMetadataServiceApplication

Get-SPMetadataServiceApplication – Get a MetadataWebServiceApplication instance

New-SPMetadataServiceApplication – Create a Metadata Shared Service Application

Set-SPMetadataServiceApplication – Set properties on a Metadata Shared Service Application

SPMetadataServiceApplicationProxy

Get-SPMetadataServiceApplicationProxy – Get a MetadataWebServiceApplicationProxy instance

New-SPMetadataServiceApplicationProxy – Create proxy for remote or local Metadata shared service application

Set-SPMetadataServiceApplicationProxy – Update metadata proxy settings

SPMetadataWebServicePartitionData

Clear-SPMetadataWebServicePartitionData

Export-SPMetadataWebServicePartitionData

Import-SPMetadataWebServicePartitionData

SPMobileMessagingAccount

Get-SPMobileMessagingAccount – Retrieves mobile messaging accounts for the specified Web application.

Set-SPMobileMessagingAccount – Configures the specified mobile messaging account.

SPObaSolutionPackage

New-SPObaSolutionPackage

SPObjectSecurity

Get-SPObjectSecurity – Returns the security information for the specified service application.

SPParentFarmTrust

Get-SPParentFarmTrust

New-SPParentFarmTrust

Remove-SPParentFarmTrust

Set-SPParentFarmTrust

SPPassPhrase

Set-SPPassPhrase – Sets the Passphrase to a new value.

SPProcessAccount

Get-SPProcessAccount

SPProduct

Get-SPProduct – Returns a list of the SharePoint related products installed in the farm and the versions of all updates installed for each of them.

SPProfileServiceApplication

New-SPProfileServiceApplication

Set-SPProfileServiceApplication

SPProfileServiceApplicationProxy

New-SPProfileServiceApplicationProxy

Set-SPProfileServiceApplicationProxy

SPProfileServiceApplicationTenant

Add-SPProfileServiceApplicationTenant

Export-SPProfileServiceApplicationTenant

Import-SPProfileServiceApplicationTenant

Remove-SPProfileServiceApplicationTenant

Set-SPProfileServiceApplicationTenant

SPResourceSecurity

Initialize-SPResourceSecurity

SPSearchService

Get-SPSearchService – Returns a search service.

Set-SPSearchService – Sets properties of a search service.

SPSearchServiceInstance

Get-SPSearchServiceInstance – Returns an instance of a search service.

Set-SPSearchServiceInstance – Sets properties of a search service instance.

SPSecureStoreApplication

Get-SPSecureStoreApplication

New-SPSecureStoreApplication

Remove-SPSecureStoreApplication

Set-SPSecureStoreApplication

SPSecureStoreApplicationField

New-SPSecureStoreApplicationField

SPSecureStoreApplicationServerKey

Update-SPSecureStoreApplicationServerKey

SPSecureStoreCredentialMapping

Clear-SPSecureStoreCredentialMapping

Update-SPSecureStoreCredentialMapping

SPSecureStoreGroupCredentialMapping

Update-SPSecureStoreGroupCredentialMapping

SPSecureStoreMasterKey

Update-SPSecureStoreMasterKey

SPSecureStoreServiceApplication

New-SPSecureStoreServiceApplication

Set-SPSecureStoreServiceApplication

SPSecureStoreServiceApplicationProxy

New-SPSecureStoreServiceApplicationProxy

SPSecureStoreTargetApplication

New-SPSecureStoreTargetApplication

SPSecurityTokenService

Get-SPSecurityTokenService

SPServer

Get-SPServer – Returns the server(s) in the farm that match the given identity.

Rename-SPServer – Renames a server that is currently connected to the farm.

SPServiceApplication

Get-SPServiceApplication – Return the specified service application.

Grant-SPServiceApplication – Grants a user account access to the Service Application.

Publish-SPServiceApplication – Share the specified local Service Application outside the farm.

Remove-SPServiceApplication – Deletes the specified service application on the local server.

Revoke-SPServiceApplication – Revokes a user’s access to a service application.

Set-SPServiceApplication

Unpublish-SPServiceApplication – Stop sharing the specified service application outside the farm.

SPServiceApplicationProxy

Get-SPServiceApplicationProxy – Returns an instance of the specified Service Application Proxy.

Remove-SPServiceApplicationProxy – Delete the specified service application proxy.

SPServiceApplicationProxyGroup

Get-SPServiceApplicationProxyGroup – Returns the proxy group for the specified service application.

New-SPServiceApplicationProxyGroup – Creates a new service application proxy group.

Remove-SPServiceApplicationProxyGroup – Completely deletes the specified service application proxy group.

SPServiceApplicationProxyGroupMember

Add-SPServiceApplicationProxyGroupMember – Adds a member to the service application proxy group.

Remove-SPServiceApplicationProxyGroupMember – Removes one or more proxies from the specified service application proxy group.

SPServiceContext

Get-SPServiceContext

SPServiceEndpoint

Get-SPServiceEndpoint

Set-SPServiceEndpoint

SPServiceInstance

Get-SPServiceInstance – Returns the services instance for a specific server or the farm.

Start-SPServiceInstance – Starts the Service Instance for a Service on a specific server or the farm.

Stop-SPServiceInstance – Stops the Service Instance for a Service.

SPSessionStateService

Disable-SPSessionStateService

Enable-SPSessionStateService

Get-SPSessionStateService

Set-SPSessionStateService

SPSharedServiceApplicationInfo

Receive-SPSharedServiceApplicationInfo

SPSingleSignOn

Disable-SPSingleSignOn – Disables the SharePoint Single Sign On service

SPSingleSignOnDatabase

Upgrade-SPSingleSignOnDatabase – Upgrades the SSO 12 data to a Secure Store database

SPSite

Backup-SPSite – Performs a backup of a site collection.

Get-SPSite – Returns all site collections that match the given criteria.

New-SPSite – Creates a new site collection at the specified URL.

Remove-SPSite – Completely deletes an existing site collection and all sub-sites.

Restore-SPSite – Restores a site collection.

Set-SPSite – Configures the specified sites.

SPSiteAdministration

Get-SPSiteAdministration – Returns a site administration object which allows a farm administrator to view certain information about site collections they may not have access to.

Set-SPSiteAdministration – Allows farm administrators to configure any site collection.

SPSiteSubscription

Get-SPSiteSubscription – Returns the site subscription for the given URL or all site subscriptions in the local farm.

New-SPSiteSubscription – Creates a new site subscription.

Remove-SPSiteSubscription – Removes a site subscription along with all contained site collections and settings.

SPSiteSubscriptionConfig

Get-SPSiteSubscriptionConfig

Set-SPSiteSubscriptionConfig

SPSiteSubscriptionMetadataConfig

Get-SPSiteSubscriptionMetadataConfig

Remove-SPSiteSubscriptionMetadataConfig

Set-SPSiteSubscriptionMetadataConfig

SPSiteSubscriptionSettings

Export-SPSiteSubscriptionSettings

Import-SPSiteSubscriptionSettings

Remove-SPSiteSubscriptionSettings

SPSolution

Add-SPSolution

Get-SPSolution

Install-SPSolution

Remove-SPSolution

Uninstall-SPSolution

Update-SPSolution

SPSolutionDeploymentLock

Remove-SPSolutionDeploymentLock

SPStateServiceApplication

Get-SPStateServiceApplication

New-SPStateServiceApplication

Set-SPStateServiceApplication

SPStateServiceApplicationProxy

Get-SPStateServiceApplicationProxy

New-SPStateServiceApplicationProxy

Set-SPStateServiceApplicationProxy

SPStateServiceDatabase

Dismount-SPStateServiceDatabase

Get-SPStateServiceDatabase

Initialize-SPStateServiceDatabase

Mount-SPStateServiceDatabase

New-SPStateServiceDatabase

Remove-SPStateServiceDatabase

Resume-SPStateServiceDatabase

Set-SPStateServiceDatabase

Suspend-SPStateServiceDatabase

SPSubscriptionSettingsServiceApplication

New-SPSubscriptionSettingsServiceApplication

Set-SPSubscriptionSettingsServiceApplication

SPSubscriptionSettingsServiceApplicationProxy

New-SPSubscriptionSettingsServiceApplicationProxy

SPTaxonomySession

Get-SPTaxonomySession – Get a TaxonomySession instance

SPTimerJob

Disable-SPTimerJob

Enable-SPTimerJob

Get-SPTimerJob

Set-SPTimerJob

Start-SPTimerJob

SPTopologyWebServiceApplication

Get-SPTopologyWebServiceApplication

Set-SPTopologyWebServiceApplication

SPTopologyWebServiceProxy

Get-SPTopologyWebServiceProxy

Set-SPTopologyWebServiceProxy

SPUsageApplication

Get-SPUsageApplication

New-SPUsageApplication

Remove-SPUsageApplication

Set-SPUsageApplication

SPUsageDefinition

Get-SPUsageDefinition

Set-SPUsageDefinition

SPUsageLogFile

New-SPUsageLogFile

SPUsageService

Get-SPUsageService

Set-SPUsageService

SPUser

Get-SPUser – Returns the user(s) that match a given search criteria.

Move-SPUser – Migrates a user account in .

New-SPUser – Adds an existing user to a site with the designated permissions.

Remove-SPUser – Removes a user from a web site.

Set-SPUser – Configures properties on an existing user.

SPUserProfilePhotoStore

Update-SPUserProfilePhotoStore

SPUserSolution

Add-SPUserSolution

Get-SPUserSolution

Install-SPUserSolution

Remove-SPUserSolution

Uninstall-SPUserSolution

Update-SPUserSolution

SPVisioExternalData

Get-SPVisioExternalData – Returns the settings for external data connections for a Visio Service application.

Set-SPVisioExternalData

SPVisioPerformance

Get-SPVisioPerformance – Returns the Visio Graphics Services settings for the performance of a Visio Service application.

Set-SPVisioPerformance – Sets performance properties for a Visio Services application.

SPVisioSafeDataProvider

Get-SPVisioSafeDataProvider – Returns the settings of a safe data provider for a Visio Services application.

New-SPVisioSafeDataProvider – Adds a new data provider to a Visio Services application.

Remove-SPVisioSafeDataProvider – Removes a data provider from a Visio Services application.

Set-SPVisioSafeDataProvider – Specifies a description of a safe data provider for a Visio Services application.

SPVisioServiceApplication

Get-SPVisioServiceApplication – Returns properties of a Visio Services application or a collection of Visio Services applications.

New-SPVisioServiceApplication – Adds a new Visio Services application to a farm.

Remove-SPVisioServiceApplication – Removes a Visio Services application from a farm.

Set-SPVisioServiceApplication – Sets the ServiceApplicationPool property of a Visio Services application.

SPVisioServiceApplicationProxy

Get-SPVisioServiceApplicationProxy – Returns properties of a Visio Services application proxy or a collection of Visio Services application proxies.

New-SPVisioServiceApplicationProxy – Adds a new Visio Services application proxy to a farm.

Remove-SPVisioServiceApplicationProxy – Removes a Visio Services application proxy from a farm.

SPWeb

Export-SPWeb – Exports a site collection, Web application, list, or library.

Get-SPWeb – Returns all sub-sites that match the given criteria.

Import-SPWeb – Imports a site collection, Web application, list, or library.

New-SPWeb – Creates a new sub-site under any existing site collection.

Remove-SPWeb – Completely deletes the specified Web.

Set-SPWeb – Configures the specified sub-site.

SPWebAnalyticsServiceApplication

Get-SPWebAnalyticsServiceApplication – Returns the settings for a Web Analytics Service application.

New-SPWebAnalyticsServiceApplication – Adds a new Web Analytics Service application to the farm.

Set-SPWebAnalyticsServiceApplication – Sets properties of a Web Analytics Service application.

SPWebAnalyticsServiceApplicationProxy

New-SPWebAnalyticsServiceApplicationProxy – Adds a new Web Analytics Service application proxy to the farm.

SPWebApplication

Get-SPWebApplication – Returns all Web applications that match the given criteria.

New-SPWebApplication – Creates a new Web application within the local farm.

Remove-SPWebApplication – Deletes the specified Web application.

Set-SPWebApplication – Configure the specified Web application.

SPWebApplicationExtension

New-SPWebApplicationExtension – Creates a new zone instance for the Web application.

SPWebApplicationHttpThrottling

Disable-SPWebApplicationHttpThrottling

Enable-SPWebApplicationHttpThrottling

SPWebApplicationHttpThrottlingMonitor

Set-SPWebApplicationHttpThrottlingMonitor

SPWebApplicationHttpThrottlingMonitors

Get-SPWebApplicationHttpThrottlingMonitors

SPWebApplicationSiginRedirectUrl

Set-SPWebApplicationSiginRedirectUrl

SPWebPartPack

Get-SPWebPartPack – Return the Web part packages installed for the specified scope.

Install-SPWebPartPack – Installs the specified Web part package to the specified location.

Uninstall-SPWebPartPack – Uninstall the specified Web part package.

SPWebTemplate

Get-SPWebTemplate – Displays all globally installed site templates that match the given identity.

Install-SPWebTemplate – Installs the given site template.

Set-SPWebTemplate – Changes the title and description of an installed site template.

Uninstall-SPWebTemplate – Uninstall the given site template.

SPWordConversionServiceApplication

New-SPWordConversionServiceApplication – Creates a new service application.

Set-SPWordConversionServiceApplication – Sets parameters on a service application.

SPWordConversionServiceApplicationProxy

New-SPWordConversionServiceApplicationProxy – Creates a new service application proxy.

SPWorkflowConfig

Get-SPWorkflowConfig – Returns workflow settings for the specified Web application.

Set-SPWorkflowConfig – Configures the workflow settings for the specified Web application.

SharePoint 2010 Performance and Capacity planning

2010-12-18T22:11:00.000+02:00

For those wanting to dig deeper into SharePoint 2010 products performance and Capacity planning, Microsoft has published some very good documents on performance tests, results and recommendations. Again, this is for those Admins who want to dig deeper into SharePoint 2010. It could help if you are creating design documents or archtecture for SharePoint 2010 for your organisation.

Even if you arent looking yet, I suggest you book mark this page. One day you may need it! I know I have and would like to share it with you!

These documents contain scenario based testing of various SharePoint 2010 Service Applications and features. They discuss recommendations by Microsoft on hardware resources, architecture and configuration to maximise and enhance the SharePoint 2010 experience.

AccessServicesCapacityPlanningDoc.docx
BCSCapacityPlanningDoc.docx
DesigningLargeListsMaximizingListPerformance.docx
ExcelServicesCapacityPlanningDoc.docx
InfoPath2010CapacityPlanningDoc.docx
LargeScaleDocRepositoryCapacityPlanningDoc.docx
MySitesSocialComputingCapacityPlanningDoc.docx
OfficeWebAppsCapacityPlanningDoc.docx
SearchforSPServer2010CapacityPlanningDoc.docx
SharePointServerCachesPerformance.docx
VisioServicesCapacityPlanningDoc.docx
WASCapacityPlanningDoc.docx
WCMCapacityPlanningDoc.docx
WebAnalyticsCapacityPlanningDoc.docx
WorkflowCapacityPlanningDoc.docx

Here is the link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=fd1eac86-ad47-4865-9378-80040d08ac55&displaylang=en

SharePoint 2010 - Important StatusStatus: This page has been declared a record or placed on hold and is locked as read-only

2010-12-17T22:14:00.000+02:00

In SharePoint 2010, you may experience this message on your page that you are trying to edit/view:
Important StatusStatus: This page has been declared a record or placed on hold and is locked as read-only

Solution:
1. Ensure that no other users have checked-in the page. You may have to ensure that the page has been Checked-out for you to to edit the page.
2. Ensure you have the appropriate permissions to edit the page.

SharePoint 2010 Search issue Internal server error exception. Troubleshoot issues Correlation ID

2010-12-16T22:16:00.000+02:00

When you search in SharePoint 2010, you may get the following error:

Error

Internal server error exception

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: de2996f1-a6c9-42fb-a6da-e5fc7d769069

Solution:

You will have to install the following hotfix

http://go.microsoft.com/fwlink/?LinkID=166231

For Windows Server 2008 R2, Hotfix for.NET Framework 3.5 SP1 that provides a method to support the token authentication without transport security or message encryption in WCF (http://go.microsoft.com/fwlink/?LinkID=166231).

Remote BLOB Storage – RBS SharePoint 2010

2010-12-14T22:20:00.000+02:00

Microsoft SharePoint 2010 caters for farms with large storage needs. SharePoint 2010 has implemented RBS – Remote Storage BLOB. With RBS, you can store BLOBs from the all_docs table and customised pages in the database stored in different location from the database, such as a file system in your network! This reduces the amount of database storage in SQL. To use RBS, a “provider” is required. The RBS provider architecture is ‘plug n play’ with SharePoint 2010. This means that third-party vendors can create and sell their own RBS provider products commercially with specific capabilities. (idea!).

For example, a third party backup vendor can use an RBS provider as part of their backup and restore capability.

The RBS architecture provides another degree of freedom for the storage of content. Its intention is to be used natively by SharePoint during the upgrade process and by third party vendors that provide storage benefits as a service.

SharePoint 2010 error when trying to delete a managed account: An object in the SharePoint administrative framework, SPManagedAccount Name=managed-account could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation.

2010-12-13T22:22:00.000+02:00

After deleting a Service Application, you may want to clear up the corresponding managed account that you created for the Service Application.

You may run into this error when attempting to delete the managed account in SharePoint Central Administration:

An object in the SharePoint administrative framework, SPManagedAccount Name=managed-account could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation.

Solution:

Remove the dependency, which is a Service Application Pool that may depend on this managed account.
Get-SPServiceApplicationPool (to get a list of the Application Pools, you will need to take note of the name for the next powershell cmdlet).
Remove-SPServiceApplicationPool (then enter the name of the Application Pool). Remove the Managed account via Powershell or through the GUI
Get-SPManagedAccount
Remove-SPManagedAccount

SharePoint 2010 - Send Notification on Item Approved/Rejected (when Content Approval Status is changed)

2010-11-16T22:16:00.000+02:00

In SharePoint 2010 new improvements are made for better event receiving management. Few new event handlers are added for site, web, list, listitems etc. However, One thing that I think badly needed was the content approval events for list items.

Nowadays content approval has become an integral part of content management system. Requirements has come up to do more work on content approval/reject. But unfortunately, SharePoint list/library doesn’t have events like ContentApproved, ContentRejected, ContentRequestedForReview so that user can tap the events to do their own work on content approval status changes. So it seems we need to do a lot of works manually to send notifications on content approval status changes.

Problem: Approving Status change events Missing

One of my client wanted to get notification on the following scenarios:

1. On Item Add/Update: If a user edit an item and item goes to pending status as the item needs approval, the approving teams need to be notified that an item is waiting for their approval.

2. On Item Approved: If the approving team approve the item,the user who added/updated the item needs to be notified.

3. On Item rejected: If the approving team reject the item, the user who added/updated the item needs to be notified with reasons why the item rejected.

But the SharePoint Object Model doesn’t have the extensibility at this point where approving status changes.

Why Approval Status change event missing?

The best solution would be if SharePoint team would provide us with out-of-box events for content approval. In that case, two events would be suffice. The events might be : ContentApprovingStatusChanging and ContentApprovingStatusChanged and the event argument’s AfterProperties and BeforeProperties values could be filled with the the old value and new value of Content Approving Status field value. However, one may argue that ItemAdded/ItemUpdate events are similar like Content Approval events. So when user add/edit an item and as part of the add/edit if approval status field get updated then which events to fire? ItemAdded/ItemUpdate or content approval events. Hmm.. maybe there’s complexities with the new content approval events and SharePoint team has not added the new content approval events.

Resolution: Use ItemAdded, ItemUpdating and ItemUpdated events to keep track of approval status changing

So consider now the problem we’re going to talk about. We need a notification system where we need to send notification to the approver or user (who is waiting for approval) on approval status change. We’ll develop a list item event receiver for ItemAdded and ItemUpdated events. When a new item will be added it’s easy to identify item status and if the status is pending then we can send notification to all people in the approving team. But when an Item is updated, you need to keep track of if the Approving status field value is changed, if so then u need to send notification. However, you can only get the old approval status field value in ItemUpdating event, but you don’t want to send notification in ItemUpdating. So it’s safe to send notification in ItemUdated event but in ItemUpdated event you’ll not get the old value. You can access the old value in ItemUpdating. So here’s the deal:

Create a new field say OldStatus in the list. This field will be used to keep track of if the approval status field value has been changed. In ItemUpdating event, set the current approval status (before updating) to OldStutus field. In ItemUpdated, compare the current status to OldStatus field value and if they are not same then it’s for sure that the approval status has been changed. So send notification.

So let’s go with the steps. First we need an List Event Receiver that will listen three events of the list: ItemAdded, ItemUpating and ItemUpdated. You need to send notification on two events: ItemAdded and ItemUpdated. However, we need to hook the event ItemUpdating to know whether the approval status is going to be changed

Create a List Event Receiver to send notification

Send notification on Item Added

On Item added event, check if the item status is pending. If so then send notification. The following code snippet may give you the gist.

public override void ItemAdded(SPItemEventProperties properties)
{
    const string approvalStatusFieldInternalName = "_ModerationStatus";

    var list = properties.List;
    var approvalStatuField = 
list.Fields.GetFieldByInternalName(approvalStatusFieldInternalName);
    var approvalStatusFieldValue = properties.ListItem[approvalStatuField.Id];
    var approvalStatus = (approvalStatusFieldValue == null) ? string.Empty :
                            approvalStatusFieldValue.ToString();
    if (approvalStatus == "Pending")
    {
        //SendNotification()
    }
}

Keep track of the approval status field value (before updated) on Item Updating event

I’m assuming that you have a field OldStatus where I’ll keep the approval status field value which is going to be changed. I’ll explain later in this post how to automatically add the field in list. But for now just take for granted that you have a field OldStatus in your list of type string. The following code show how to keep the approval status (before update) value in OldStatus field in ItemUpdating Event.
public override void ItemUpdating(SPItemEventProperties properties)
{
    const string approvalStatusFieldInternalName = "_ModerationStatus";

    var list = properties.List;
    var approvalStatuField = 
list.Fields.GetFieldByInternalName(approvalStatusFieldInternalName);
    var approvalStatusFieldValue = properties.ListItem[approvalStatuField.Id];
    var approvalStatusValue = (approvalStatusFieldValue == null) ? string.Empty :
                approvalStatusFieldValue.ToString();

    if (string.IsNullOrEmpty(approvalStatusValue)) return;

    EventFiringEnabled = false;
    properties.ListItem["OldStatus"] = approvalStatusValue;
    properties.ListItem.SystemUpdate(false);
    EventFiringEnabled = true;
}

Check the OldStatus field value and current approval status value to know if the approval status changed.</LI>

Item updated is fried once the update is done. So we’ll get the updated value of Approval Status. But fortunately, we have kept the old value of Approval Status field in OldStatus field during ItemUpdating event as shown in step 2.

public override void ItemUpdated(SPItemEventProperties properties)
{
    const string approvalStatusFieldInternalName = "_ModerationStatus";
    var list = properties.List;
    

    var approvalStatusField = 
list.Fields.GetFieldByInternalName(approvalStatusFieldInternalName);
    var currentStatuFieldValue = properties.ListItem[approvalStatusField.Id];
    var currentStatus = (currentStatuFieldValue == null) ? string.Empty : 
                        currentStatuFieldValue.ToString();

    var oldStatusFieldValue = properties.ListItem["OldStatus"];
    var oldStatus = (oldStatusFieldValue == null) ?
string.Empty : oldStatusFieldValue.ToString();

    if (string.IsNullOrEmpty(oldStatus) && oldStatus != currentStatus)
    {
        //SendNotification();
    }
}

Create a feature receiver to attached List Event Receiver and to create field OldStatus

Finally We need an feature receiver (not list event receiver) which will do two works: Attached our list event receiver to a list and create a field OldStatus in the list.

FeatureActivating Event

In FeatureActivating you need to check first if the event is already registered. If not registered then register the event. Also make sure the list has OldStatus field. In the code below, listNeedsToAttachedNotitificationReceivers is array of list names which needs to attach the event receivers.

public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
    string[] listNeedsToAttachedNotitificationReceivers = { "Product", "Order" };
    var myAssemblyName = "MyProject.SharePoint";

    foreach (var listName in listNeedsToAttachedNotitificationReceivers)
    {
        var web = properties.Feature.Parent as SPWeb;
        var list = web.Lists[listName];
        SPEventReceiverDefinitionCollection 
spEventReceiverDefinitionCollection = list.EventReceivers;
        if (!IsEventReceiverAlreadyAttached
(spEventReceiverDefinitionCollection, myAssemblyName))
        {
            //Attach three ItemAdded, ItemUpdating and itemUpdated event receivers
            SPEventReceiverType eventReceiverType = SPEventReceiverType.ItemAdded;
            spEventReceiverDefinitionCollection.Add(eventReceiverType, 
                Assembly.GetExecutingAssembly().FullName, 
                "MyProject.SharePoint.Receivers.ListItem.ContentApprovalEventHandler");
            eventReceiverType = SPEventReceiverType.ItemUpdated;
            spEventReceiverDefinitionCollection.Add(eventReceiverType, 
                Assembly.GetExecutingAssembly().FullName, 
                "MyProject.SharePoint.Receivers.ListItem.ContentApprovalEventHandler");
            eventReceiverType = SPEventReceiverType.ItemUpdating;
            spEventReceiverDefinitionCollection.Add(eventReceiverType, 
                Assembly.GetExecutingAssembly().FullName, 
                "MyProject.SharePoint.Receivers.ListItem.ContentApprovalEventHandler");
            list.Update();
        }
        EnusureOldStatusFieldExists(list);
    }
}

private static bool I
sEventReceiverAlreadyAttached(SPEventReceiverDefinitionCollection 
spEventReceiverDefinitionCollection, string myAssemblyName)
{
    bool eventReceiverAttached = false;
    for (int i = 0; i < spEventReceiverDefinitionCollection.Count; i++)
    {
        if (spEventReceiverDefinitionCollection[i].Assembly.Contains(myAssemblyName))
        {
            eventReceiverAttached = true;
            break;
        }
    }
    return eventReceiverAttached;
}

private static void EnusureOldStatusFieldExists(SPList list)
{
    var field = list.Fields.TryGetFieldByStaticName("OldStatus");
    if (field == null)
    {
        list.Fields.Add("OldStatus", SPFieldType.Text, false);
        list.Update();
    }
}

Feature Deactivating Event

In feature deactivating event, unregister the list event receivers. If you want you can delete the OldStatus field. However I have not deleted the field in the code below:

public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
{
    string[] listNeedsToAttachedNotitificationReceivers = { "Product", "Order" };
    var myAssemblyName = "MyProject.SharePoint";


    foreach (var listName in listNeedsToAttachedNotitificationReceivers)
    {
        var receiversToRemove = new List<Guid>();
        var web = properties.Feature.Parent as SPWeb;
        var list = web.Lists[listName];
        SPEventReceiverDefinitionCollection 
spEventReceiverDefinitionCollection = list.EventReceivers;
        for (int i = 0; i < spEventReceiverDefinitionCollection.Count; i++)
        {
            if (spEventReceiverDefinitionCollection[i].Assembly.Contains(myAssemblyName))
            {
                receiversToRemove.Add(spEventReceiverDefinitionCollection[i].Id);
            }
        }
        if (receiversToRemove.Count > 0)
        {
            foreach (var guid in receiversToRemove)
            {
                list.EventReceivers[guid].Delete();

            }
            list.Update();
        }
    }
}

How it works all together?

It’s a bit complex huh? oK, let’s me explain how it works.

The feature receiver needs to be activated first. The feature receiver attached the event receiver to list and create a string field OldStatus in the list. Next if an item is added to the list, the listItem event gets fired and if the item status is pending (means needs approval) then send notification. If an existing item is edited and saved then ItemUpdating event is fired. This is the event where the item is not yet saved. So I have put the current approval status in the OldStatus field. In ItemUpated event I have compared the OldStatus and current status field value. If the valued doesn’t match then the approval status is changed and we need to send the notification.

Move SharePoint Site/Web From One Development Server to Another

2010-11-15T22:15:00.000+02:00

Sometimes, we need to move the site from one server to another, usually in development environment. In that case its required few steps to make sure you have moved your site in new server. I have successfully move my sites and I’m pointing here the exact steps that worked for me.

Backup the site or export the web

First of all you need to take backup of the site (if you want to move site collection). If you want to move a single site then export the web contents. For site backup use the following command:

Backup-SPSite -Identity http://MySiteColllection.com -Path "C:\Backup\BackupFile.bak" -Confirm:$false

For exporting web use the following command.

Export-SPWeb –Identity http://MySiteCollection.com/myweb –Path “C:\Backup\BackupFile.cmp” –Confirm:$False

For more on these commands follow MSDN link.

Create Dummy site or web on the destination server to overwrite

Before restoring or importing site/web you need to create a dummy site/web on the destination server. In case of site restore, create a new site collection. In case of web import, create a site with the same name and template used in source server’s web.

Deploy code on the server

If possible, then deploy the sharepoint solution (generated from your developer code in Visual Studio) on the destination server. In some case the restore/import operation looks for features/resources on the site/web that is referenced in the backup/export file. So deploying the code on the server make sure the code (that will be finally used in the restored site/web) is on the destination server. If your code has web level feature/resources then use the root web as the default one to deploy code.

Restore or import the site/web

Finally you are ready to restore the site. Run the following command to restore a site collection.

Restore-SPSite -Identity http://MyNewSiteCollection.com -Path "C:\Backup\BackupFile.bak" -Confirm:$false -Force

Run the following import command to import site.

Import-SPWeb –Identity http://MyNewSieCollection.com/MyNewWeb –Path “C:\Backup\BackupFile.cmp” –Overwrite –Confirm:$False

For more on these commands follow MSDN link.

Check user Permissions

If you restored a site collection then you need to change site collection administrator as the restored site is still pointing to the old site collection administrators (and maybe the administrator is invalid in the new server). From SharePoint central administration site change the site collection administrator to proper one.

Few points to notice

When you move the site/web few points need to remember:

If you restore just a web then your import operation may fail saying a feature is not installed on the web/site. This may happen in case where the source site /web’s backup file is referring a resource (say feature) that is not available on the destination server. In this case, make sure your code is deployed properly on the destination server. If you get the error for a particular web, then create a dummy web with the same name as on the source server, on the destination server and then deploy the code on the web and finally try to restore the web. In case of web import, make sure you have created the new web on the destination server with the same template. You can’t overwrite a web on destination server with a source one that is using different template.

SharePoint Error: The exported site is based on the template STS#1 but the destination site is based on the template STS#0

2010-11-14T22:13:00.000+02:00

Today I was trying to export one of my site from one Virtual machine to another. First I took a export of the web from my source server and then I tried to import the content in the destination server. And then the import failed with the error “The exported site is based on the template STS#1 but the destination site is based on the template STS#0”. I couldn’t remember the template with which I created the source site but I took for granted from the error message that the source and destination web are not created from the same template. After googling I finally found import will only work if source and destination web are created from the same template. In my case the source site was created from Blank Site template (STS#1) but the destination site was created from Team site template (STS#0).

So I deleted the destination site and recreated with the source template and the import was successful. For full lists of web site templates you can followAravindhan’s posts.

SharePoint 2010 - Rename Site Url

2010-11-13T22:10:00.000+02:00

Sometimes in development environment and even in production you may need to rename a site url. For example you have planned a site with URLwww.mysite.com in Development or in Production. Later you have decided to rename the site url to www.yoursite.com. There’s no shortcut way to do that in SharePoint. You need to delete the existing web application for url www.mysite.com and create a new one with url www.yoursite.com.

1. Backup the site collection first

Run the following powershell command to backup site.

Backup-SPSite –Identity SiteUrl –Path BackupLocation

2. Delete the existing site from central admin.

Navigate to central admin and delete the web application including database and IIS site as shown below:

3. Create the a new site with new Url (say http://www.yoursite.com)

Now create a new web application with the new url in host header as shown below:

4. Restore the backup on the new site

Finally restore the backup taken on step 1 overwriting the new site collection. Run the following command on powershell command

Restore-SPSite –Identity SiteUrl –Path BackupFilePath -Force

Linq to SharePoint

2010-11-12T22:08:00.000+02:00

SharePoint 2010 has added new Linq extension called Linq-to-SharePoint similar like Linq-to-Sql. In Linq to Sql, when you Visual Studio generate classes based on your database schema, under the hood a tool called SqlMetal is used. Though VS generates classes for you, you can use SqlMetal outside of VS for your own purpose. Linq to SharePoint is new extension which allows to generate DataContext (having classes representing lists) based on your sharepoint lists using SPMetal and you can use the DataContext for manipulating SharePoint list in an object-oriented fashion. So you don’t need to worry about CAML or SharePoint Object Model. The steps to work with Linq-to-SharePoint is easy. Let’s dig it deeper.

Generate Linq-to-SharePoint DataContext class: To use Linq to SharePoint you need to use SPMetal to generate Linq-To-SharePoint class. You can find the SPMetal in the location “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN”. You can run the command from command prompt. For example the following command will generate Linq-to-SharePoint DataContext class for site ‘http://localhost’ and put the code inC:\MyClass.cs file with namespace MyNameSpace.

spmetal /web:http://localhost /code:c:\myclass.cs /namespace:mynamespace

One thing to point here is that there are Visual Studio extension availa to enable developers to generate DataContext from Visual Studio. One such tool isLinq to SharePoint DSL Extension.
Add DataContext class to your Visual Studio Project: The file you have generated at step 1 need to add in your Visual Studio Project. To do so you need to add reference to Microsoft.SharePoint.Linq.dll from Visual Studio’s Add Reference windows’ ‘.NET’ tab.
Code Using DataContext Class: Now you can use the DataContext class for manipulating SharePoint lists. For example in the following code I have used the DataContext class generated at step 1 to add a new product in the product list.

using (var context = new MyclassDataContext(http://mysite))
{
    var item = new ProductItem();
    item.AvaialableQuantity = 100;
    item.LaunchDate = DateTime.Now;
    item.ProductDescription = "this is computer monitor";
    item.ProductName = "Monitor";
    context.Product.InsertOnSubmit(item);
    context.SubmitChanges();  
}

Suggestion: If you use SPMetal to generate DataContext class then you’ll find that all classes are placed in a single file (in my case MyClass.cs file). This is very difficult to manage and modify. My suggestion will be to modify the file to move classes in individual pages. You can use some Refactoring tools like Resharper.</LI>

CAML and Linq side-by-side

You may think CAML is dead now as we can do all operations using Linq to SharePoint. Wait, here few point to notice. Firstly, when you use Linq to SharePoint, under the hood, CAML is used. the Linq to SharePoint convert you expression in CAML. However, you can still use CAML for retriving data from database, then you can use Linq to do operations on returned results. For example, you can use CAML to find products. Then you can run linq query against the result set to perform operations like orderby, group, join etc. As shown in the example below, I have used Linq to SharePoint to query Product list to find items whose name contains monitor and also ordered by available quantity.

using (var context = new MyclassDataContext("http://mysite"))
{
    var proudcts = from p in context.Product
                    where p.ProductName.Contains("monitor")
                    orderby p.AvaialableQuantity
                    select p;
}

In the following example, I have used CAML query to perform the same operation I have performed above. In the above example I have used Linq to SharePoint extension fully. But in the following example I have used CAML query first to filter data from database. Then I have run Linq query to order data. The following example doesn’t use Linq to SharePoint. Rather it uses the conventional CAML and C# Linq.

SPList productList = SPContext.Current.Web.Lists["Product"];
SPQuery camlQuery=new SPQuery();
camlQuery.Query = "your CAMl query";

var products = productList.GetItems(camlQuery);
var orderProducts = from p in products.Cast<SPListItem>()
                where p["ProductName"].ToString().Contains("monitor")
                orderby Convert.ToInt32(p["AvaialableQuantity"])
                select p;

An Exception you may get:

You may find the following exception when you try to run an application in SharePoint server. At first glance you may think the site is not accessible or you have misspelled the site name. But the real fact is that if you try to run your application in 32 bit mode then you may get the exception.

The Web application at http://localhost could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

Handy tools for Linq to SharePoint

SharePoint 2010 is not out there for too long. But there are much activities to help developers to easy development/deployment. I have found few codeplex projects aimed at easing development,deployment and more. I have found few Visual Studio extensions for SharePoint in MSDN Visual Studio gallery. The major problem we face in SharePoint development is that we need to deploy our code to test in development environment. VS 2010 has added nice extension already for developer to ease and fast development/deployment. But few VS extensions developed by others may add extra value to SharePoint developer’s life. Here are few useful links SharePoint developers may find handy.

Linq to SharePoint DSL Extension

CKS For SharePoint Server

SharePoint Developer Tool

Linq to SharePoint limitations

With Linq to SharePoint you can’t run all kinds of queries. There some kind of queries which is inefficient. For example if you join two lists in such a way that for each item in first list, you need to go to database for finding matching items in second list then the query is inefficient and not supported in Linq to SharePoint. You can find more details on this on the following link:

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

WindowsFormsHost: Host ActiveX and windows form controls in WPF

2010-11-11T22:09:00.000+02:00

If you ever need to host ActiveX control in your wpf application then you can do it by using WindowsFormsHost control. Also sometimes you may need to add windows form control in WPF. you may have developed some controls in windows form technology and you don't want to rewrite this for WPF. WindowsFormsHost control can save you for this time. The following steps describes what to do to add ActiveX or windows form control in wpf application:

1. Add reference to WindowsFromsIntegration assembly which is WindowsFormsIntegration.dll. This is the assembly where WindowsFormsHost control is defined. So if you add WIndowsFormsHost control before adding the assembly reference you''ll find that the WindowsFormsHost control is not recognized in XAML (if you just drag and drop the control form toolbox).

2. Add reference to windows forms assembly which is system.windows.forms.dll. You also need to add the namespace in XAML file as shown below:

xmlns:wf="clr-namespace:System.Windows.Forms;assembly=System.Windows.Forms"

3. Add reference to the activex control. When you add reference from VS automatically generate an AxHost wrapper for the activex control. Then add the assembly reference in XAML file as shown below:

xmlns:ax="clr-namespace:AxLib;assembly=AxInterop.AxLib"

FYI, if you try to add the activex dll reference without adding the other two reference you may not get the namespace in the XAML. WindowsFormsHost control can also be used to host any control designed for windows form.

Now you can add your ActiveX control in one of two ways:

1. Add Control directly in XAML as shown below:

<WindowsFormsHost Name="wfHostControl">
<ax:MyControl x:Name="axMyCtrl"/>
</WindowsFormsHost>

2. Add the control from code by instantiating and placing in the child property of the WindowsFormsHost control.

MyControl ctrl=new MyControl();

wfHostControl.Child = ctrl;

If you need to do something on form load its better to work on WindowsFormsHost control's load event instead of wpf application's load event.

SharePoint 2010: Client Object Model – an Introduction

2010-11-10T21:48:00.000+02:00

SharePoint 2007 allows using its Object model to run against server running SharePoint. For clients (not running SharePoint in the box) the simplest way to communicate with SharePoint server is web services. SharePoint Client Object Model (OM) can be run on client PC (where SharePoint is not installed) to communicate with SharePoint server. So whereas SharePoint (Server) Object Model runs in a SharePoint server and can manipulate SharePoint objects, Client OM can run in client PC and communicate with SharePoint server remotely.

SharePoint 2010 introduces three new client APIs which can be used to interact with SharePoint sites. The three APIs are targeted for three different types of clients:

1. For .net Managed applications (for example, console applications, window applications, web applications etc, which are not running inside SharePoint Context).

2. For Silverlight applications.

3. For using with JavaScript (called ECMAScript). This API is only available for applications hosted inside SharePoint (for example, web part deployed in SharePoint site can use this JavaScript API for accessing SharePoint from browser using JavaScript).

I’ll explain all of these API sets gradually. In this post I’ll explain some basic problems SharePoint developers faced during development with SharePoint 2007 in absence of Client Object Model.

Why Client Object Model (OM)?

SharePoint 2007 had no Client Object model available. So you may ask why this is introduced in SharePoint 2010? We had no problem without Client OM and millions of sites are running smoothly without having Client OM. The main reason is that Microsoft has found lot of requests from SharePoint users to introduce more and more web services to get data out of SharePoint in the last couple of years. But introducing web services will not fix the issues, as Microsoft found, because then the request for more functionality in the web services will continue. Even if Microsoft provides a good numbers of web services with SharePoint, customization in web services will be required for different clients and this will make the out of the box web services unusable. Also introducing a large number of web services will be a waste as not all companies will use all the web services functionalities.

In response to add more web services from users, Microsoft has taken a different approach called Client Object Model (OM). This SharePoint Client OM will allow getting data out of SharePoint from PCs that are not hosting SharePoint. Also Client OM provides complete API to interact with SharePoint Server which is more intuitive and useful and very much similar with SharePoint Object Model.

Similarity with SharePoint Object Model

Now SharePoint developers will fear that the Client Object Model will introduce new burden for them to get used to it. But SharePoint team provided great efforts to keep the Client OM familiar with SharePoint Object Model. The following table shows the equivalent objects in Client and SharePoint Object Model.

Server (Microsoft.SharePoint)	Client Object Model
SPContext	ClientContext
SPSite	Site
SPWeb	Web
SPList	List
SPListItem	ListItem
SPField	Field

So the class names in Client OM are similar as like SharePoint Object Model. However the way client OM will be used a bit different than usual SharePoint Object Model that we will explore in the upcoming posts.

How Client OM is developed and work under the hood?

It’s interesting how SharePoint team has developed the same set of classes for three different sets of applications (Managed, Silverlight and ECMAScript). There is same class ListItem for three different set of applications. As shown in the following table, three different assemblies/files are used for three different types of applications.

Client Type	Assembly/File
Managed Client	Microsoft.SharePoint.Client
Silverlight	Microsoft.SharePoint.Client.Silverlight
ECMAScript	SP.js

To ensure the same class object (say ListItem) behaves similarly in three different types of applications SharePoint team followed the steps described below:

a) SharePoint team first set attributes to the SharePoint classes and methods and properties that need to be exposed in Client OM.

b) Then a code generator is run against the SharePoint object model to generate client OM automatically.

This automated code generation has ensured maximum compatibility between these three sets of APIs. As the following figure shows client communicate to the server thorough Client OM which under the hood uses Client.svc WCF service to communicate with SharePoint Server. Client.svc service uses Server OM as per client request and return result to the client in JSON format.

Figure: How Client Object model works with Server

With this new Client OM, we almost don’t need to use web service to communicate with SharePoint server. However, the client OM just released and we will find its shortcomings as well use it more and more in live projects. In my next posts I’ll go through three differents kinds of Client OM (Managed .net, Silverlight and ECMAScript).

SharePoint 2010: Metadata Service

2010-11-09T21:44:00.000+02:00

In SharePoint 2010 two metadata related supports are added which were a big challenges in SharePoint 2007. One Challenges I faced personally was not having the support of taxonomy or hierarchical metadata. Another challenges was the metadata could not be shared across site collection boundaries. So in SharePoint 2010 the following two new features are added to solve the issues:

1. Taxonomy Support:

Taxonomy is a mean of managing data in hierarchy. Though other CMSs have this taxonomy support out of the box, till SharePoint 2007 we had not this support out of the box. But SharePoint 2010 has this support built in. We can now use hierarchical metadata to tag content in SharePoint 2010.

2. Shared Metadata

Prior to SharePoint 2010 there was no way to share metadata across site collection boundaries. So if you ever needed to share metadata then you would go and copy the same metadata in different site collection. Now in SharePoint 2010 there’s a shared service called “Shared Metadata Service” which will facilitate the metadata sharing across the site collection and web application level.

Few definitions associated with Metadata Service

There are two types of metadata that can be associated with an item in SharePoint 2010:

1. Managed Metadata or Taxonomy: As the name suggested these metadata are managed centrally (from central administration). Users with appropriate permission can only add/edit/deleted these kind of metadata. Other users just use these metadata to tag item.

2. Unmanged Metadata or Folksonomies: These unmanged metadata are not managed centrally. If a user find that managed metadata can’t meet his requirement then he can add his own metadata to the item.

Few others terms are described below:

Term: Term is keyword or phrase that can be associated with a content. Simply we can say term is a single node in taxonomy.

Term Sets: A Collection of terms. So simply we can say term sets as a subset of taxonomy.

Term Store: A store (say database) which store all terms.

Managed Keywords: Managed keyword is a kind of metadata field which supports only non-hierarchical list called keyword-set. Managed Keyword columns allows to select from existing metadata store. It also allow to add the keyword to the store if it doesn’t exist already. This is actually an way to implement the Folksonomies.

How to define Term sets and Terms?

Go to Central administration site –> Application Management –> Manage Service Applications (under service applications). Then click Managed Metadata Service and you’ll be landed in the term store properties page. In that page move your mouse on the “Managed Metadata Service” and you’ll get a popup menu “New Group” as shown below:

Figure 1: New metadata group.

Once you create a new group you can create term set and term. In the following figure I have defined one group (Sales System) then I have defined two Term sets (IT Product and Region). Then I have defined different terms under the term sets.

Figure 2: Term sets and terms under group.

Use terms in list/library column

To assign metadata you need to create a column of type “Managed Metadata” for your list or libraries. If you go to add a column to your list you’ll find a new column type “Managed Metadata”. In that column you have two options to set your managed metadata.

Use a Managed term set: With this option user will just be able to select from available terms. User will not be able to add new terms in the term set. As shown in the following figure, this column will only allow the terms defined in the term set “IT Product”</LI>

Customize your term set: This option is for “Managed Keywords”. With this option selected user will be able to add new term in the custom term set. when you will select this option a new term set will be created for you.</LI>

I had created a column ProductType that is bound to the term set “IT Product”. When I landed to add new item page and started typing in the Product Type field, the suggestions were presented as shown below:

Figure 3: Metadata auto suggestion

Summary

In summary, the shared metadata service will help much to manage metadata from a central place. Also taxonomy will help better content tagging and better content organization.

SharePoint 2010 Error: System.Web.HttpException: Directory 'C:\inetpub\wwwroot\wss\VirtualDirectories\80\_catalogs\masterpage' does not exist.

2010-11-07T21:42:00.000+02:00

I had got the error when I tried to use pagemethods in SharePoint. I had registered the AjaxControlToolkit namespace in masterpage and then I replace ScriptManager with AjaxControlToolkit’s ToolkitScriptManager as shown below:

<ajaxToolkit:ToolkitScriptManager id="ScriptManager" runat="server" 
EnablePageMethods="true" EnablePartialRendering="true" 
EnableScriptGlobalization="false"   EnableScriptLocalization="true"/>

The problem was I enabled the pagemethods by setting EnablePageMethos to true. Disabling the pagemethods fixed the issue. However I didn’t explore why there’s the error if pagemethods is enabled.

So disable the pagemethods by setting EnablePageMethods=”false” and then then error will disappear…

SharePoint 2010–Dialog Box Close Not postback

2010-11-05T21:39:00.000+02:00

void btnOK_Click(object sender, EventArgs e)
{
this.Context.Response.Write("<script type='text/javascript'>window.frameElement.commitPopup();</script>");
this.Context.Response.End();
}

SharePoint 2010 Error: Cannot make a cache safe URL for "1031/styles/Themable/corev4.css", file not found. Please verify that the file exists under the layouts directory.

2010-11-04T21:40:00.000+02:00

I had to take backup from my client’s production site to make some analysis in my local server. So I took backup and restored the site in local server. Restored was successful. Then I changed the site collection administrator of the restored site as it was still pointing to the production server’s site collection administrator.

Then I tried to browse the site and found the interesting error “Cannot make a cache safe URL for "1031/styles/Themable/corev4.css", file not found. Please verify that the file exists under the layouts directory.” The very first thing I noticed the path contains 1031. Anyone can guess that this is language id and thought came to my mind is that my client SharePoint site not in English. The production site was in German language and when I restored the site, its looking for resources in German language ID folder.

Then I download the language pack from MSND and refreshed the browser. It worked like magic….

SharePoint 2010 - Adding a custom control to the Team Site Wiki Page Template ( wkpstd.aspx ) programmatically

2010-11-01T09:29:00.000+02:00

This is maybe my last post about the Team Site Wiki Page customization with the aim of exceeding its limitations. This time we are going to customize the unique template ( wkpstd.aspx) by replacing the control that renders the editable content by a custom one.
In this post example, we will take advantage of the use of this custom control to render not editable additional contents, for instance, a header and a footer that could be the same for a specific Wiki Page Library. Of course, we are not going to really customize the template, but we are going to use a delegate control to replace the control at runtime.

Here are the screen shots of the result:

We can see a non editable Header and Footer on the Team Site Wiki Page

In edit mode these additional contents are not rendered, but we can add new content as usual

And of course, after having saved the page, the new content is rendered wtih the non editable Header and Footer.

Steps required

If you look at the Team Site Wiki Page template, wkpstd.aspx, you can see the control that is rendering the editable content/

<SharePoint:EmbeddedFormField ID="WikiField" FieldName="WikiField" ControlMode="Display" runat="server" />

We are first going to create a custom EmbeddedFormField control

Then, we are going to use a delegate control to replace the native EmbeddedFormField control by the custom one in order to have the control on the wiki page content rendering.

1 - Creating a custom EmbeddedFormField control

Here is the screen shot of the Visual Studio solution:

and the custom control source code:

using System;

using System.Collections.Generic;

using System.ComponentModel;

using System.Linq;

using System.Text;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebControls;

using Microsoft.SharePoint.Security;

using System.Security.Permissions;

using System.Diagnostics;

namespace CustomControls

{

[SharePointPermission(SecurityAction.LinkDemand, ObjectModel = true), AspNetHostingPermission(SecurityAction.LinkDemand, Level = AspNetHostingPermissionLevel.Minimal), SharePointPermission(SecurityAction.InheritanceDemand, ObjectModel = true), AspNetHostingPermission(SecurityAction.InheritanceDemand, Level = AspNetHostingPermissionLevel.Minimal)]

public class EmbeddedFormFieldCustom : FormField

{

public EmbeddedFormFieldCustom()

{

Debug.WriteLine("EmbeddedFormFieldCustom: " + "constructor...");

}

private string _header = "";

private string _footer = "";

public string Footer

{

get { return _footer; }

set { _footer = value; }

}

public string Header

{

get { return _header; }

set { _header = value; }

}

[PersistenceMode(PersistenceMode.InnerDefaultProperty)]

public string Content

{

get

{

SPFieldMultiLineText field = base.Field as SPFieldMultiLineText;

if (field != null)

{

Debug.WriteLine("EmbeddedFormFieldCustom: " + "SPFieldMultiLineText ok");

return field.GetFieldValueAsHtml(this.ItemFieldValue, base.ListItem);

}

Debug.WriteLine("EmbeddedFormFieldCustom: " + "SPFieldMultiLineText non ok");

return base.Field.GetFieldValueAsHtml(this.ItemFieldValue);

}

set

{

Debug.WriteLine("EmbeddedFormFieldCustom: " + "set Content");

this.ItemFieldValue = value;

}

[SharePointPermission(SecurityAction.Demand, ObjectModel = true)]

protected override void Render(HtmlTextWriter output)

{

Debug.WriteLine("EmbeddedFormFieldCustom: " + "rendering..");

output.AddAttribute(HtmlTextWriterAttribute.Id, this.ClientID);

output.Write(_header);

output.RenderBeginTag(HtmlTextWriterTag.Div);

base.Render(output);

output.Write(_footer);

output.RenderEndTag();

}

2 - Replacing the standard control by the custom one by using a delegate control

Here is the delegate control source code:

<%@ Control Language="C#" ClassName="WikiPageCustomLink" %>

<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls"

Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Assembly Name="CustomControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0f4e5a441a5ac20c" %>

<%@ Import Namespace="Microsoft.SharePoint" %>

<%@ Import Namespace="System.Diagnostics" %>

Control ctrlTofind = null;

CustomControls.EmbeddedFormFieldCustom myCustomEmbeddedFormField = null;

protected void FindControl(Control aControl, string ID)

{

if (aControl.HasControls())

{

foreach (Control aControl2 in aControl.Controls)

{

if (aControl2.ID == ID)

{

ctrlTofind = aControl2;

}

else

{

FindControl(aControl2, ID);

}

else

{

if (aControl.ID == ID)

{

ctrlTofind = aControl;

}

protected override void OnInit(EventArgs e)

{

if (!IsPostBack)

{

Debug.WriteLine("onInit");

if (Page.TemplateControl.ToString().Contains("ASP.WKPSTD_ASPX"))

{

try

{

int ctrlNumber = this.Page.Controls.Count;

foreach (Control aControl in this.Page.Controls)

{

FindControl(aControl, "WikiField");

}

myCustomEmbeddedFormField = new CustomControls.EmbeddedFormFieldCustom();

myCustomEmbeddedFormField.Header = "<span style='color:red;font-size:12pt' >This is my Custom header, not editable</span>";

myCustomEmbeddedFormField.Footer = "<span style='color:red;font-size:12pt' >This is my Custom footer, not editable</span>";

Control updatePannelContentTemplateContainer = ctrlTofind.Parent;

UpdatePanel myUpdatepannel = (UpdatePanel)updatePannelContentTemplateContainer.Parent;

int index = 0;

for (int i = 0; i < updatePannelContentTemplateContainer.Controls.Count; i++)

{

if (updatePannelContentTemplateContainer.Controls[i].ID == "WikiField")

{

index = i;

}

updatePannelContentTemplateContainer.Controls.Remove(ctrlTofind);

updatePannelContentTemplateContainer.Controls.AddAt(index, myCustomEmbeddedFormField);

myCustomEmbeddedFormField.FieldName = "WikiField";

myCustomEmbeddedFormField.ID = "WikiField";

myCustomEmbeddedFormField.ControlMode = Microsoft.SharePoint.WebControls.SPControlMode.Display;

}

catch (Exception ex)

{

Response.Write("<br>error : <br>" + ex.Message);

Response.Write("<br>error : <br>" + ex.StackTrace);

}

base.OnInit(e);

}

</script>

The secret is to load the custom control only if it is not a post back, since the embedded control itself seems to be used only for displaying the content.

SharePoint 2010 - Modal Pop-Up for a Unique Content Type

2010-10-28T00:58:00.000+03:00

To continue the conversation with the modal pop up window, I was asked the following great question:

“What if your list has different content types, each having their own form? Is there a way to make this pop-up specific to the form of a certain content type?”

The answer is yes it is quite easy to link the pop-up modal window to a unique content type: You would use the same approach but you would add in the Content Type ID to the end of the URL string:

<a onclick="javascript:NewItem2(event, "http://sitename/_layouts/listform.aspx?PageType=8&ListId={49E3BDCF-9C06-413D-A7B8-413F2E8F6B0D}&ContentTypeId=0x01005C9243AA25668B4CAACB42C41B0D360600052ECA5C

1544864D9F9B7BF90A874A4F&RootFolder=");
javascript:return false;"
href="/_layouts/listform.aspx?PageType=8&ListId={49E3BDCF-9C06-413D-A7B8-413F2E8F6B0D}&ContentTypeId=0x01005C9243AA25668B4CAACB42C41B0D360600052ECA5C

1544864D9F9B7BF90A874A4F&RootFolder="
target="_self">
Add a Unique Content Type Item</a>

To find the custom content type ID, simply click on the list settings, within the content type section right click on the custom content type and then click on properties. Within the Address URL, the ID is at the very end after the “ctype=”

Simply Replace the above blue ID with your own custom one. This will allow you to have links to custom content types within the same list and not have to worry about the default content type settings.

SharePoint 2010 - Ways to extend the SharePoint Modal Window

2010-10-27T00:57:00.000+03:00

So in my last post I simply wanted to show an input form in a SharePoint 2010 modal window. This got my creative juices flowing and I wanted to experiment a little. I found out that you can easily display anything in the Modal window that you wanted.

Web Site: Bing
<a onclick="javascript:NewItem2(event, "http://www.bing.com");
javascript:return false;" href="http://www.bing.com/" target="_self">Show Bing In Modal Window</a>

Image
<a onclick="javascript:NewItem2(event, "http://sitename/Images/image.png");
javascript:return false;" href="/images/image.png/" target="_self">Show Image</a>

Video/Games
This does not really work since most video’s open up in a separate application like Window Media Player and not within the browser. However you can use things like flash .swf files to show in the modal window.
<a onclick="javascript:NewItem2(event, "http://www.microsoft.com/games/gamesforwindows/games/madagascar2/Mad2_Final_ENU.swf");
javascript:return false;" href="http://www.microsoft.com/games/gamesforwindows/games/madagascar2/Mad2_Final_ENU.swf" target="_self">Flash Game</a>

So basically you can show basically anything that you have a link to and can be visible within a browser.

Enjoy, and let me know what creative things you have placed in your modal window…

D.I.S.C Kişilik Envanter Testi Sonuçlari–2010 için Yenilenmiştir

2010-10-26T22:41:00.000+03:00

Kariyer.net sitesi üzerinde yapılan kişilik envanter testini doldurduktan sonra aldığım sonuçlar aşağıdaki gibi çıkmıştır. Sizin gerçek hareketleriniz ve davranışlarınızı tespit etme konusunda oldukça başarılı bir test. Benim sizlere tavsiyem 10 dakikanızı ayırıp bu testi doldurmanızdır.

•    Girişimci, iş geliştirici, değer katıcıdır.
•    Önemli kararlarda yer almak, lider olmak ister.
•    Sonuç odaklıdır, hızlı karar alır.
•    Sorumluluk taşır, direkt hareket eder ve konuşur.
•    İşbitirici ve otoriterdir; hatta bazen sert ve agresif olabilir.
•    İşleri hızlandırır, kolaylaştırır.
•    Katılımcıdır, göz önünde olmayı, meydan okumayı sever.
•    Fırsatları iyi değerlendirir, rakiplerini karşışına alabilir, rekabetçidir.
•    Başkalarının düşüncelerini önemser son kararı kendisi verir.
•    Olması gerektiği yerde her zaman bulunur.
•    Başkalarının kendisini dinlemesini ister.
•    Konsantrasyonunun kesilmesini istemez.

2009 yılı için hazırlanmış olan teste ise linkten ulaşabilirsiniz.

SharePoint 2010 - How To: Create Hyperlink to Modal Pop-Up Form

2010-10-26T00:56:00.000+03:00

I was asked by a client recently if there was a way to create a hyperlink to a New Item Form anywhere within a site but still get the rich experience of the Modal pop-up window that grays out the background. (Note this is for SharePoint 2010 Only…)

I basically took the code directly from the “Add new item” and the “Add Document” link within the list view.

What this allows you to do is simply add in the following code to any content editor web part, Master page, or Page Layout in any site collection and display the form to be filled out. The user will get the nice experience of the modal window and not have to navigate away from their current page.

This could be used for example a feedback form that is included in the master page so whenever someone wants to give feedback it is always going back to a central list. The only that is required for you to know is the List ID and the site name.

Full Code For a List Item:
<a onclick="javascript:NewItem2(event, "http://SiteName/_layouts/listform.aspx?PageType=8&ListId={83747BB4-49C6-4181-B4A3-F8C6B611846D}&RootFolder=");
javascript:return false;"
href="/_layouts/listform.aspx?PageType=8&ListId={83747BB4-49C6-4181-B4A3-F8C6B611846D}&RootFolder="
target="_self">
Submit Feedback</a>

Full Code for a Library Item:
<a href="http://SiteName/_layouts/Upload.aspx?List={94AC86A8-6774-4822-A197-A98542251678}&
RootFolder=" onclick="javascript:NewItem2(event, "http://SiteName/_layouts/Upload.aspx?List={94AC86A8-6774-4822-A197-A98542251678}&RootFolder=");
javascript:return false;"
target="_self">
Upload a Document</a>

What you need to change:
URL: Change “SiteName” to your URL
List ID: Change the list ID to your custom list/library ID

To find out the list/library ID, simply navigate to the list/library you want to display and then click on list settings
Look at the end of the URL.
You will get something similar to this: ~~%7B~~94AC86A8%2D6774%2D4822%2DA197%2DA98542251678~~%7D~~
Remove the first %7B and the last %7D
Then change all %2D’s to “-“
So the final would be 94AC86A8-6774-4822-A197-A98542251678

You could also add in an image right within the <a> tag and make a nice button for users to click on. Once you have customized the code you can now simply add the code to any page on the site and you will get the following results:

Site Collection 2 hyper linking to a list on Site Collection 1

SharePoint 2010 - How To: Hide Left Side Navigation on Home Page

2010-10-25T00:54:00.000+03:00

I was recently asked: "How can I hide the side nav bar on the main homepage layout ?? I want to be able to use the side NAV with in the team site etc etc, but I don't want it on the front page.. "

There are a couple of ways to do this in SharePoint 2010. If you are using a non-publishing site you can add a Content Editor Web Part to the page and add the following to the HTML Source.

<Style>
body #s4-leftpanel
{
display: none;
}
.s4-ca
{
margin-left: 0px;
}
</style>

Basically the CSS above hides the left navigation Div, and then sets the content area to not have a left margin.

Once you are done, simply modify the web part and hide it on the page.

If you are using a publishing site for your homepage simply add the same styles specified above to a custom page layout. That way if you have a need for other pages that do not need the left side navigation you can re-use the page layout.

Visual guide to Windows Live ID authentication with SharePoint 2010 - part 1

2010-10-24T12:34:00.001+03:00

Using Windows Live ID as login provider for SharePoint is a really huge thing. It makes the scenario for public facing web sites, extranets etc. much more easier, for instance there is no need to maintain passwords and users in the same degree. For SharePoint 2007 there is no native support for this, so I built a custom Live ID login provider (available at http://spwla.codeplex.com), but SharePoint 2010 has native support for claims based access. And that is what's on the menu for tonight...

This post, and the subsequent ones, will show you how to enable Windows Live ID on a SharePoint 2010 farm (SPF or SPS). I will do a visual approach using a lot of screenshots. It has not been an easy path since there are no official guidance on this subject (at the time of this writing), so I'm going to throw in a couple of steps where you can fail miserably while setting it up. Big thanks to Paul Schaeflein who also walked the hard path and took some hits to get this to work! Although there are a couple of available blog posts out there on this issue, some of the are very sparse on the details (why?) and some even contains faulty instructions. Just to safe up on this - the instructions works on my machines and I've been able to reproduce these steps a number of times. If you have any suggestions or comments, just leave them here and I'll try to (get someone to) answer them...

So what are we waiting for, let's get the party started. I have to warn you - if you don't like certificates - stop reading!

Background

While I will explain more in details as we move along I think it is important to have a little heads up on claims based access and Windows Live ID. First of all (passive) claims based access is based on the simple scenario where a client/user (subject) trying to access a site (also called Relying Party/RP). This RP has distributed the login procedure to one or more trusted parties called Identity Providers (IP). In our case SharePoint is the RP and Live ID is the IP and you of course are the subject. When the subject tries to access the RP, the subject will be redirected to the IP where the actual logon process is taking place. By attaching cookies to the response and redirecting the user back to the RP with a set of (encrypted) claims the RP can finally authenticate the user. For a better understanding I recommend you to read A guide to Claims-based Identity and Access Control.

Windows Live ID (WLID) will take care of the login and send back a unique ID to the SharePoint site. This unique ID is the only claim WLID will give you. (Unfortunately you cannot get the correct e-mail address or the name of the user.) SharePoint will first verify the validity of the encrypted security token (containing the claims) before actually starting the AuthN and AuthZ process using the unique ID as username in SharePoint. You will later see how we give access to these unique ID's.

Another important thing to keep in mind is that WLID have two "zones"; INT and PROD. The PROD zone is what you normally use when logging in to Hotmail etc. The INT zone is used for development and testing and have a completely different account database, so you need to have accounts in the INT zone to continue, more about this in a little bit. You cannot skip the INT zone, you have to register your site there first before applying for approval in the PROD zone.

The steps provided here is only for the INT environment. For PROD it is basically the same and the post is long enough as it is...

Registering the site

Before even starting to configure the SharePoint site we need to register our site for usage with Windows Live ID. This is done using the Microsoft Service Manager web application located at http://msm.live.com/. You log in to this service using you normal (PROD) Windows Live ID account.

In the left menu click on Register Your Site (1). This will bring up the Register Your Site page where you should enter the name of your site, use a descriptive name (2) and the DNS Name of your site (3). The DNS Name is important! Here you must specify a DNS Name, which we will later change into a URI, or rather URN. Write something random such as wictor.live.

The DNS Name will be used as a SAML Audience when the security token is sent back and it will be verified by SharePoint. According to the SAML specification the audience must be a URI (a URN or URL). If you use a URL then WLID will for some reason remove the protocol from the audience when sending it back to the RP and SharePoint will throw an exception ([InvalidOperationException: This operation is not supported for a relative URI.] System.Uri.GetLeftPart(UriPartial part)). This might change in the future.

Finally you have to specify that you will use Windows Live ID (4). Click Submit to continue.

You will get a confirmation screen. Click Yes to confirm and proceed to the next step

After a few seconds you will be presented with the results. If anything goes wrong you need to go back and edit your registration accordingly - but it shouldn't if you followed these steps.

Click on the Go to Manage Your Site link. In the drop-down (1) select the site that you just registered and then click on the Modify Editable Site Properties link (2).

The next screen allows you to edit the properties of the site. First of all check the Show advanced properties check box to enable more options.

First we need to rename the Domain name (1) and set our real domain name to use. Then we need to replace the dummy DNS name (2) with a URN, in this case I use urn:wictorslivesite:int. Remember not to specify a URL, it just won't work as of now. The third thing to edit is the Default Return Url (3); this must be an HTTPS url pointing to the /_trust/default.aspx page, for instance https://extranet.corp.local/_trust/default.aspx. This is the URL that the IP will post back the results to. Finally we have to edit the Expire Cookie URL (4). Just fix the URL and never mind the actual page (you can implement such a page if you feel to at a later time).

Then scroll down a bit on the page until you reach Override Authentication Policy, this step is crucial. Select MBI_FED_SSL in the drop-down. And when you're done click Submit (at the top of the page).

Verify and confirm your changes by clicking Yes on the next screen. Take a screenshot and/or notes all these changes.

That's it. Your site is now configured. Actually you can configure a bunch of more features here - but stick to these as of now...

Let's move on to the SharePoint Server.

Certificates

Claims based authentication uses certificates for encryption and signing and you have to trust the certificate of the IP on your SharePoint servers. The following steps must be done on all WFE's in the farm.

To get the IP certificate; browse to federation metadata URL: https://nexus.passport-int.com/federationmetadata2/2007-06/federationmetadata.xml (this is for the INT zone). Then copy the inner text from the first X509Certificate node. Open up the Notepad application and paste the text and then save the file as LiveID-INT.cer. Make sure that you only get the inner text of the element.

Now you have the certificate in a file and you need to import it to the correct locations on the SharePoint Server(s). It is actually required to be stored locally on three different locations. Open mmc.exe and add the Certificates snap-in. When you select to add it you must first select to use the Computer Account to manage the accounts for and select to use the Local computer as computer to manage.

Expand the tree until you reach SharePoint > Certificates then right-click on the node and Select All Tasks > Import...

In the import wizard that appears locate the LiveID-INT.cer file you just created and then click Next > Next > Finish. That's the first one.

Repeat this procedure for the Trusted Root Certification Authority and Trusted People. Don't worry if you don't have a Certificates sub-node. It will be created when you import the certificate.

Now we're one step closer and it is time to get dirty with some PowerShell. You could of course have done this step using PowerShell, but I leave that for another crafty blogger to show how... Just remember to do this on all WFE's!

Create the STS provider

To create the Trusted Identity Token Issuer, that we will use to configure as the login provider for the Web Applications, we fire up PowerShell. This step will not be that "visual" as the previous ones, since none of these commands can be run using the standard SharePoint user interface. I guess it's just a matter of time until someone makes a neat add-on with these simple commands...

I'll give you the script first and then explains all the involved steps:

1: asnp microsoft.sharepoint.powershell
2: $realm = "urn:wictorslivesite:int"
3: $certfile = "C:\Temp\LiveID-INT.cer"
4: $rootcert = Get-PfxCertificate $certfile
5: New-SPTrustedRootAuthority "Live ID INT Root Authority" -Certificate $rootcert
6: $emailclaim = New-SPClaimTypeMapping 
    -IncomingClaimType "http://schemas.xmlsoap.org/claims/EmailAddress" 
    -IncomingClaimTypeDisplayName "http://schemas.xmlsoap.org/claims/EmailAddress" 
    -SameAsIncoming
7: $upnclaim =  New-SPClaimTypeMapping 
    -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims
/nameidentifier" 
    -IncomingClaimTypeDisplayName "UPN" 
    -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn"
8: $authp = New-SPTrustedIdentityTokenIssuer -Name "LiveID INT" 
    -Description "LiveID INT" -Realm $realm -ImportTrustCertificate $certfile 
    -ClaimsMappings $emailclaim,$upnclaim -SignInUrl "https://login.live-int.com
/login.srf" 
    -IdentifierClaim "http://schemas.xmlsoap.org/ws/2005/05/identity/claims
/nameidentifier"

The first line just loads the SharePoint PowerShell Snapin (1), asnp is a shortcut for Add-PSSnapin and saves you a cpl of keystrokes. Then we set three local properties; realm corresponds to the DNS Name (that is the URN), certfile points to the location where you saved the LiveID-INT.cer file and the rootcert is the certificate loaded in as an object.

Make sure not to make any typos in the claims URN's - been there, done that!

Then we add the certificate to a SharePoint trusted Root Authority, using the New-SPTrustedRootAuthority cmdlet. You can verify that it is correctly imported by going to Central Adminitration > Security > Manage Trust:

Then we need to create two claims mappings; one for e-mail (line 6) and one for the identifier (line 7). The claim mappings defines how the incoming claims are mapped to the SharePoint tokens. These two claims are then sent into the New-SPTrustedIdentityProvider cmdlet (line 8) and here is where the magic happens. This cmdlet creates a new trusted identity provider with a name and description, we instruct it which claims mappings to use and which claim is the identifier claim. We are also specifying the URL for the WLID (INT zone) login page.

Once these commands are executed, we are ready to head on over to the UI and create a Web Application. By all means, if you prefer to do the rest using PowerShell, feel free to do it.

If you are fiddling back and forwards using different registered Live ID services, you can switch the Realm using the DefaultProviderRealm property of the Trusted Identity Provider object (authp). Don't forget to call Update() on the object... You can only have one provider for each service, even if the realms differ.

Create the Web Application

Fire up Central Administration and go to Application Management > Manage web applications. Click New to create a new Web Application.

First of all you need to select to use Claims Based Authentication. Then enter a Name for your web application, use the port 443 (SSL) and (in this case) configure the host header to match the domain name that you entered while registering the WLID service. Just standard stuff so far.

Under Security Configuration make sure that you select Use Secure Sockets Layer (SSL).

Under Claims Authentication Types leave Windows Authentication enabled if you like, but make sure to check Trusted Identity Provider checkbox and then check the LiveID INT provider, the one we created using PowerShell.

Once done click OK to create the Web Application.

We're almost there just a few steps more...

Create the Site Collection

Once the Web Application is created you can directly click on the Create Site Collection link. Enter name and description for the site, and also specify which template to use.

Now it is time to give some permissions to this site collection. Assume that we did not select any Windows Authentication when creating the Web Application, then we can only add Live ID users, right?

If you don't have a WLID account in the INT domain it is time to get one now. Open up a new browser window. Go to https://accountservices.passport-int.net/ and sign up for a new account or sign in using one of your existing INT accounts. (Stability of the INT domains are not 100% :-). When you have signed up or logged in click on Credentials and then View your unique ID.

You will now see a screen with your unique ID; write it down, copy it or remember it...

Close the browser and return to the Central Administration where you started creating a Site Collection. Now paste or write this unique ID and append @live.com in the Primary Site Collection Administrator. But, make sure to convert all characters to lowercase, otherwise you will not be able to log in later:

Then click OK to create the Site Collection.

Final configurations

Before browsing to the site we need to make some final adjustment in the IIS. To be precise we will add a certificate to the site. You can use a certificate that you have acquired for your site or when testing just use a Self-Signed, which I will show you here.

To create a Self-Signed certificate start the IIS Manager and select the server. In the Features View double-click the Server Certificates module.

Then click Create Self-Signed Certificate in the Actions bar to the right and follow the instructions. Mostly next-next-finish.

The final configuration is to use this certificate on the Web Application. Choose the Web Application you created in SharePoint in the IIS Manager (1), then click on Bindings (2), select to edit the only binding you have (3) and choose the SSL certificate you just created in the drop-down (4). Click OK and close everything down.

That's it! Let's see how it behaves...

Taking it for a test drive

Now open up a web browser and go to the web application you have created using the domain name you specified when creating it, make sure to use https. You should see the standard warning in the browser that the certificate is not valid (add it as trusted if you want to skip this warning in the future), otherwise just click the continue link.

If you have several authentication providers you will see the new SharePoint 2010 Sign In screen with a drop-down where you can choose the authentication provider you would like to use to log in with. If you only have one, in this case the WLID, you will be redirected to the WLID Log In screen - the same will happen if you select LiveID in the drop-down.

If you get an error stating We're unable to complete your request, like below, you most certainly have not used the correct Realm when creating the trusted identity provider using PowerShell. Make sure that the Realm and the DNS Name in the Live ID Service Manager are exactly the same, case sensitive and all.

The Windows Live ID sign in screen should look as expected, just the same as logging in to other Live ID services. Enter your INT username and password (remember this is still the INT zone).

If you remembered your username and password correctly you will very soon see the beautiful SharePoint 2010 scenery:

Note that your username and display name will be exactly the same as the unique id you have for that user. How to fix this is scheduled for a later post :)

Next steps

So, there you have it. It's a handful of steps to complete and you have to make sure not to mistype anything. I will continue this series with some more info that could be of great use when setting this up - hopefully not as long as this one though...

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

2010-10-24T10:40:00.000+03:00

I am examining the SharePoint 2010 architecture in order to find the best ways to customize the Wiki Pages of a Team Site. In this post we will focus on two kinds of elements:

The SharePoint 2010 Ribbon and how are populated the Styles and Markup Styles Menu
Some of the SharePoint 2010 templates, including the v4.master Master Page and the Team Site Wiki Page Template, wkpstd.aspx

Important: do not mistake a Wiki Page of a Team Site for a Wiki Page of an Enterprise Wiki. They are totally different since an Entreprise Wiki is a kind of publishing site, and a Wiki Page of an Enterprise Wiki can be based on different Wiki Page Templates.

In this post, I am examining the Wiki Pages for a Team Site so that this information can be used for SharePoint foundation 2010.

For more information about Enterprise Wiki:

Enterprise Wikis overview (SharePoint Server 2010)
ContentTypeId.EnterpriseWikiPage Property
SPC: Customizing Enterprise Wikis in SharePoint 2010 with Gail Jacoby & Ted Pattison

1 - Managing the Styles and Markup Styles Menu Items

One important thing to kow is that these items are populated dynamically, client side, using the JavaScript loaded by the SharePoint 2010 Ribbon, and I am now going to show how to see it in action.

1.1 - Debugging the SharePoint 2010 Ribbon

We are going to debug the JavaScript of the Ribbon while using IE8 in order to see how the menu are populated, so let us start by adding a new Style menu item.
Add an HTML form Web Part in a SharePoint 2010 wiki page in order to be allowed to insert some HTML within the page and add an style tag with a ms-rteStyle so that the menu can be able to load this style as a new item.

Then open the Tools menu of IE8 and locate the Developer Tools

Open the Developer Tools and hit the Script Tab

There is not much scripts loaded for the moment but activate the Edit mode for the page.

You will notice that activating the Edit Mode leads to the load of several files, but locate the following:

sp.ui.rte.debug.js

Open it
locate this line (12890) RTE.StyleRuleUtility.$u = function($p0, $p1, $p2)
and set the following breakpoint:

sp.ui.rte.debug.js -->

Place a breakpoint in front of
the first line
if (!$p0.startsWith('.')) {

The goal now is to force SharePoint 2010 to load the styles, so Save & Close the page, empty the temporary internet files, add a custom style to one of the CSS files.

Now, hit the "Start Debugging" button in the Developer Tools
then, go back to the wiki page and activate the Edit Mode.

The tool starts debugging and stops on the breakpoint.
Continue to press F11, and you will be taken to a resource file that seems to validate some parameters, then when you come back to the script, you notice that a variable has been initialized to look for the ms-rte class elements.

Then the url for the first css file is retrieved

Then, this is AMAZING! the JavaScript of the Ribbon is loading the content of the CSS file by using an AJAX request with the XMLHttpRequest object.
You will notice the responseText variable with all the CSS classes loaded!

Then it is the turn of the wiki.css

and the corev4.css

finally I had a custom styles CSS, and you will see that I have placed the ms-rteStyle-Normal inside of it

Then the JavaScript starts loading the classes available within the page, first these two that are located in the <head> tag:

.ctl00_PlaceHolderMain_Bottom_0
{ border-color:Black;border-width:1px;border-style:Solid; }

.ctl00_wpz_0
{ border-color:Black;border-width:1px;border-style:Solid; }

</style>

Then the JavaScript finds the custom style I have placed within the HTML Form web Part

and stores the inner and outer html of it

and the class name

Conclusion: as the styles are loaded dynamically from all the places where you can store CSS classes, we don't have to worry about coding to manage the Styles and Markup Menus items, but just to focus on the good way of storing and referencing our CSS.

1.2 - Storing and registering the SharePoint 2010 CSS

- At the wiki page level.

With MOSS 2007, when creating a portal, we were sometimes hesitating between using the collaborative part of SharePoint (the lists, the pages, the Web Part pages), and the integrated CMS (Web Content Management). Both had benefits and drawbacks, and it seems that, in SharePoint 2010 the Wiki Pages of a Team Site are now closer to a WCM Page Layout than ever because the layout of the page has been dramatically improved.

However, the wiki pages of a Team Site don't seem to have been designed to be customized, and it is perfectly normal because there is a customizable version of the Wiki Pages in Sharepoint Server 2010: the Wiki Pages of the Enterprise Wiki.

Now this precision has been made, let us examine the limitations of the Wiki Pages for a Team Site:

First of all if you unghost a Wiki Page, the page UI will be spoiled by a premanent warning message.

Second, you cannot create other Wiki Page Templates and make them available for the end users when they want to create pages although it is possible with the Page Layouts and for the Wiki Pages of the SharePoint 2010 Enterprise Wiki.
Why?
When you create a Wiki Page within a team Site by using the SharePoint 2010 UI, the product use the method
SPFileCollection.Add( String,SPTemplateFileType)

It is the only method that can produce ghosted files within SharePoint 2010. The available tempates are:

StandardPage
WikiPage
FormPage

and as you can see in the following screen shot of relector, the reference to the Wiki Page template is hardcoded, so there always will be only one template for the wiki pages of a Team Site, the one that is located at DocumentTemplates\wkpstd.aspx

Of course you can customize the Wiki Pages of a Team Site and let them in a ghosted state by deploying them with a feature, but you will have to upgrade and activate your feature each time you need another custom wiki page, and you will lose the benefit of letting end users create the pages by themselves

This is, at first, a bit puzzling, especially because, as the JavaScript of the SharePoint 2010 Ribbon is loading dynamically the CSS classes to populate the Styles and Markup menus within a Wiki Page, we were expecting to a native way of referencing the CSS at the level of the Wiki Page without that it could be modified by a contributor. Here again, we cannot do it although it is possible wiht a Page Layout and for the Wiki Pages of the Entreprise Wiki.

However, if you want to reference a custom CSS for one or several wiki pages of a Team Site at the level of the page without modifying the template, I have found a means to do it using a delegate control.

Unfortunately, it will not be enough to use this trick to manage the items of the Styles and Markup since you have first to REMOVE those that are delivered with the Out Of The Box version of SharePoint 2010 ie the native SharePoint 2010 ms-rteStyle and ms-rteElement classes (ms-rteStyle-Normal, ms-rteStyle-Highlight, ms-rteStyle-Byline,...., H1.ms-rteElement-H1, .ms-rteElement-H1, etc.) that are located within the corev4.css file.
(You could try anyway to use this trick to programmatically specify an alternate CSS for the site at the level of the Wiki Page, but I think it is not a good idea).

- At the Master Page level

Because we will need most of the time when branding a SharePoint 2010 site using wiki pages, to at least, remove the native ms-rteSyle and ms-rteElement classes located in the Themable/corev4.css folder and to replace them by our customn classes, we will use most of the time an alternate CSS, either by specifying it within the SharePoint Server 2010 UI, or programmatically for SharePoint 2010 foundation.

It is a very bad idea when wanting to replace the SharePoint 2010 corev4.css by a custom one to remove the CSSLink control within a Master Page and to render a custom LINK tag or to hardcode it because the CSSLink web control renders some other useful LINK for the search, and the new SharePoint 2010 dialogs, and also manages the new SharePoint 2010 themes.
So, in SharePoint 2010, when referencing any CSS it becomes quite mandatory to use the CSSLink and the CSSRegistration controls, because of the new themes.

SharePoint 2010 - Enable Small Social Buttons

2010-10-24T00:51:00.000+03:00

To convert the large social buttons to smaller ones you simply have to modify the following:

Within your custom Master Page search for: “GlobalSiteLink3”

Simply Add “-mini” to the control ID

Original Large Control:
<SharePoint:DelegateControl ControlId="GlobalSiteLink3" Scope="Farm" runat="server"/>

New Small Control ID:
<SharePoint:DelegateControl ControlId="GlobalSiteLink3-mini" Scope="Farm" runat="server"/>
If you want to make the small buttons horizontal versus vertical simply add the following to your custom CSS:

.ms-mini-socialNotif-Container{
white-space: nowrap;
}

Enjoy!

SharePoint 2010 - Issues with moving search into top ribbon bar

2010-10-23T00:48:00.000+03:00

I was recently on a project where there was a requirement to have many items in the main navigation. There was not an option to consolidate these into smaller groups. The idea was to move the search box up into the top ribbon bar.

This would allow for more horizontal space for the navigation items. However in my attempt to move the search I found a little gotcha. I selected the search control in SharePoint Designer and moved it right above the welcome navigation control code.

Wrapped the control in a div tag and temporarily added an inline style of float left.

I saved the master page and then checked out what it looked like. The search was moved up correctly but it was not until I used IE8 dev toolbar to check for compatibility in IE7.

As you can see below in IE7 the search, and welcome link/drop down is no where to be seen and the ribbon tabs got all squished.

After doing some testing in IE7 mode an inline style gets applied to the ms-cui-TabRowRight with “Display: none”

I am not 100% why this is, but if I try to put the search anywhere else in the ribbon it just does not show… So I guess this is more of a warning to the designers out there. If you are thinking about putting the search in the top ribbon bar in your design comps know that there might be some issues with browser compatibility.

So what I ended up doing is moving the search to the left of the Social Notification tags. Wrapped it in a <td> tag and called it a day. The client was happy with the results since they were still able to have their navigation items and the search moved to a different location.

Thanks Fur Sadik Ulker!!!

SharePoint 2010 - Tab Web Part JQuery, Java, and CSS

2010-10-22T00:47:00.001+03:00

I have been searching for a simple tab web part for SharePoint but mostly came up empty handed… I was looking for something that a user can easily drag and drop a web part onto a specific tab within the page. There are quite a few free tab web parts out there but most of them were not just quite what I wanted. I checked out the following Tab web part solutions.

Easy Tabs: From Path To SharePoint
- Pro: The tabs automatically take the name of the web part.
- Con: There is no option to add more than one web part per tab, and the User Interface is not that intuitive.
Zone Tabs: From MSDN

Pro: You have a lot of options for tab customization
Con: It’s a web part that you have to install on the server. From what I remember it’s not that easy to re-arrange the web parts on the page.

I finally found this article from Bits Of SharePoint Site:
http://www.bitsofsharepoint.com/ExamplePoint/Site/TabPage.aspx

His code was exactly what I needed. All I had to do was make a few adjustments of the HTML and create my own tab styles. The process to get this to work is you simply edit the page layout in the source link below (Code is already included in header control) and change the name of the tabs to what ever you want. You can have as many tabs as you want but if you go over 8 you will need to add more web part zones.

Once you have your tabs specified, simply choose what design you want. I created a few example designs that will get you started. To change the designs simply remove the commented out referenced style sheet and comment out the one you don’t want. You can place the support files anywhere you want but the links in the page layout point to the 12 hive: /_layouts/1033/styles/tabstyles/

For inspiration, I looked around the web and found a few unique styles that I wanted to replicate, and I also came up with a few of my own.

Design 1: MSN

Design 2: Yahoo

Design 3: WebMD

Design 3a: WebMD Alt

Design 4: Rounded Tabs 1

Design 5: Rounded Tabs 2

Drop me a comment if you found this useful!

SharePoint 2010 - Content Query for Blog Posts

2010-10-21T00:46:00.000+03:00

I hope this post will help many of you feel comfortable with using the Content Query Web Part.

In this post I will walk you through the process of creating a content query web part and configuring it to show custom field types. I will also give details on how to use XSLT to stylize and format the data being pulled.

I will be using the following scenario as an example. Say that you had a site collection with a top level publishing site. This publishing site would display a the most recent blog posts from all blog sites within its own site collection.

To solve this problem we will use a Content Query Web Part and a customized ItemStyle.xsl using XSLT.

Please note that the “SharePoint Server Publishing Infrastructure” needs to be enabled at the site collection to display the content query web part.

Step 1: Add a Content Query Web Part to Page

Navigate to the site that you want the blog posts to show up and click on edit page.
Under Editing Tools in the Ribbon, Click on insert > Web Part
Under the Content Rollup Category Click on Content Query
Then Click on the Add Button
Now that you have a CQWP on the page edit the web part

Expand open the “Query” properties
Since we will be just showing blog post in this query choose the following
- List Type: Posts
- Content Type Group: List Content Types
- Content Type: Post
You should get a result like the following.

Next we will configure the web part to pull in additional values from the blog posts.
- Title – linked to post
- Date – with standard formatting
- Body – Rich text
- Author
- Number of Comments
- Categories

Step 2: Configure Web Part

Click on web part arrow and choose “Export”
Save the .webpart file to your desktop
Edit the “Content_Query.webpart” file in Notepad
Search for "CommonViewFields”
Replace the default “<property name="CommonViewFields" type="string" />” with the following:

<property name="CommonViewFields" type="string">Title, Text;PublishedDate, DateTime;Body, RichHTML;Author, Text;NumComments, Lookup;PostCategory, Lookup;</property>

Here are the available Field Types that can be used
- Text
- Note
- Number
- Currency
- Integer
- Boolean
- DateTime
- Threading
- Lookup
- Choice
- URL
- Counter
- RichHTML
- Image
When creating your own there are a few rules.
- First off you need to separate each custom field type by a semi colon (Ex: Title, Text;Editor, Text)
- There cannot be a space after the semi colon
Save the .webpart file
Edit the page again and choose Inster Web Part
It’s a little hard to find but click on the Upload a Web Part and browse for the custom .webpart file.

Click on Upload
Now when you click on Insert webpart you will see a category of imported webparts.
Click on Add button.
Now you will not see a difference but now the webpart has been configured to display these custom columns.

Step 3: Configure ItemStyle.xsl

Click on View All Site Content > Style Library > XSL Style Sheets
Download the itemstyle.xsl file
Add the following to the top of the file

xmlns:ddwrt="http://schemas.microsoft.com/WebParts/v2/DataView/runtime"

At the very bottom of the xsl file add the following template

<xsl:template name="BlogPost" match="Row[@Style='BlogPost']" mode="itemstyle">
        <xsl:variable name="SafeLinkUrl">
            <xsl:call-template name="OuterTemplate.GetSafeLink">
                <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
            </xsl:call-template>
        </xsl:variable>
        <xsl:variable name="DisplayTitle">
            <xsl:call-template name="OuterTemplate.GetTitle">
                <xsl:with-param name="Title" select="@Title"/>
                <xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
            </xsl:call-template>
        </xsl:variable>
        <div class="custom_posttitle">
            <xsl:call-template name="OuterTemplate.CallPresenceStatusIconTemplate"/>
            <a href="{$SafeLinkUrl}" title="{@LinkToolTip}">
              <xsl:if test="$ItemsHaveStreams = 'True'">
                <xsl:attribute name="onclick">
                  <xsl:value-of select="@OnClickForWebRendering"/>
                </xsl:attribute>
              </xsl:if>
              <xsl:if test="$ItemsHaveStreams != 'True' and @OpenInNewWindow = 'True'">
                <xsl:attribute name="onclick">
                  <xsl:value-of disable-output-escaping="yes" select="$OnClickTargetAttribute"/>
                </xsl:attribute>
              </xsl:if>
              <xsl:value-of select="$DisplayTitle"/>
            </a>
        </div>
    <xsl:variable name="StartDate">
        <xsl:value-of select="ddwrt:FormatDateTime(string(@PublishedDate), 1033, 'g')" />
    </xsl:variable>
    <div class="custom_date">
            <xsl:value-of select="$StartDate" />
    </div>
    <div class="custom_description">
            <xsl:value-of select="@Body" disable-output-escaping="yes" />
    </div>
    <div>
        <table class="custom_postdetails" border="0" cellpadding="0" cellspacing="0">
            <tr>
                <td class="custom_author">
                        By: <xsl:value-of select="@Author" /> |
                </td>
                <td class="custom_comments">
                        Comments: <xsl:value-of select="@NumComments" /> |
                </td>
                <td class="custom_category">
                        Category: <xsl:value-of select="@PostCategory" />
                </td>
            </tr>
        </table>
    </div>
</xsl:template>

Save the file and upload it to back up to the style library

Step 4: Apply Custom XSL style to content query

Modify the Content Query Web Part again
Expand open The Presentation Category
Choose the custom “BlogPost” style
Save the page and you should now see the blog post with the following data and format.

SharePoint 2010 - SharePoint Designer 2010 Edit in Advanced Mode

2010-10-20T00:43:00.000+03:00

In SharePoint Designer 2007 you can simply open up any type of file you wanted even if it did not reside in SharePoint. Well now things have change for 2010… Now you are forced to open up a SharePoint site before attempting to open up a file that resides outside of SharePoint. If you try before opening up a site you get the following error message: “You must first open a Web site before editing external Web pages…” Not really sure why they changed this maybe they want to ensure that you are not downloading the free SharePoint designer and simply using it as a HTML editor for non-SharePoint sites…

Anyways that is not the focus of this post. I also noticed that SharePoint designer tricks you to thinking that you cannot edit pages. Say you want to modify a file that does reside in SharePoint. By Default it will open up in a read only view (HTML) and will not allow you to change the file. It will have a orange like highlight to areas that are not editable.

So the trick is to right click on the document and choose the option “Edit File in Advanced Mode”.

Now you can edit the file as you wish!

Hope this helps! If you know of a better way please leave a comment.

SharePoint 2010 - Themes

2010-10-19T00:42:00.000+03:00

As you all know SharePoint has a new theme engine for 2010. You can do cool things such as create a theme in PowerPoint, export it and then import it into SharePoint 2010, click apply and you got a custom theme. One aspect that I could not find documented is the definition of when you choose a color for a particular element what is it really changing?

If you modify the theme for a site you can use the picker to choose a OOTB or custom theme. Or you have the ability to choose your own color scheme via the following elements.

My approach: Make each element white to start with and then one by one add color and document the results. Just for kicks here is what it looks like when it is completely white… (not a color scheme I would recommend…) I will be using a red color: #C12345 for testing.

Here are the details for each one of the elements above:

Text/Background- Dark 1 (41 Classes)

Page Title Hyperlink Text
Hover Text
VB Body Text
Site Action Menu Text
Left Navigation Links Text
Site Setting Page Text Headers

Text/Background - Light 1 (37 Classes)

Body Background
Toolbar Background
Quick Launch Borders
Web Part Header Background
Site Action Menu Background
Site Action/Welcome Text Color
Pop-Up Window Background

Text/Background - Dark 2 (43 Classes)

Top Banner Background
Left Navigation Header Text
Recycle Bin/View All Site Content Text
I Like/Tags Notes Text
Library Column Text
Site Action Drop Down Border
Breadcrumb Current Location Text
List Description Text

Text/Background - Light 2 (19 Classes)

Browse Tab and hover Background
Title Container Background
Top Links/Header 2 Background
Quick Launch Background
Web Part Adder Background

Accent 1 (10 Classes)

Quick Launch Hover Text
Top Link Selected Tab

Accent 2 (4 Classes)

.ms-error
Rich Text Colored Heading 2 Text Styles

Accent 3 (9 Classes)

Rich Text “Caption” Style Text Color

Accent 4 (5 Classes)

Border Under Web Part Selector

Accent 5 (3 Classes)

Rich Text Colored Heading 4 Text Styles

Accent 6 (3 Classes)

Rich Text Highlight background color

Hyperlink (12 Classes)

Toolbar Text Color
VB Body Hyperlink Text
a:link Class Text Color
Web Part Title Hyperlink Text (Not Visited)

Followed Hyperlink (2 Classes)

.ms-WPBody a:visited
a:visited

I hope this post will help you when you decide to create your own theme via the above elements. If you create your own theme you can simply view the source of the page and there will be a unique CSS style sheet reference “_themes/16/corev4-8digithex.css?ctag=#”. Just copy that url and past it to the end of your site string http://yoursitename.com/ and you can download the custom file.

Yazgeliştir Gönüllüleri Toplantısı

2010-10-18T22:54:00.000+03:00

Türkiye’de yazılım geliştirme alanında çalışanların paylaşım noktası olan Yazgeliştir’i takip eden herkesi 23 Ekim Cumartesi günü düzenleyeceğimiz Yazgeliştir Gönüllüleri etkinliğine bekliyoruz. Bu etkinlikte Yazgeliştir yönetimi ve editörleri ile tanışıp, Yazgeliştir ile ilgili son gelişmeler ve gelecek planlarından haberdar olacaksınız. Ayrıca Yazgeliştir ekibi olarak görüş ve önerilerinizi dinliyor olacağız. Tüm bunların yanısıra etkinlikte yazılım geliştirme alanındaki son yenilikler içerikli bir sunum da olacak. Microsoft İstanbul ofisinde saat 13:00’te başlayacak etkinliğimizin program detaylarını aşağıda bulabilirsiniz:

Tarih:
23 Ekim 2010 Cumartesi, 13:00 – 17:00

Program:
13:00 – 14:00 Yazgeliştir yönetimi ile tanışma
14:00 – 15:00 Son gelişmeler ve 2011 planları
15:00 – 15:45 Açık tartışma
16:00 – 16:45 Yazılımcılar İçin Yenilikler – Tamer Öz

Yer:
Microsoft İstanbul Ofisi
Bellevue Residence Levent Mahallesi
Aydın Sokak. No:7 Levent,
34340 İstanbul/Türkiye

SharePoint - Style Individual Navigation Items for 2007 & 2010

2010-10-18T00:40:00.000+03:00

Here is a simple yet effective way to stylize individual top navigation items for SharePoint 2007 & 2010 just using CSS. SharePoint 2010 will need a slight modification to the master page but the same effect can be achieved. See bottom of post for 2010 implementation.

To start off with lets review how this can be accomplished for 2007. SharePoint 2007 provides a unique ID for each note in the navigation.

1st Tab: Dedicated as your default Home or root node
- ID: zz1_TopNavigationMenun0
2nd Tab: This is the first child node from the root
- ID: zz1_TopNavigationMenun1
3rd Tab: This is the second child node from the root
- ID: zz1_TopNavigationMenun2
4th Tab: This is the third child node from the root

ID: zz1_TopNavigationMenun3

See the pattern… It keeps going and going. Here is what it looks like from the IE DOM Explorer in IE8:

So you might ask well what can I do with this unique ID? Well here is a quick sample of what you can do. Its not pretty but it shows off that you can have a custom Icon, background color, font, etc. for each node in the navigation.

Here is the CSS and OOTB Icon references that I used to create the above design. So how does it work? Basically it combines the trigger of the unique ID and attaches it to the class of “ms-topnav a”. You will notice that I had to do a funky bit of css to fill in the background behind the arrow for news.

.ms-topnav{
border: none;
background-color: transparent;
background-image: none;
font-weight: bold;
}
#zz1_TopNavigationMenun0 .ms-topnav a{
background-image: url(/_layouts/images/newshomepage.png);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #006699;
border: 1px #006699 solid !important;
padding:18px 20px 0px 80px;
height: 54px;
color: #FFF;
}
#zz1_TopNavigationMenun1 .ms-topnav a{
background-image: url(/_layouts/images/PLICON.PNG);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #FF9933;
border: 1px #FF9933 solid !important;
padding:18px 20px 0px 80px;
height: 54px;
color: #FFF;
}
#zz1_TopNavigationMenun2 .ms-topnav a{
background-image: url(/_layouts/images/ANNOUNCE.PNG);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #336633;
border: 1px #336633 solid !important;
padding:18px 20px 0px 80px;
height: 54px;
color: #FFF;
}
#zz1_TopNavigationMenun2 .ms-topnav td{
background-color: #336633;
}
#zz1_TopNavigationMenun3 .ms-topnav a{
background-image: url(/_layouts/images/ReportCenter.png);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #990000;
border: 1px #990000 solid !important;
padding:18px 20px 0px 80px;
height: 54px;
color: #FFF;
}
#zz1_TopNavigationMenun4 .ms-topnav a{
background-image: url(/_layouts/images/SMT_LARGE.PNG);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #660066;
border: 1px #660066 solid !important;
padding:18px 20px 0px 80px;
height: 54px;
color: #FFF;
}
#zz1_TopNavigationMenun5 .ms-topnav a{
background-image: url(/_layouts/images/categories.png);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #999;
border: 1px #999 solid !important;
padding:18px 20px 0px 80px;
height: 54px;
color: #FFF;
}

So how do you do this for SharePoint 2010…

Well first you will need to modify the master page and do a search for “UseSimpleRendering="true"”. This basically tells SharePoint to render the navigation using a clean unordered list <UL> <LI> format.

Since this is so clean, it does not have any unique ID’s attached to it like it did in SharePoint 2007.

So if you change it to false: UseSimpleRendering="false" you can clearly see that each node now has a unique ID:

So if we simply take the same approach for 2007 we can get similar results. You will notice the only difference in the ID’s from 2007 to 2010 is that they put in a “V4” after the word “Menu” and before the “n#”

2007 ID: zz1_TopNavigationMenun0
2010 ID: zz1_TopNavigationMenuV4n0

You can also remove the “ms-topnav” since it is not needed. You should end up with something like this:

Below is the CSS that I used to achieve the design above for SharePoint 2010. Remember you need to make that modification to the master page noted above to get this to work. Also notice that I kept the “a” reference at the end of each ID.

#s4-topheader2{
border: none;
background-color: transparent;
background-image: none;
font-weight: bold;
height: 54px;
padding-bottom: 5px;
}
#zz1_TopNavigationMenuV4n0 a{
background-image: url(/_layouts/images/newshomepage.png);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #006699;
border: 1px #006699 solid !important;
padding:18px 20px 18px 80px;
color: #FFF;
}
#zz1_TopNavigationMenuV4n1 a{
background-image: url(/_layouts/images/PLICON.PNG);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #FF9933;
border: 1px #FF9933 solid !important;
padding:18px 20px 18px 80px;
color: #FFF;
}
#zz1_TopNavigationMenuV4n2 a{
background-image: url(/_layouts/images/ANNOUNCE.PNG);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #336633;
border: 1px #336633 solid !important;
padding:18px 20px 18px 80px;
color: #FFF;
}
#zz1_TopNavigationMenuV4n3 a{
background-image: url(/_layouts/images/ReportCenter.png);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #990000;
border: 1px #990000 solid !important;
padding:18px 20px 18px 80px;
color: #FFF;
}
#zz1_TopNavigationMenuV4n4 a{
background-image: url(/_layouts/images/SMT_LARGE.PNG);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #660066;
border: 1px #660066 solid !important;
padding:18px 20px 18px 80px;
color: #FFF;
}
#zz1_TopNavigationMenuV4n5 a{
background-image: url(/_layouts/images/categories.png);
background-repeat: no-repeat;
background-position: -40px -3px;
background-color: #999;
border: 1px #999 solid !important;
padding:18px 20px 18px 80px;
color: #FFF;
}

Enjoy!

SharePoint 2010 - CSS references in Master Pages

2010-10-17T00:31:00.000+03:00

Here are some of the most common ways to reference your custom CSS for SharePoint 2010. One key change over 2007 is the ability to specify After=”corev4.css” in the CssRegistration to make sure your custom CSS is referenced after the OOTB corev4.css file.

<SharePoint:CssLink runat="server" Version="4"/>
Note: Default OOTB
Output Order:

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/Themable/corev4.css"/>

<SharePoint:Theme runat="server"/>
Note: If a theme is enabled
Output Order:

<link rel=”stylesheet” type=”text/css” href=”/_themes/[UniqueCounter#]/corev4-[u=UniqueHex#].css?ctag=[UniqueCounter#]”/>

<SharePoint:CssRegistration name=”customfolder/samplecustom.css” runat=”server”/>
Note: Alternate CSS on Server but comes before corev4.css
Output Order:

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/customfolder/samplecustom.css"/>
<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/Themable/corev4.css"/>

<SharePoint:CssRegistration name=”customfolder/samplecustom.css” After=”corev4.css” runat=”server”/>
Note: Alternate CSS on Server and comes after corev4.css.
Output Order:

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/Themable/corev4.css"/>
<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/customfolder/samplecustom.css"/>

<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/samplecustom.css %>" After="corev4.css" runat="server"/>
Note: Alternate CSS In SharePoint Database for sites without publishing enabled
Output Order:

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/Themable/corev4.css"/>
<link rel="stylesheet" type="text/css" href="/Style%20Library/emc_2010_custom.css"/>

<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/samplecustom.css %>" After="corev4.css" runat="server"/>
Note: Alternate CSS In SharePoint Database for sites with publishing enabled
Output Order:

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/Themable/corev4.css"/>
<link rel="stylesheet" type="text/css" href="/[sitename]/Style%20Library/en-US/Themable/Core%20Styles/emc_2010_custom.css"/>

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/customfolder/samplecustom.css"/>
Note: Alternate CSS on Server by using the standard link rel. Does not need the After attribute…
Output Order:

<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/Themable/corev4.css"/>
<link rel="stylesheet" type="text/css" href="/_layouts/1033/styles/customfolder/samplecustom.css" />

SharePoint 2010 - Change Search Icon with Just CSS

2010-10-16T00:37:00.000+03:00

I created a post awhile ago on how to change the SharePoint site logo via CSS so that you don’t have to modify the titlegraphic.gif file on the file server or change it via the UI for every site to make a global change.

I have a simple solution that changes the search GO icon from the standard to something more custom with just CSS.

The icon is not specified via the master page so you will not be able to change it there.

<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server">
<SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" />
</asp:ContentPlaceHolder>

You might be tempted take the route of changing the following files on the server and replacing them with your own custom ones. But I have an alternative that works just as well and you don’t have to mess with any of these base Image files.

GOSEARCH.GIF ICONGO01.GIF ICONGO02.GIF ICONGO03.GIF

Upload your custom images to a sub folder within the following directory:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\YourCustomFolder

Then in your custom CSS simply place the following CSS:

td.ms-sbgo{
background-color:transparent;
padding-left:3px;
padding-right:3px;
padding-bottom:0px;
padding-top:0px;
border:solid 0px #949494;
}
td.ms-sbgo a{
padding: 0px 0px 0px 0px !important;
margin: 0px 0px 0px 0px !important;
}

td.ms-sbgo a{
background-image: url(/_layouts/images/yourcustomfolder/custom_search.gif);
background-repeat: no-repeat;
background-position: top left;
}
td.ms-sbgo a img{
    visibility: hidden;
    height: 17px;
    width: 17px;
}

You will simply just have to change the folder name, image name, and the height and width of the image to be specific to you and you should be good to go. The result should look something like this:

Happy Customizing!

SharePoint 2010 - Alternative way to Change Site Logo

2010-10-15T00:34:00.000+03:00

OOTB SharePoint allows you to change the logo of the page from the default: titlegraphic.gif to another image by going into site settings > Title, Description, and Icon.

The following method is a way to add a new logo to your page with just CSS. If you wanted to make this more global you will need to use an alternate method to override the default CSS classes.

Upload your new logo to either the server or to a list on your site. Add a Content Editor webpart to the page. Add in the following to the source viewer.

<STYLE>
.ms-titleimagearea{
background-image:url("/_layouts/images/xyzcorp.gif");
background-repeat: no-repeat;
background-position: top left;
}
#ctl00_onetidHeadbnnr0{
visibility: hidden;
height:130px;
width: 126px;
}
</STYLE>

In the example above I have uploaded the xyzcorp.gif logo to the images folder on the server. Make sure you modify the elements above in bold green: logo name, height, and width (of logo). Save the page and you should now have the new logo on the page.

Redirect in SharePoint using SPUtility.Redirect

2010-10-14T20:50:00.001+03:00

Redirect in SharePoint using SPUtility.Redirect
I was looking at the Redirect method in the SPUtility class. Besides the url, this method also takes a parameter of type SPRedirectFlags. I was wondering when to use the values of this enumeration. The MSDN documentation does help a bit, but not very much. I asked on Twitter if anyone knew the meaning of these values. Within minutes, Anders answered and pointed me in the right direction. One of the examples of why I love Twitter!

The signature of the Redirect method is:

public static bool Redirect(string url, SPRedirectFlags flags, HttpContext context)

There is an overload that also takes the queryString as a parameter. The SPRedirectFlags enumeration has these values:
-CheckUrl
-Default
-DoNotEncodeUrl
-DoNotEndResponse
-RelativeToLayoutsPage
-RelativeToLocalizedLayoutsPage
-Static
-Trusted
-UseSource
-Source url

If UseSource is part of the flags parameter of the Redirect method, the url to which the user is redirected will be read from the querystring of the original request (context parameter). The new url will be the value of one of these querystring parameters:

-Source
-NextUsing
-NextPage
If one of these parameters has a value, the new url will be validated. Validation is done by the IsUrlSafeForRedirect method of the Request property of the current SPWeb. The url in the querystring of the original request needs to be a relative url. See the samples below.

If this url is not valid, or the UseSource parameter resulted in an empty string, the url parameter that was originally passed will be used.

Static url

If Static is part of the flags parameter, the url is considered relative. Depending on the presence of RelativeToLayoutsPage in the flags parameter, the url is relative to the ´_layouts´. If this enumeration value is present, SharePoint checks the flags parameter for the presence of RelativeToLocalizedLayoutsPage. If this is present, a new absolute url to the localized ‘_layouts’ folder is constructed. If not, the url is constructed to the root of the ‘_layouts’ folder. The layouts url is the url of the current SPWeb, followed by ‘_layouts’ and the Language of the current SPWeb. If constructing this url fails for whatever reason, the url will be the url of the current SPSite. If required, the value of SPGlobal.ServerCulture.LCID is added to the url.

Absolute url

If Static is NOT part of the flags parameter, the user will be redirected to the value of the url parameter, after validating the url. If Trusted is part of the flags parameter, the url is always valid. If Trusted is not available, it depends on the outcome of the IsUrlSafeForRedirect method of the Request property of the current SPWeb whether or not the url is valid.

Encoding

The last step is before the user is redirected is the encoding. If DoNotEncodeUrl is NOT present in the flags attribute, the url is first encoded using SPHttpUtility.UrlPathEncode.

Samples

Below you will find a number of samples. Each sample starts with the sample code for SPUtility.Redirect. This code is tested in a web part. The 3 lines below that sample show the results of calling the redirect. The first column contains the page url that contains the web part. The second column contains the result of the redirect.

SPUtility.Redirect(http://newsite, SPRedirectFlags.Default, HttpContext.Current);
http://intranet/site1/Pages/default.aspx    no redirect
http://intranet/site1/Pages/default.aspx?Source=http://newsite    no redirect
http://intranet/site1/Pages/default.aspx?Source=/news    no redirect

SPUtility.Redirect("/news", SPRedirectFlags.Default, HttpContext.Current);
http://intranet/site1/Pages/default.aspx    http://intranet/news
http://intranet/site1/Pages/default.aspx?Source=http://newsite    http://intranet/news
http://intranet/site1/Pages/default.aspx?Source=/news    http://intranet/news

SPUtility.Redirect(http://newsite, SPRedirectFlags.Static, HttpContext.Current);
http://intranet/site1/Pages/default.aspx?Source=http://newsite no redirect
http://intranet/site1/Pages/default.aspx http://newsite

SPUtility.Redirect(http://newsite, SPRedirectFlags.UseSource, HttpContext.Current);
http://intranet/site1/Pages/default.aspx    no redirect
http://intranet/site1/Pages/default.aspx?Source=http://newsite    no redirect
http://intranet/site1/Pages/default.aspx?Source=/news    http://intranet/news

SPUtility.Redirect("images/approve.gif", SPRedirectFlags.Static | SPRedirectFlags.RelativeToLayoutsPage | SPRedirectFlags.RelativeToLocalizedLayoutsPage, HttpContext.Current);
http://intranet/site1/Pages/default.aspx    http://intranet/site1_layouts/1033/images/approve.gif
http://intranet/site1/Pages/default.aspx?Source=http://newsite    http://intranet/site1_layouts/1033/images/approve.gif
http://intranet/site1/Pages/default.aspx?Source=/news    http://intranet/site1_layouts/1033/images/approve.gif

There are a few members of the enumeration that I did not describe, because I was not able to find out how these are used.

SharePoint 2010 Client Object Models – The ECMAScript library

2010-10-10T20:58:00.000+03:00

a managed .NET API for building client applications using a SharePoint object model.
a managed Silverlight object model.
an object model to be used in Javascript, the ECMAScript library.
For developers this is an important step forward. Until now, developing SharePoint applications using an object model was limited to applications running on the server. For client applications we had to rely on web services and the RPC protocols. Using these 3 new models, it will be much easier to create client applications. And the reach of our applications will be bigger, because they are very likely to also run on the new SharePoint Online. The three object models are a limited sub set of the server object model. Most objects, properties and methods of the site collection (SPSite) and it’s underlying structures are available in the new models.

In this article I will show you an example of a custom ASPX page that will use the Javascript library. It is a page that runs in the LAYOUTS folder. It shows all users that have direct permissions on the current site. By clicking a user name, the page will show me more information about that user. By selecting a user and one of the available SharePoint groups, the page will add the user to that group. After doing that, the page will remove the permissions for the user.

Showing the users and the user groups is done in server side code. Showing user information and moving the user’s permissions to the group is handled by javascript using the ECMAScript library.

Step 1 – Show the users and groups

The ASPX page loads the lists with users and groups in the OnLoad of the page. It creates a collection of custom objects and sets these collections as the datasource for the Repeater controls. The code snippet below shows how the users are loaded:

   1: SPWeb web = SPContext.Current.Web;
   2: List<SharePointUser> users = new List<SharePointUser>();
   3: foreach (SPRoleAssignment assignment in web.RoleAssignments)
   4: {
   5:     if (assignment.Member is SPUser)
   6:     {
   7:         SPUser user = (SPUser)assignment.Member;
   8:         SharePointUser usr = new SharePointUser(user.ID, user.Name);
   9:         users.Add(usr);
10:     }
11: }
12: listUsers.DataSource = users;
13: listUsers.DataBind();
The snippet below shows the ASPX code for the repeater that shows the users:

   1: <asp:Repeater ID="listUsers" runat="server">
   2:     <HeaderTemplate>
   3:     <h3>Users with direct permissions on this site</h3>
   4:     </HeaderTemplate>
   5:     <ItemTemplate>
   6:     <li style="list-style-type:none">
   7:         <input type="checkbox" id="selectUser<%# DataBinder.Eval(Container.DataItem, "ID") %>" name="selectUser" />
   8:         <a href="javascript:getUserInfo(<%# DataBinder.Eval(Container.DataItem, "ID") %>);">
   9:             < %# DataBinder.Eval(Container.DataItem, "Name") %>
10:         </a>
11:     </li>
12:     </ItemTemplate>
13: </asp:Repeater>
For every user in the collection, a hyperlink is rendered. When the link is clicked, javascript function “selectUser” is called. This function takes the ID of the user as parameter

Step 2 – Preparing the page for using the ECMAScript library

The ECMAScript library is available in a number of JS files in the LAYOUTS folder. The main file is SP.js. When you include this file in the APSX page using a ScriptLink control, all other required JS files are loaded automatically. This MSDN page shows all relevant files. By linking SP.js to your page, the SP namespace is registered. This is the SharePoint namespace that contains all objects. If you are going to build code using this library, you will very likely need this MSDN Page to reference what object, properties and methods are available. The SharePoint js files are minified (‘crunched’ in the SDK) versions. This makes them hard to read and use for debugging. Therefore every js file also has a ‘debug’ equivalent in the same folder. By opening sp.debug.js you will be able to see what is available in the SP namespace.

The snippet below show how to prepare the ASPX page:

   1: <SharePoint:ScriptLink
   2:     Name="sp.js" LoadAfterUI="true" Localizable="false"
   3:     runat="server" ID="ScriptLink1" />
Step 3 – Getting the user information

As we have seen in step 1, clicking a user’s name fires the javascript function ‘selectUser’. This function is shown in the snippet below.

   1: function getUserInfo(userID) {
   2:     var clientContext = new SP.ClientContext.get_current();
   3:     var web = clientContext.get_web();
   4:     var userInfoList = web.get_siteUserInfoList();
   5:     var camlQuery = new SP.CamlQuery();
   6:     camlQuery.set_viewXml('<View><Query><Where><Eq><FieldRef Name=\'ID\'/>' +
   7:                           '<Value Type=\'Number\'>' + userID + '</Value></Eq>' +
   8:                           '</Where></Query><RowLimit>1</RowLimit></View>');
   9:     this.collListItem = userInfoList.getItems(camlQuery);
10:     clientContext.load(collListItem);
11:     clientContext.executeQueryAsync(
12:         Function.createDelegate(this, this.onQuerySucceeded),
13:         Function.createDelegate(this, this.onQueryFailed));
14: }
As in server side code, we first need to get the SharePoint context. Because our page is an ASPX page running in the LAYOUTS folder, it is always in context of the current SharePoint site. In all 3 new client object models, the SharePoint context is represented in a ClientContext object. In line 2 of the snippet above, we’re getting the current SharePoint context. The next few lines look pretty familiar if you are used to SharePoint server side programming. We are getting a reference to the User Information List of the current site. Next we create a CAML query to find the list item for the user that was selected, and we load the items based on that query from the list. The big difference with the server side object model, is that we did not yet have any contact with SharePoint. Although we have called the getItems method of the list, our collection is not yet loaded. This happens when we load the collection in line 10 and execute the query using clientContext.ExecuteQuery in line 11. This gives you the option to minimize the number of roundtrips to the server from your client code. This makes SharePoint client programming different from server side programming. You need to do more thinking about what objects and properties to use when. It makes sense to load as many objects you need, before calling ExecuteQuery once, to actually get the objects from the server.

In the sample above, you see another difference between client and server side programming. The ECMAScript library is, as the Silverlight API, asynchronous. The ExecuteQuery method takes 2 parameter, the functions that will be called in both a success and a failure scenario. The snippet below shows the ´success´ function of my sample page:

   1: function onQuerySucceeded(sender, args) {
   2:     var item = collListItem.itemAt(0);
   3:     var profile = item.get_item('Notes');
   4:     var pictureUrl = item.get_item('Picture').get_url();
   5:
   6:     var userImage = document.getElementById('userImage');
   7:     userImage.src = pictureUrl;
   8:     var profileDiv = document.getElementById('userProfile');
   9:     profileDiv.innerHTML = profile;
10: }
This code loads the first item from the collection, get the values of the Notes and Picture

Step 4 – Move the user to the group

Last part of this article show how to remove the user permissions and add the user to the selected group. When a groupname is clicked, the javascript function moveSelectedUsersToGroup is called and the ID of the group is passed as parameter. The snippet below shows this function:

   1: function moveSelectedUsersToGroup(groupID) {
   2:     var users = document.getElementsByName('selectUser');
   3:     this.clientContext = new SP.ClientContext.get_current();
   4:     this.web = clientContext.get_web();
   5:     var groups = web.get_siteGroups();
   6:     var group = groups.getById(groupID);
   7:     var groupUsers = group.get_users();
   8:     for (i = 0; i < users.length; i++) {
   9:         if (users[i].checked) {
10:             var id = users[i].id.replace(/selectUser/, '');
11:             var siteUsers = web.get_siteUsers();
12:             var user = siteUsers.getById(id);
13:             groupUsers.addUser(user);
14:             var assignments = web.get_roleAssignments();
15:             var assignment = assignments.getByPrincipalId(id);
16:             assignment.deleteObject();
17:             clientContext.executeQueryAsync(
18:                 Function.createDelegate(this, this.addUsersSucceeded),
19:                 Function.createDelegate(this, this.onQueryFailed));
20:         }
21:     }
22: }
What this does before the query is executed to SharePoint, is:

get a reference to the SharePoint group
find the selected user in the site users
add the user to the selected group
find the role assignment for the selected user
delete the role assignment for the selected user
By submitting the query to SharePoint, all these actions are all executed at once in 1 roundtrip to the server. If this action is successful, the javascript function addUsersSucceeded is called. This function has not specical function, it notifies the user about the outcome of the process.

In this article we have seen how to use one of the three new client object models, the ECMAScript library. Although programming client applications is now a lot easier, and is more like programming the server, the are some conceptual differences that are important to understand. The next few articles will show you some examples on how to get started using the other two client object models.

Adding and Deploying Solutions with PowerShell in SharePoint 2010

2010-09-29T13:22:00.000+03:00

Visual Studio 2010 makes it really easy to add and deploy solutions when you are developing (the F5 experience), but you may eventually want to deploy those solution packages elsewhere then on your development machine. We can still use the stsadm tool, but that is effectively considered deprecated now in favor of PowerShell.

To get started with PowerShell, run the SharePoint 2010 Management Console located in your Microsoft SharePoint 2010 Products folder on your start menu. This automatically loads the Microsoft.SharePoint.PowerShell snappin so that we can execute SharePoint commands.

[code:xml]
Add-SPSolution c:\codefolder\SharePointSolution.wsp
Install-SPSolution –Identity SharePointSolution.wsp –WebApplication http://yoursharepointurl -GACDeployment
Update-SPSolution –Identity SharePointSolution.wsp –LiteralPath c:\codefolder\SharePointSolution.wsp –GACDeployment
Uninstall-SPSolution –Identity SharePointSolution.wsp –WebApplication http://yoursharepointurl
Remove-SPSolution –Identity SharePointSolution.wsp

Also cool is getting your SharePoint version by using Powershell

function global:Get-SPFarm
{
return [Microsoft.SharePoint.Administration.SPFarm]::Local
}
$farm = Get-SPFarm
$farm.BuildVersion

The result looks like

Major Minor Build Revision
----- ----- ----- --------
14 0 4536 1000</DIV>