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 (115) .

English

If you have read my comments on the Writing Custom Web Service for SharePont, Is it supported here (http://blog.libinuko.com/2011/02/16/sharepoint-writing-custom-web-service-for-sharepoint-is-it-supported/) ; you may have already created standard ASPNET web services. It is working, but with some limitation:

1. You can not have path virtualization

   Virtualization is one of SharePoint’s technique provided by SPVirtualPath provider, that enable virtualization of your web service path. For example, list.asmx will be available for http://mysite.com/_vti_bin/lists.asmx , or http://mysite.com/sites/myothersitecollection/_vti_bin/lists.asmx. The site collection has been virtualized by SharePoint.

   Without virtualization any web service consumer will have to access to the same path, usually in the root; for example /_services/mywebservice.asmx">/_services/mywebservice.asmx">http://<webapps>/_services/mywebservice.asmx

2. You can not have SPContext

   SPContext is very powerful object in SharePoint development. Using this context, we can retrieve current SharePoint context without having to instantiate it. For example, you can get current SPWeb by calling SPContext.Current.Web – and you don’t need to dispose it (in fact you’re not suppose to dispose it). Still using SPContext you can have direct access to list and everything under SharePoint.

   Without having direct access to SPContext, you have to instantiate SPWeb or SPSite using normal constructor with URL as parameter. It means new SPSite/SPWeb thread in the server memory, and you have to dispose it once you’ve done working with it.

So, how can we write custom web service for SharePoint in supported mode?

Before we start, we have to understand SharePoint architecture and how does the processing works for web services. I take following picture from SharePoint Architecture in MSDN. It describe how SharePoint process our request. There is SPHttpApplication which has SPRequestModule and any additional ASP.NET Module; and before the request returned back to the user SPHttpHandler is doint the job.

How SharePoint process web services?

If we dig into into the process on how SharePoint process request to web services in _vti_bin.

There are 3 scenarios of http request to the web services,

1. Disco request, identified by suffix ?DISCO in the web service address. For example, */_vti_bin/list.asmx?Disco
2. WSDL request, identified by suffix ?WSDL in the web service address. For example, */_vti_bin/list.asmx?Wsdl
3. Web service post request. For example, */_vti_bin/list.asmx?op=GetListItems

Every request will be processed by SPHttpHandler (SharePoint) and ScriptHandlerFactory (system.web.extension), but the SPHttpHandler will be selective only for Disco and Wsdl request.

On disco/wsdl request, SPHttpHandler will transfer the request to wsdisco.aspx or wswsdl.aspx using Server.Execute operation. This operation ensure that wsdisco.aspx/wswsdl.aspx is receiving same request object. wsDISCO.aspx or wsWSDL.aspx will then instantiate SharePoint Context object. Any *.aspx will be successfully instantiate SharePoint context object because they are managed by SPHttpApplication and hence it also impacted by SPVirtualPath provider from SharePoint which will activate path virtualization.

Next, wsDISCO.aspx will transfer the request to the <service>DISCO.aspx and wsWSDL.aspx will transfer to the <service>WSDL.aspx – using Server.Execute operation. So here we have seen 2 transfer operation. At the end, the result is correct WSDL/DISCO request. The correct WSDL/DISCO will point to the correct virtual path of the request. (Remember how do you create <service>disco.aspx / <service>wsdl.aspx)

When a consumer use the contract and tries to consume it. The SPHttpHandler will no longer intercept the request, but the normal ScriptHandlerFactory from System.Web.Extensions. However with the correct path in disco/wsdl, now the asmx now have the ability to look into current context from SharePoint. And hence you will be able to use SPContext.Current.Web in custom web services.

Part-2 is how to start create custom web services. I will need help from my buddy Denni , he will code for me. –

References

1. Writing Custom Web Services for SharePoint Products and Technology (http://msdn.microsoft.com/en-us/library/dd583131(v=office.11).aspx)

2. SharePoint Architecture (http://msdn.microsoft.com/en-us/library/bb892189(v=office.12).aspx )

3. Architectural Overview of Windows SharePoint Services (http://msdn.microsoft.com/en-us/library/dd583133(v=office.11).aspx)

4. Modifying Built-In SharePoint Files (http://msdn.microsoft.com/en-us/library/bb803457(v=office.12).aspx)

English

When I am looking for a way to compress file(s) into Zip, I find a blog from David Aiken here (Compress Files with Windows PowerShell then package a Windows Vista Sidebar Gadget) . I will just focus on Add-Zip function and nothing more.

Here is the original code:

function Add-Zip
{
    param([string]$zipfilename) 

    if(-not (test-path($zipfilename)))
    {
           set-content $zipfilename ("PK" + [char]5 + [char]6 + ("$([char]0)" * 18))
           (dir $zipfilename).IsReadOnly = $false
     } 

     $shellApplication = new-object -com shell.application
     $zipPackage = $shellApplication.NameSpace($zipfilename) 

     foreach($file in $input)
     {
            $zipPackage.CopyHere($file.FullName)
            Start-sleep -milliseconds 500
     }
}

usage: dir c:\demo\files\*.* -Recurse | add-Zip c:\demo\myzip.zip

I am raising two problems with the code:

1. Looking at the usage example, it is clear that the function accept only fully path filename. The reason, on line-12 , the $shellApplication.NameSpace parameter is $zipfilename; and this is not possible without giving fully path filename.

2. On line-16, the operation expect that $input array will contains object with FullName properties, that why the usage example uses DIR. What about if you just want to specify a filename?

With the 2 problem above, I am ready to improve that function. In the new improved version, Get-ChildItem will help us to convert any string representation of a file to a fully path filename. It won’t break DIR piping functionality, since actually Get-ChildItem is dir (and extra) functionality.

Here is the improved version:

function Add-Zip
{
	param([string]$zipfilename)

    $currFile = $zipfilename | get-childitem
	if(-not (test-path($zipfilename)))
	{
		set-content $currFile.FullName ("PK" + [char]5 + [char]6 + ("$([char]0)" * 18))
		(dir $currFile.FullName).IsReadOnly = $false
	}

	$shellApplication = new-object -com shell.application
	$zipPackage = $shellApplication.NameSpace($currFile.Fullname)

	$input | % {
            $file = $_ | get-childitem
            $zipPackage.CopyHere($file.FullName)
            Start-sleep -milliseconds 500
	}
}

usage: "FileInThisFolder.txt" -Recurse | add-Zip "ZipInThisFolder.zip"
        dir c:\demo\files\*.* -Recurse | add-Zip c:\demo\myzip.zip

So, I hope you enjoy the improved version.

English:

So what is the largest number in SharePoint numeric column?

Before we can answer this question, let take a look how SharePoint store the data in SQL table. By design, SharePoint will map specific column type in SharePoint into SQL data type; they are nvarchar, ntext, sqlvariant, int, float and bit. For example, true/false column will be mapped to bit and numeric column will be mapped to float.

There are two types of float data type in SQL, 7 digits or 15 digits precisions (http://msdn.microsoft.com/en-us/library/ms173773.aspx). And of course, Microsoft’s engineer will choose the larger precision 15 digits – using 8 bytes storage. (See table below)

n is the number of bits that are used to store the mantissa of the float number in scientific notation.

The nvalue represent the number of bits that are used to store the mantissa of the float number. Therefore the maximum value of the float number is 2^53 =  9.00719925 × 10¹⁵ .

Precision represent the length of significant digit to which a number can be represented. When a number contains digits more than max precision digits, then it will be rounded up/down to the precision digits. For example, 12345 will be seen as 1.2345 x 10⁴ in 5 digits precisions or 1.235 x 10⁴ in 4 digits precisions. Hence bigger precision is desirable to represent the exact number, otherwise it will only represents approximation value.

Since SQL Server specifies 15 digits precision for its floating point, then you must be-careful for any number with more than 15 digits. For example, the 999,999,999,999,999 is maximum exact value based on 15 digits precision. Any number above that, even with different as small as 0.1 will be an approximate value; for example 999,999,999,999,999.1 is same as 999,999,999,999,999 . And if you do arithmetic operation – then you may end-up with big floating error.

So what is the impact?

1. Storage Boundaries (2^53)
   This boundaries limits the maximum value which can be stored in a numeric column. You can’t save 9.007199256 x 10¹⁵ without rounding. And everything beyond this storage boundaries will be ignored and saved as 2^53 value.
2. Precision Boundaries (15 digits)
   This boundaries limit the number of digits before SQL starts to round-up/round-down. Remember floating data is approximate , and therefore not all value can be represented as is.  As you may guess, if you try to save 999,999,999,999,999.5 – you will end-up with 1,000,000,000,000,000 value.

The good news is, we have used SQL floating data type without any problem; so we put the same faith to SharePoint numeric column. However, if you want to use SharePoint or SQL table, please ensure that you have enough precision for your data.

English

You may already read this following article “Writing Custom Web Service for SharePoint Products and Technologies” (http://msdn.microsoft.com/en-us/library/dd583131(v=office.11).aspx) or “Walkthrough: Creating a Custom ASP.NET Web Service” (http://msdn.microsoft.com/en-us/library/ms464040.aspx). The steps can be summarized as follows:

1. Create normal ASPNET web service
   In this step you will create ASPNET Web Services using Visual Studio as you always do. From this step, you will have <Service>.asmx, where <Service> is your web service asmx file.
2. Create corresponding .disco file and a .wsdl file
   In this step you will create extract of DISCOvery  file and WSDL of ASPNET web service from step #1, and add reference to Microsoft.SharePoint assembly. From this step, you will have 2 files <Service>disco.aspx and <Service>wsdl.aspx.
3. Copy the 3 files to _vti_bin (12hive\ISAPI)
   In this step you will copy the 3 files (<Service>.asmx, <Service>disco.aspx and <Service>wsdl.aspx) into 12hive\ISAPI. Of course in real deployment, you can use WSP.
4. Register the new web service in spdisco.aspx
   In this step you will modify built-in SharePoint file spdisco.aspx, so that your web service will be recognized by SharePoint.

Until here you will have working custom web service in SharePoint but  are you sure that your SharePoint farm is still supported?

If you read “Modifying Built-In SharePoint Files” (http://msdn.microsoft.com/en-us/library/bb803457(v=office.12).aspx) rules, the step #4 is unsupported. Step#4 is to modify spdisco.aspx so that the custom web service will work.

So do you still want to built custom web service using that technique?
My suggestion, think twice! In fact you can still use ASPNET web service without SharePoint integration – it will work but lost SharePoint context. Moreover, you can’t tell WSP to modify spdisco.aspx unless you use event handler – which mean more complexity.

English

Microsoft just released cumulative update package for December 2010. The CU will contains hotfix package for Office 2010 Client and Servers.

See full release from Microsoft in this KB :KB2479673.

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

I never aware of SharePoint Conference before, but this year there will be SharePoint Conference 2009 with almost 250 sessions planned. And I hope we can get closer to know SharePoint 2010.

Taken from MS SharePoint Team blog, here are the sessions….

• SharePoint 2010 Overview and What’s New
• Upgrading to SharePoint 2010
• SharePoint 2010 Capacity and Performance Planning
• SharePoint 2010 Security and Identity Management: What’s New.
• Visual Studio 2010 Tools for Office Development
• SharePoint 2010 Ribbon, ECMAScript and Dialog Framework Development
• Developing with REST and LINQ in SharePoint 2010
• Upgrading SharePoint Server 2007 Code to SharePoint 2010
• Building SharePoint Composite Applications with the Microsoft Application Platform
• What’s New in Business Connectivity Services (The Business Data Catalog Evolves!)
• FAST Search for SharePoint – Capabilities Deep-Dive
• Advanced Dashboard Creation with PerformancePoint Services for SharePoint 2010
• Overview of Visio 2010 and Visio Services for SharePoint 2010
• SharePoint 2010 Web Content Management Deep-Dive
• If You Build It, They Will Come: Driving End User Adoption

I wish I could come to the conference.

Indonesian

Sejak mengenal SharePoint, saya tidak pernah tahu akan adanya SharePoint Conference; namun di tahun 2009 ini akan diselenggarakan SharePoint Conference dengan menampilkan sekitar 250 sesi. Melihat sesi-sesi yang akan ditampilkan, nampaknya SharePoint Conference 2009 ini akan memperkenalkan SharePoint 2010 kepada masyarakat umum.

Berikut ini adalah rancangan sesi yang akan tampil di konferensi, diambil dari blog MS SharePoint Team….

• SharePoint 2010 Overview and What’s New
• Upgrading to SharePoint 2010
• SharePoint 2010 Capacity and Performance Planning
• SharePoint 2010 Security and Identity Management: What’s New.
• Visual Studio 2010 Tools for Office Development
• SharePoint 2010 Ribbon, ECMAScript and Dialog Framework Development
• Developing with REST and LINQ in SharePoint 2010
• Upgrading SharePoint Server 2007 Code to SharePoint 2010
• Building SharePoint Composite Applications with the Microsoft Application Platform
• What’s New in Business Connectivity Services (The Business Data Catalog Evolves!)
• FAST Search for SharePoint – Capabilities Deep-Dive
• Advanced Dashboard Creation with PerformancePoint Services for SharePoint 2010
• Overview of Visio 2010 and Visio Services for SharePoint 2010
• SharePoint 2010 Web Content Management Deep-Dive
• If You Build It, They Will Come: Driving End User Adoption

I wish I could come to the conference.

English

Wow the wave of Office 2010 is going closer and closer.  After the announcement of limited invitation to Office 2010 Technical preview , thus who does not have a good luck could browse to watch introduction video here.