English:

Few month ago I have introduced RemoteStsAdm, a PowerShell module that enable you to execute StsAdm.exe remotely. StsAdm.exe is a command line administration tools for SharePoint. Unfortunately to run StsAdm, one must log-in to SharePoint server member – since the tool can not be executed remotely. RemoteStsAdm is to answer this problem, allowing admin to execute StsAdm remotely. You can download the source code from MSDN Galery here or read the original article in previous post here. 

Yesterday, I have released ImportPSModule that will easy PowerShell module distribution, allow update notification and configuration. The RemoteStsAdm PowerShell module is now available via NuGet, so that you don’t need to download and extract manually. All will be done seamlessly, and whenever we got script update – you will get notified as soon as you open PowerShell session.

So what do you wait for, open PowerShell session and type following:

Import-PSModule RemoteStsAdm 

You may already know PsGet by Chaliy or PsGet by Anurse for PowerShell module distribution. They have created PowerShell module distribution mechanism with different approach.

Chaliy uses PowerShell script approach and customized module directory. Everytime you want to distribute your PowerShell module, you have to fork his github project to update Directory.xml content. Even tough the instruction in https://github.com/chaliy/psget/wiki/How-to-add-your-module-to-the-directory is very clear, however I think there is risk of incorrect Directory.xml modification.

Anurse uses PowerShell manifest approach and standard NuGet package to download and put module in appropriate location. In this case you can create a NuGet package containing PowerShell files and publish it to NuGet repository. Using his module, you will be able to get PowerShell module from NuGet repository right to your console. I like this approach because it uses standard NuGet package and publishing process. However, sometimes I want to be able to register the new module in my profile. I also want to ensure that I always use latest PowerShell Module package – ie. update local module automatically when there is new module in NuGet repository.

So then, I started to create Import-PSModule a PowerShell script module that will give you functionalities such as:

1. Importing PS Module from NuGet repository
2. Load imported module to current session
3. Register imported module to current user profile or all user profile
4. Un-register imported module from current user profile or all user profile
5. Auto-update imported module when user start PowerShell session

To start using the module, start PowerShell session and type following

(new-object Net.WebClient).DownloadString("http://blog.libinuko.com/wp-content/plugins/download-monitor/download.php?id=1") | iex 

The script will perform following actions:

1. Download latest ImportPSModule from central NuGet repository.
2. Install the package to desired location. If you choose to install in User-Module or Global-Module, all future packages will be installed under Module path. If you choose to install in other folder, then all future package will be installed within installation folder.
3. Load the ImportPSModule to the memory. It will also  download latest NuGet.CommandLine package if you don't have in your system.

So what do you waiting for? Start to install the module and publish your PowerShell module in NuGet repository. But don't forget TAG "PSModule" to your NuGet package.

If you want to validate InstallPSModule.ps1, please click here InstallPSModule (116) .

English

The STSADM.exe is command-line tool for administration of Office SharePoint Server (SharePoint 2007, SharePoint 2010). It is installed on the same location as SharePoint Products and Technologies location: %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin (for SharePoint 2007) or %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin (for SharePoint 2010). You must be Farm Administrator to be able to run the tool.

By default, the STSADM.exe must be executed locally since it will access SharePoint Object Model. It is also necessary for the tools to connect to the SQL Database using credential of the user who executes it. Therefore, normally the Administrator must remote-login to the SharePoint server before he/she can run the tools.

Remote execution of STSADM.exe using PowerShell Invoke-Command cmdlet faces double-hop challenges. This occurs when SQL Database for the farms is installed on different machine than the SharePoint server. The credential in theInvoke-Command session can not pass through to the SQL Database without configuring delegation in the WinRM services.This module solve double-hop problem without configuring CredSSP.

Download the module here:
http://code.msdn.microsoft.com/Remote-StsAdm-in-6fec24b8

English

Either you’re SharePoint geeks or newbie, intellisense is always helpfull to provide inline guidance. Previously we need to configure Visual Studio environment manually to get very basic information about CAML schema.

After all, we always need better and better tools for the job.  Thanks to John F. Holliday , that provides free Visual Studio 2010 add-ins for more sophisticated CAML intellisense - the CAML.Net.Intellisense. You can download the bits in Visual Studio Gallery ( Gallery > Tools > caml.net.intellisense). Nice job John.

English

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

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

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

English

Today, I almost missed an update of very nice tool – Microsoft SharePoint Administration Toolkit. I browse to Microsoft SharePoint Team Blog, – found out that they already announce the 4th release last week.

But before you can play around with the tools, you will need to install following pre-requisites:

1. Service Pack 2 for WSS and SharePoint Server 2007
2. April Cumulative Update for WSS and SharePoint 2007.

The April CU comes as hotfix – so you will need to register your email address and get the download link + password from your inbox.

Since its almost late for me, I think – I will continue the installation tomorrow, after downloading the package.

Check here for more details :
1. April CU : http://blogs.msdn.com/sharepoint/archive/2009/05/13/april-cumulative-update-packages-ready-for-download.aspx

2. Microsoft SharePoint Administration toolkit:
http://blogs.msdn.com/sharepoint/archive/2009/08/27/announcing-the-fourth-release-of-the-microsoft-sharepoint-administration-toolkit.aspx

English

Remember about critics to “stsadm –o copyappbincontent” to deploy SharePoint resource in my previous post here.

At the end of the post, I think that it should be “stsadm –o copyfarmappbincontent” instead.

Why?
Because the last will work in centralized deployment mode, same as solution deployment.

But what’s the secret? Why the standard copyappbincontent doesn’t work in farm configuration?

I’ll post in another article. But now, I have created the project in Codeplex. You can grab the code or download the binary here.

Setelah lama menggunakan BlogJet, hari ini nampaknya saya akan beralih menggunakan Windows Live Writer. Yach, kita harus menghormati pembuat BlogJet yang menuntut pembayaran lisensi; sementara menulis di Blog adalah pekerjaan sambilan yang semestinya juga gratis. Jadi tidak logis kalau saya harus merogoh kocek untuk membeli BlogJet.

Dilain pihak, Microsoft menawarkan Windows Live Writer secara gratis kepada para pengguna Windows. Jadi mungkin ini adalah saat yang tepat untuk berpindah kelain hati. Goodby BlogJet, and welcome Windows Live Writer.

Pertama saya pikir, Windows Live Writer tidak secantik ini. Ternyata WLW ini memberikan pengalaman menulis blog yang kaya. Saya seolah-olah menulis langsung di halaman blog.

Bagian preview pun tak kalah menariknya, karena menampilkan preview tampilan blog kita secara utuh dengan themes yang digunakan. Nampaknya, saya akan segera jatuh cinta pada Windows Live Writer.

Misalnya, ketika saya mengganti account blog ke blog yang lain, WLW secara otomatis akan mendownload themes dan file-file yang dibutuhkan untuk menampilkan perview. Dan hasilnya saya memang seolah-olah melihat tampilan posting di web.

English

For anybody who works with SharePoint Object Model (SOM), you might have read these articles  :

• Common Coding Issues When Using the SharePoint Object Model
• Using Disposable Windows SharePoint Services Objects

If you have not read those articles, I suggest to spend your 10 minutes to read them. It was posted 1 year ago, but still relevant if you’re actively develop or do code quality control in SharePoint development.

I’ve been working with team that are new to SharePoint and even tough we have a brief explanation and code standards; they tends to miss at some points. I usually use the list from Roger Lamb (SharePoint 2007 and WSS 3.0 Dispose Pattern by Example) for my reference to do sampling check on our controlled sources.

But, thanks to Pandrew – who made SharePoint Dispose Checker . With this tool, I would never do visual sampling check again. It will just make our quality control job easier. Run the tools and go grab the line in the source code to see if it is truly undispossed or just false positive.

Bahasa

Bagi rekan-rekan yang bekerja dengan SharePoint Object Model (SOM),  dua artikel ini mungkin sudah pernah Anda baca  :

• Common Coding Issues When Using the SharePoint Object Model
• Using Disposable Windows SharePoint Services Objects

Jika Anda belum sempat keduanya, cobalah untuk meluangkan sedikit waktu untuk membaca artikel tersebut.  Meskipun sudah cukup lama ditulis, namun tulisan itu masih relevan untuk rekan-rekan yang aktif mengembangkan aplikasi dengan SharePoint.

Biasanya saya menggunakan daftar yang dibuat oleh Roger Lamb (SharePoint 2007 and WSS 3.0 Dispose Pattern by Example) untuk melakukan pengecekan terhadap hasil code rekan-rekan dalam satu tim. Caranya adalah dengan mengambil sampling dari semua code yang telah dibuat.

Tetapi pekerjaan itu sekarang menjadi jauh lebih mudah dengan adanya  SharePoint Dispose Checker , yang dibuat Pandrew dkk. Dengan utility ini, tidak perlu ada lagi pengecekan acak. Cukup dengan menjalankan utility dan memverifikasi ulang method yang dilaporkan “bermasalah”.  “Bermasalah” belum tentu benar-benar tidak melakukan dispose – tetapi bisa jadi hanya interpretasi berbeda dengan SPDisposeChecker; namun ini sudah cukup membantu kita untuk melakukan pengecekan secara langsung hanya pada baris-baris yang dicurigai saja.

English (versi Indonesia)

New WSS 3.0 extensions for Visual Studio 2005, wow its great. It includes project templates for,

• Web Part
• Team Site Definition
• Blank Site Definition
• List Definition

What the best part is Sharepoint Solution Generator – this is must try tool kit.

Download at http://www.microsoft.com/downloads/details.aspx?familyid=19f21e5e-b715-4f0c-b959-8c6dcbdc1057&displaylang=en

–o0o–

Indonesia (English version)

Hari ini secara tidak sengaja, waktu WSS 3.0 di Microsoft, saya menemukan ekstension Visual Studio 2005 untuk WSS 3.0. Didalamnya ada beberapa template proyek, al.

• Web Part
• Team Site Definition
• Blank Site Definition
• List Definition

Satu lagi yang patut dicoba dari tools ini adalah Sharepoint Solution Generator – hmm… makhluk apa ini ya?

Download filenya di http://www.microsoft.com/downloads/details.aspx?familyid=19f21e5e-b715-4f0c-b959-8c6dcbdc1057&displaylang=en