Lots of revision paid off in the end.

OR

  
  

  
  
  
  
  

  
  
    
  

  
  
  
  

        
            
        
    

  

    
        
        
        
            

                
                    
                            
                                active
                            
                            
                            

                                    
                                        
                                    
                                

                            
                    
                    
                        
                    
                
                  

            
        
    

    
        
            
    

Server Error in ‘/’ Application.

924D3DEEAC964880B38A9F4D4B664511^TestUser^123^123^20071011T161646

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Sitecore.Exceptions.TicketParseException: 924D3DEEAC964880B38A9F4D4B664511^akom^123^321^20071011T161646
…

Why is this happening?

A: These characters “^” and “|” can’t be used in the name of the user and the password.

Reference:
http://sdn.sitecore.net/Scrapbook/Illegal%20characters%20in%20the%20name%20of%20the%20user%20and%20the%20password.aspx

item:renamed
0
Item
Result item

1
String
Item name before renaming

Unfortunately in practice the second value is actually the current item name, and not the previous name.

This bug presents a massive problem if you require the previous name.

Fortunately I found a way around this.
By using the Sitecore history engine, you can work out what the previous name was.

Solution:

        protected void OnItemRename(object sender, EventArgs args)
        {
            var itm = Event.ExtractParameter(args, 0) as Sitecore.Data.Items.Item;

            if (itm == null)
            {
                return;
            }

            var history = itm.Database.Engines.HistoryEngine.GetHistory(DateTime.UtcNow.AddDays(-1), DateTime.UtcNow.AddDays(1));

            if (history.Count < 1)
            {
                return;
            }

            var oldEntity = GetOldEntity(itm.ID.Guid, itm.Paths.Path, history);

            var oldName = GetOldName(oldEntity.ItemPath);
        }

        ///

        /// Uses the history engine to retrieve the last entry with a different path from the target item.
        /// 

        ///

        /// The item id.
        /// 
        ///

        /// The item path.
        /// 
        ///

        /// The history.
        /// 
        /// 
        /// History Entity
        /// 
        public static HistoryEntry GetOldEntity(Guid itemId, string itemPath, HistoryEntryCollection history)
        {
            var oldEntities = from h in history
                              orderby h.Created descending
                              where h.ItemId.Guid.Equals(itemId) && (!h.ItemPath.Equals(itemPath))
                              select h;

            return oldEntities.Count() < 1 ? null : oldEntities.First();
        }

        ///

        /// Gets the old item name
        /// 

        ///

        /// The old item path.
        /// 
        /// 
        /// The old item name
        /// 
        public static string GetOldName(string oldItemPath)
        {
            return oldItemPath.Substring(
                (oldItemPath.LastIndexOf("/", StringComparison.CurrentCulture) + 1),
                (oldItemPath.Length - oldItemPath.LastIndexOf("/", StringComparison.CurrentCulture) - 1));
        }

The error:

Sitecore’s event handlers conflict with RadGrid, which causes sorting, filtering, editing and deleting to fail.
I kept receiving a bank page every time an event fired, as if it lost the datasource.

The solution:

The solution to this problem is to exclude the controls from Sitecore’s event handlers.
You can do this very easily by updating the following section in the Sitecore web.config:

  
    
      
        System.Web.UI.WebControls.Repeater
        System.Web.UI.WebControls.DataList
        System.Web.UI.WebControls.GridView
        Telerik.Web.UI.RadGrid
      
    

CryptographicException file not found

Server Error in ‘/’ Application.
The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Security.Cryptography.CryptographicException: The system cannot find the file specified.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[CryptographicException: The system cannot find the file specified.
]
System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer) +7715070
System.Security.Cryptography.DSACryptoServiceProvider.ImportParameters(DSAParameters parameters) +258
System.Security.Cryptography.DSA.FromXmlString(String xmlString) +501
Sitecore.Nexus.Licensing.NexusLicenseApi.(String xml, Guid instance) +124
Sitecore.Nexus.Licensing.NexusLicenseApi.GetSnapShot(Guid instance) +683
Sitecore.SecurityModel.License.LicenseManager.GetSnapshotData(Guid instance) +47
Sitecore.SecurityModel.License.LicenseManager.UpdateSnapshot() +70
Sitecore.SecurityModel.License.LicenseManager.Initialize() +8
Sitecore.Nexus.Web.HttpModule.Application_Start() +76
Sitecore.Nexus.Web.HttpModule.Init(HttpApplication app) +435
System.Web.HttpApplication.InitModulesCommon() +65
System.Web.HttpApplication.InitModules() +43
System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +729
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +298
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +289

Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927

This random error is actually being caused by the IIS application pool not being configured to run using a non-standard user account Identity.

The solution:

To solve the problem, set Load User Profile to true for the website application pool in IIS.

1. Open IIS Manager
2. Click on Application Pools on the right.
3. Right Click on the application pool for your web site and select “Advanced Settings”
4. In the Process Model section, set Load User Profile to true.

References:

http://www.realnero.info/2010/04/sitecore-cryptographicexception-file.html
http://sdn.sitecore.net/Products/Sitecore%20V5/Sitecore%20CMS%206/ReleaseNotes/ChangeLog.aspx

But this isn’t the case. To check if an item is valid, I created a custom function called ValidateItemFields that works in an item event handler.

Solution:

        ///

        /// Validates all fields in item.
        /// 

        ///

        /// The item to be validated.
        /// 
        /// 
        /// True if all fields are valid.
        /// 
        private static bool ValidateItemFields(Item item)
        {
            if (((item != null) && !item.Paths.IsMasterPart) && !StandardValuesManager.IsStandardValuesHolder(item))
            {
                item.Fields.ReadAll();
                item.Fields.Sort();
                foreach (Field field in item.Fields)
                {
                    if (!string.IsNullOrEmpty(field.Validation) && !Regex.IsMatch(field.Value, field.Validation, RegexOptions.Singleline))
                    {
                        return false;
                    }
                }

                var formValue = WebUtil.GetFormValue("scValidatorsKey");
                if (!string.IsNullOrEmpty(formValue))
                {
                    var validators = ValidatorManager.GetValidators(ValidatorsMode.ValidatorBar, formValue);
                    var options = new ValidatorOptions(true);
                    ValidatorManager.Validate(validators, options);
                    var valid = ValidatorResult.Valid;
                    foreach (BaseValidator validator in validators)
                    {
                        var result = validator.Result;
                        if (validator.ItemUri != null)
                        {
                            var item1 = Client.ContentDatabase.GetItem(validator.ItemUri.ToDataUri());
                            if (((item1 != null) && StandardValuesManager.IsStandardValuesHolder(item1)) && (result > ValidatorResult.CriticalError))
                            {
                                result = ValidatorResult.CriticalError;
                            }
                        }

                        if (result > valid)
                        {
                            valid = validator.Result;
                        }

                        if (validator.IsEvaluating && (validator.MaxValidatorResult >= ValidatorResult.CriticalError))
                        {
                            return false;
                        }
                    }

                    switch (valid)
                    {
                        case ValidatorResult.CriticalError:
                            return false;

                        case ValidatorResult.FatalError:
                            return false;
                    }
                }
            }

            return true;
        }

Example:

///

        /// On Item Moving event handler for ImportArticle Items
        /// 

        ///

        /// The sender object.
        /// 
        ///

        /// The args.
        /// 0 - Item being moved
        /// 1 - Move destination
        /// 
        public void OnItemMoving(object sender, EventArgs args)
        {
            var item = Event.ExtractParameter(args, 0) as Item;
            if (item == null)
            {
                return;
            }

            // Check item type is ImportArticle
            if (!item.Template.Name.Equals(TemplateName))
            {
                return;
            }

            // If ancestor is a child of Content Node, then return
            if (item.Axes.GetAncestors().Any(ancestor => ancestor.Paths.Path.Equals(ContentItemPath)))
            {
                return;
            }

            // If item is valid, return
            if (ValidateItemFields(item))
            {
                return;
            }

            SheerResponse.Alert(ErrorMessage, new string[0]);
            ((SitecoreEventArgs)args).Result.Cancel = true;
        }

If you have a namespace which has the same name as another namespace but at a different level, .net won’t know which namespace to use, and will through an error.

This is also true for classes as well.

Example:

namespace Zone.Section
{
public class ShowZone{}
}


using Zone.Section

}

Now the example above will not compile, because .net can only see the Zone for Website.Zone, and not Zone.Section.

This problem usually occurs if you haven’t organised your namespaces properly, or is you have inherited code form various sources.

The solution

To get this code to work, you need to use the global prefix, and define the “using” (or Imports in vb.net) within the namespace.

For example:

using Zone.Section

}

OR

namespace Website.Zone
{

}

Publishing a Cuyahoga site from the source code using visual studio will not work using the in built publishing tools alone. You need to take a few additional steps.

Please note I used Visual Studio 2008 to create this tutorial. The steps may differ slightly in different versions.

1. Rebuild solution

Rebuild the entire solution to make sure everything is up to date.
Also make sure all your modules have been added to the Modules folder of the Web project successfully.

2. Publish Cuyahoga.Web project

Publish the web project by selecting from the menu:

• Select the Cuyahoga.Web project in the solution explorer.
• Select Build from the menu bar.
• Select Publish Cuyahoga.Web.
• In the Publish dialog:
  • Select a target location for the published site.
  • Select “Delete all existing files prior to publish” for a clean install.
  • Select “Only files needed to run this application.”
  • Select Publish button.

3. Add module files to published site.

You need to copy the modules folder from you Cuyahoga.Web project, over to your published site manually.
If there is nothing in your Cuyahoga.Web modules folder, you probably didn’t rebuild the solution properly, so go back and repeat step 1.

4. Deploy

Your site is now fully compiled and ready to deploy.

It didn’t seem obvious to me at first how to change the appearance of the Cuyahoga admin template, so I thought I’d create a simple guide to point you in the right direction.

Web Config

Cuyahoga Admin Web Config

The web config within the admin folder of your Cuyahoga site is where you can find the template settings.
/Admin/Web.config

<appSettings> <add key="TemplateDir" value="~/Admin/Controls/" /> <add
    key="DefaultTemplate" value="AdminTemplate.ascx" /> <add key="DefaultCss"
    value="~/Admin/Css/Admin.css" /> <add key="DefaultTitle" value="Cuyahoga Site
    Administration" /> </appSettings>

Template directory

Set this to the directory that contains the template you want to use for the admin section.

Default template

Set this to the template file you wish to use as the default admin template. Note that this file must reside within the template directory.

Default CSS

Set the default CSS file to be used by the template.

Default Title

Set the default page title use for the admin section.

Conclusion

Its probably best to make a copy of the standard AdminTemplate.ascx template, then edit this to fix your design if your new to using templates in Cuyahoga.

But the system is flexible enough to allow you to create your own templates from scratch.

This tutorial shows you how to create a simple module for the open source CMS Cuyahoga.
Visual studio 2008 was used to create this example, but it should also work in Visual Studio 2005 with the SP1 upgrade.

Supporting documents:
Cuyahoga.Modules.Sample Files VB.net
PDF tutorial

1. Download Cuyahoga source

You can download the latest version here:
http://sourceforge.net/projects/cuyahoga/files/

2. Install and run site

Set up a sample site or use your current Cuyahoga site.

3. Open the Cuyahoga solution in visual studio.

4. Add a new web application project to the solution.

Name the project using the following standard: Cuyahoga.Modules.

Add Project

Add Web Project

6. Add directories

Add the following directories to your project:
Web
Install
Install/Database
Install/Database/mssql2000

Add Folders

7. Add post build events.

Edit and then add the following post build events to your project properties:

xcopy /s /y "$(ProjectDir)"Web\*.as?x "$(SolutionDir)"Web\Modules\Sample\
xcopy /s /y "$(ProjectDir)"Install\Database\*.sql "$(SolutionDir)"Web\Modules\Sample\Install\Database\
xcopy /s /y "$(TargetDir)"Cuyahoga.Modules.Sample*.dll "$(SolutionDir)"Web\bin\

You can find the post build events window by going to:
Open Project Properties

Go to Project Properties

Properties Compile

Build Events

If your using a different version of visual studio, the build events window might be a tab in the project properties window.

8. Add project references.

You will need to add at least the following two project references:
Cuyahoga.Core
Cuyahoga.Web

To add a project reference, right click on the project in the solution explorer and the select add reference.

Add project reference

Add reference

9. Create the module controller.

Create a new class in the root of your module project called Module.
For example – SampleModule

Add the following code to your class, remember to change SampleModule for the name of your module.

C#

using System;
using Cuyahoga.Core.Domain;

Namespace Cuyahoga.Modules.Sample
{
    ///

    /// Controller class of the module
    /// 

    class SampleModule: ModuleBase
    {
        ///

        /// Controller constructor
        /// 

        Public SampleModule()
        {
            //nothing in the constructor for this basic sample
        }
    }
}

VB.net

Imports System
Imports Cuyahoga.Core.Domain

'''

''' Controller class of the module
''' 

Class SampleModule
    Inherits ModuleBase
    '''

    ''' Controller constructor
    ''' 

    Public Sub New()
        'nothing in the constructor for this basic sample
    End Sub
End Class

10. Create a user control.

Add a new user control to your web folder, for example:

<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="Sample.ascx.cs"
    Inherits="Cuyahoga.Modules.Sample.Web.Sample" %>
Hello World!

The code behind needs to inherit the BaseModule Control.

For example:

C#

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

using Cuyahoga.Web.UI;

Namespace Cuyahoga.Modules.Sample.Web
{
    ///

    /// Sample control displayng in Cuyahoga the "Hello World" text
    /// 

    public partial class Sample : BaseModuleControl
    {
        protected void Page_Load(object sender, EventArgs e)
        {
            //for this basic sample we do not need to do anything
        }
    }
}

VB.net

Imports System
Imports System.Data
Imports System.Configuration
Imports System.Collections
Imports System.Web
Imports System.Web.Security
Imports System.Web.UI
Imports System.Web.UI.WebControls
Imports System.Web.UI.WebControls.WebParts
Imports System.Web.UI.HtmlControls

Imports Cuyahoga.Web.UI

Namespace Web
    '''

    ''' Sample control displayng in Cuyahoga the "Hello World" text
    ''' 

    Partial Public Class Sample
        Inherits BaseModuleControl
        Protected Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs)
            'for this basic sample we do not need to do anything
        End Sub
    End Class
End Namespace

11. Create the SQL installation scripts.

In the Install/Database/mssql2000 folder you need to add 3 files to take advantage of the auto install and uninstall features.

Version File

For example if your module is at version 1.0.0, you need to add a file called 1.0.0.sql with the following code:

UPDATE cuyahoga_version SET major = 1, minor = 0, patch = 0 WHERE assembly = 'Cuyahoga.Modules.Sample'
go

install.sql

The install.sql file will contain all the tables and stored procedures that need to be installed in the database to run your module, as well as update some of the CMS tables to identify your module.

For example:

/*
 *  Table data
 */
--Install the Sample module for Cuyahoga in SQL Server

INSERT INTO cuyahoga_moduletype ([name], assemblyname, classname, path, editpath, inserttimestamp, updatetimestamp)
VALUES ('Sample', 'Cuyahoga.Modules.Sample', 'Cuyahoga.Modules.Sample.SampleModule', 'Modules/Sample/Sample.ascx', NULL, getdate(), getdate())
GO

INSERT INTO cuyahoga_version (assembly, major, minor, patch)
VALUES ('Cuyahoga.Modules.Sample', 1, 5, 0)
GO

uninstall.sql

The uninstall.sql file will contain instructions to delete the tables, stored procedures and other records installed by the install.sql file.

For example:

--Uninstall the Sample module in Cuyahoga for SQL Server

DELETE FROM cuyahoga_version WHERE assembly = 'Cuyahoga.Modules.Sample'
go

DELETE FROM cuyahoga_moduletype
WHERE assemblyname = 'Cuyahoga.Modules.Sample'
go

12. Rebuild entire solution and run.

Run the site and login as admin.
Navigate to the modules page and you should now see your module in the table.

Click install and if everything is fine it should be installed and you can now add that modules to sections of the site.

Troubleshooting

Namespace problems.

You might come across a problem when you try to install the module which throws the following error:

An error occured: Loading failed for Sample.Could not find module: Cuyahoga.Modules.Sample.SampleModule, Cuyahoga.Modules.Sample

This is caused by some of the namespaces in your module not being compiled correctly.
I found out that Visual studio sometimes adds the default namespace to your class in addition to whatever namespace you declare.
So if you used Namespace Cuyahoga.Modules.Sample.Web in your code, this will actually come out as Namespace Cuyahoga.Modules.Sample.Cuyahoga.Modules.Sample.Web.
To fix this remove the default namespace from your class. So the example I provided before will now simply be: Namespace Web

Install Scripts

In order for the install scripts to work, they need to have the right file name and be places in the correct folder structure defined in the tutorial.
Its recommended to have all three files for this feature to work smoothly.

Cannot see web form or user control source files in Visual Studio.

For some reason, Visual Studio will sometimes hide certain files and folders. To see all files in the project folder go to PROJECT in the main menu and select SHOW ALL FILES.

Further reading:

http://www.paolocorti.net/2007/04/30/cuyahoga-hello-world-sample-module-tutorial/
http://www.cuyahoga-project.org/home/developers.aspx

By default you are unable to add web forms or user controls to a Class Library project. This guide will tell you how to get around this.

IMPORTANT – Backup your project file before you make any amends to it, just in case something goes wrong.

Step 1 – Open class library project file in a text editor.

The project file is usually in the root folder and has a file extension of .vbproj or .csproj

Step 2 – Add or replace the tag

Add or replace the tag with the following:

{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}

This tag should be underneath the tag, which is within the tag.

Example:

  
    Debug
    AnyCPU
    9.0.30729
    2.0
    {42FC0FAF-C05B-4C16-AB8A-3F4698F910D8}
    {349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}
    Library
    Cuyahoga.Modules.Test
    Cuyahoga.Modules.Test
    512
    WebControl
    v3.5
    On
    Binary
    Off
    On
  
  
    true
    full
    true
    true
    bin\Debug\
    Cuyahoga.Modules.Test.xml
    42016,41999,42017,42018,42019,42032,42036,42020,42021,42022
  
  
    pdbonly
    false
    true
    true
    bin\Release\
    Cuyahoga.Modules.Test.xml
    42016,41999,42017,42018,42019,42032,42036,42020,42021,42022
  
  
    
    
    
    
    
    
    
      3.5
    
    
      3.5
    
    
      3.5
    
  
  
    
    
    
    
    
    
    
    
  
  
    
    
    
      True
      Application.myapp
    
    
      True
      True
      Resources.resx
    
    
      True
      Settings.settings
      True
    
  
  
    
      VbMyResourcesResXFileCodeGenerator
      Resources.Designer.vb
      My.Resources
      Designer
    
  
  
    
      MyApplicationCodeGenerator
      Application.Designer.vb
    
    
      SettingsSingleFileGenerator
      My
      Settings.Designer.vb
    
  
  
  

Step 3 – Save file and open project up in visual studio.

Conclusion

You should now be able to add web forms and user controls from the solution explorer within visual studio.

Further reading:
http://haacked.com/archive/2006/02/07/AddingWebUserControlToAClassLibraryInVS.NET2005.aspx

If a directory within an ASP.net website is deleted while the site is running, this causes the whole site to reboot, loosing any session data and logging out users.

This quick tutorial will show you a quick fix that can be run in your global.asax to prevent this from happening.

Step 1 – Define the bug fix method

Define the following method somewhere in your application (easiest is within the global.asax file, but you can place it anywhere else that’s more convenient).

C#

private void FixAppDomainRestartWhenTouchingFiles()
{
if (CurrentTrustLevel == AspNetHostingPermissionLevel.Unrestricted)
{
// From: http://forums.asp.net/p/1310976/2581558.aspx
// FIX disable AppDomain restart when deleting subdirectory
// This code will turn off monitoring from the root website directory.
// Monitoring of Bin, App_Themes and other folders will still be operational, so updated DLLs will still auto deploy.
PropertyInfo p = typeof(HttpRuntime).GetProperty("FileChangesMonitor", BindingFlags.NonPublic | BindingFlags.Public | BindingFlags.Static);
object o = p.GetValue(null, null);
FieldInfo f = o.GetType().GetField("_dirMonSubdirs", BindingFlags.Instance | BindingFlags.NonPublic | BindingFlags.IgnoreCase);
object monitor = f.GetValue(o);
MethodInfo m = monitor.GetType().GetMethod("StopMonitoring", BindingFlags.Instance | BindingFlags.NonPublic);
m.Invoke(monitor, new object[] { });
}
}

VB.net

        Private Sub FixAppDomainRestartWhenTouchingFiles()
    If CurrentTrustLevel = AspNetHostingPermissionLevel.Unrestricted Then
        ' From: http://forums.asp.net/p/1310976/2581558.aspx
        ' FIX disable AppDomain restart when deleting subdirectory
        ' This code will turn off monitoring from the root website directory.
        ' Monitoring of Bin, App_Themes and other folders will still be operational, so updated DLLs will still auto deploy.
        Dim p As PropertyInfo = GetType(HttpRuntime).GetProperty("FileChangesMonitor", BindingFlags.NonPublic Or BindingFlags.[Public] Or BindingFlags.[Static])
        Dim o As Object = p.GetValue(Nothing, Nothing)
        Dim f As FieldInfo = o.[GetType]().GetField("_dirMonSubdirs", BindingFlags.Instance Or BindingFlags.NonPublic Or BindingFlags.IgnoreCase)
        Dim monitor As Object = f.GetValue(o)
        Dim m As MethodInfo = monitor.[GetType]().GetMethod("StopMonitoring", BindingFlags.Instance Or BindingFlags.NonPublic)
        m.Invoke(monitor, New Object() {})
    End If
End Sub

Step 2 – Create Global.asax file in root of application.

If you don’t already have a global.asax file, you need to create one in the root of your application.

Step 3 – Run method in Application Start event of global.asax

C#

protected void Application_Start(Object sender, EventArgs e)
{
// Misc
FixAppDomainRestartWhenTouchingFiles();
}

VB.net

Protected Sub Application_Start(ByVal sender As [Object], ByVal e As EventArgs)
' Misc
FixAppDomainRestartWhenTouchingFiles()
End Sub

Conclusion

This should fix the bug and prevent the ASP.net web site from restarting when a directory is deleted.

Further reading:
http://forums.asp.net/p/1310976/2581558.aspx

This tutorial will show you how to precompile an ASP.net Web Site Project in Visual Studio 2008.

ASP.net currently has 3 different project models:

1. Web Site Projects
2. Web Application Projects
3. MVC Projects

Unlike Web Application and MVC projects, Web Site Projects do not need to be precompiled before they can be deployed on the web server. ASP.net dynamically compiles the site on Application start which means websites can be deployed quicker. The disadvantage is the user will experience delays every time the site needs to recompile on the server.

To overcome this problem, you can precompile a Web Site Project in Visual Studio 2005 upwards (excluding Visual Web Developer) before you upload it to the web server.

Steps

1. Open or create a new website project in Visual Studio.
2. Go to Build > Publish Web Site
3. In the Target Location text box, enter where you would like to save the precompiled site.
4. Leave the default values how they are, unless you wish to customise the build.
5. Press OK.
6. Visual Studio will build and save the entire pre-compiled website in the location you selected.
7. Simply upload this to your web server as you would normally do.

Notes

Warning: Make sure you delete the App Code folder on your web server if one already exists. If you have a class file in the App Code folder that has the same class as one on a precompiled site, you will get an error as both will be referenced in the project.

Further reading

For more information, please see:
How to: Precompile ASP.NET Web Sites

1. Open IIS

2. Save configuration file

3. Delete website

Requirements

• Visual Studio 2005 or higher.
• ASP.net AJAX Extensions installed on the development machine.
  style="color: rgb(85, 26, 139);">http://www.asp.net/ajax/downloads/
• The host server must have at least .net 2.0.
• ASP.net AJAX Control Toolkit -  href="http://www.codeplex.com/Wiki/View.aspx?ProjectName=AjaxControlToolkit"
  style="color: rgb(85, 26, 139); text-decoration: none;">http://www.codeplex.com/Wiki/View.aspx?ProjectName=AjaxControlToolkit
• AJAX Validation Guidance Bundle -  href="http://websf.codeplex.com/Wiki/View.aspx?title=Validation_landing_page">http://websf.codeplex.com/Wiki/View.aspx?title=Validation_landing_page

STEP 1 – ASP.net AJAX Extensions

STEP 2 – ASP.net AJAX Control Toolkit

STEP 3 – Add the dll’s

<%@
Register
Assembly=”AjaxControlToolkit.WCSFExtensions”
Namespace=”AjaxControlToolkit.WCSFExtensions”
TagPrefix=”ajaxtoolkitwcsfextensions”
%>

AJAX Server Side Validation

This is an example of using server side validation,
client side by using ASP.net AJAX and the validation extension
controls.

Protected Sub CustomValidator1_ServerValidate(ByVal source As Object, ByVal args As System.Web.UI.WebControls.ServerValidateEventArgs)
	Handles CustomValidator1.ServerValidate
	args.IsValid = validateNumber()
End Sub

Function validateNumber() As Boolean
	If IsNumeric(TextBox1.Text) Then
		Return True
	Else
		Return False
	End If
End Function

<system.web>
 <compilation>
   <assemblies>
    <add assembly="System.Web.Extensions, Version=1.0.61025.0,
                   Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   </assemblies>
 </compilation>
</system.web>

<system.web>
 <Pages>
  <Control>
   <add tagPrefix="asp" namespace="System.Web.UI"
      assembly="System.Web.Extensions, Version=1.0.61025.0,
                Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
  <Control>
 <Pages>
<system.web>

<system.web>
 <httpHandlers>
  <remove verb="*" path="*.asmx"/>
   <add verb="*" path="*.asmx" validate="false"
      type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions,
            Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   <add verb="*" path="*_AppService.axd" validate="false"
      type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions,
            Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/s>
   <add verb="GET,HEAD" path="ScriptResource.axd"
      type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions,
            Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
      validate="false"/>
 </httpHandlers>
</system.web>