The xsl:param instruction is just like xsl:variable with one important difference: its value is only treated as a default value and can be overridden at runtime.

Reference: http://www.xml.com/pub/a/2001/02/07/trxml9.html?page=2

<Pasted from http://blog.sqlauthority.com/2008/09/09/sql-server-error-fix-sharepoint-stop-working-after-changing-server-computer-name/>

If Microsoft Office SharePoint Server (MOSS) and your database (MS SQL Server) are running together on same physical server, changing the name of the server (computer) using operating system may create non-functional SharePoint website.

When you change the physical server name the SharePoint is already connected to the SQL instance of old computer name (OldServerName/SQLInstance) and on changing the name the SharePoint will not able to connect the SQL Server  as now the SQL Server instance will run on new computer name (NewServerName/SQLInstance).

To solve this problem you need to reconfigure the entire Microsoft Office SharePoint Server with SQL Server Instance. Please follow the steps to fix the issue.

1. Open command prompt, change directory to where stsadm.exe exists.

C:\cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

2. To invoke setconfigdb operation we need to use stsadm.exe. Run following command on command prompt

stsadm.exe -o setconfigdb -databaseserver ServerName -farmuser MyUserName – farmpassword MyPassword

3. Go to IIS, All Programs>>Administrative Tools>>Internet Information Service (IIS) Manager.

4. Right Click SharePoint Central Administration v3, click on delete and re-run the configuration wizard; the web application will be re-created by the configuration wizard.

5. After the above operation has completed successfully, run the SharePoint Products and Technologies Configuration Wizard.

All Programs>>Microsoft Office Server >> SharePoint Product and Technologies Configuration Wizard

6. Complete all the steps of wizard by clicking on Next button.

At the end of this process you will get a success wizard.

On completion of this whole procedure Microsoft Office SharePoint Server gets connected to the database with new Computer Name

It’s Wednesday morning, I got a shock when my engineers told me that they are not able to connect to Team Foundation Server. As usual, the best remedy of all time: RESTART the computer and server. However, it’s still not working. I still hit the error as mentioned above.

If you were in my situation, no panic :). Go to “IIS” of your TFS server, expand “Application Pools”, notice “Microsoft Team Foundation Server Application Pool”. Is it Stop or in Error mode? If yes, do the following and have your nice day:

Note the identity of your application pool. E.g.: Domain\TFSService. Go to “Active Directory Users and Computers” or “Local Users and Computers”, right-click and select Properties of that user, and check the “Password Never Expires” box. Now, restart your server or start the “error” application pool.

Thanks to Niraj for the guidance (http://nirajrules.spaces.live.com/blog/cns!12C5F7733841CB22!119.entry).

A great post comparing the differences between ASP.Net MVC validation framework available out there: http://goneale.com/2009/06/25/aspnet-mvc-validation-refresh-best-techniques-frameworks/

As I tried, “devermind.com: Client-side form validation made easy (w/ xVal)” so far remains the best validation framework as it combines Data Annotation, jQuery and xVal methods together.

Pasted from http://www.codetoday.net/default.aspx?g=posts&t=1595. Thanks to AdmOd.

1) In your IIS, identify your web site’s application pool as illustrated as below.

2) Go to Application Pools under your IIS

3) Right-click the early identified Application Pool, select “Advanced Settings” to go to the menu as shown below. Change the “Build-in account” value to “LocalSystem”

Pasted from http://weblogs.asp.net/hosamkamel/archive/2008/11/20/asp-net-mvc-project-and-team-build-issue.aspx. Original Author: Hosam Kamel

To get the MVC project build successfully with the team build make sure of the following:

- Your build server has the WebApplication targets file located in <Program Files> \MSBuild\Microsoft\Visual Studio\v9.0\WebApplications , if not . copy this file from your development machine to the same path in the build server.

- You have installed ASP.NET MVC framework in the Build server, this is the most important step otherwise you application will not build successfully in the team build you may faces some errors like :

error CS0234: The type or namespace name 'Mvc' does not exist in the namespace 'System.Web' (are you missing an assembly reference?)

or

Controllers\RuleController.cs(31,10): error CS0246: The type or namespace name 'AcceptVerbs' could not be found (are you missing a using directive or an assembly reference?)

** Update

This will work with Beta version of ASP.NET MVC since the installation register the MVC assembly in GAC.

For preview versions , you can reference the DLL from your build project

<AdditionalReferencePath Include="C:\Program Files\Microsoft ASP.NET\ASP.NET MVC CodePlex Preview 4\Assemblies" />