SQL Server Authentication enabling using Microsoft SQL Server 2008 Management Studio

Microsoft SQL Server Management Studio provides integrated environment for accessing, configuring, managing, administering and developing all components of SQL Server. There you can see two authentication modes called "Windows Authentication" and "SQL Server Authentication". The Windows authentication mode only allows you to login/connect to SQL Server with Windows authentication.

If you install the Microsoft SQL Server using Windows Authentication mode, the "sa" account is disabled by default. So if you plan to use SQL Server Authentication, you have to enable the "sa" account. This tutorial tells you how to enable the "sa" account and there you must remember that the SQL Server service needs to restart to make this change effective. 

1. First, Login to the SQL Server Management Studio using Windows Authentication. Right-click on the database instance, and go to Properties.

2. Then on Properties page, click on Security and select SQL Server and Windows Authentication mode, and click on OK to close the Server Properties page.

3. Now you will get dialog box saying that you should restart your SQL Server to take the changes take effect. Is is not done yet, you have to done one more thing to enable the "sa" login.

4. Now expand Security folder and go to Logins. You can see the "sa" account is disabled when you install SQL Server using Windows Authentication mode.

5. Then right-click on the "sa" account and go to Login Properties. There you can set a password for the "sa" account.

6. Click on the Status page. There you can see the "sa" account is disabled by default. Click on the Enabled button to enable it. Then click on Ok to close the "sa" Login Properties.

Now "sa" account is enabled and you can login to the SQL instance using the "sa" account after restarting the SQL Server.

Allow IIS to access Local SQL Server database

You can change the ApplicationPoolIdentity from IIS7 -> Application Pools -> Advanced Settings.

Under ApplicationPoolIdentity you will find local system. This will make your application run under NT AUTHORITY\SYSTEM, which is an existing login for the database by default.

Introducing IIS Express

Developers today build and test ASP.NET sites and applications using one of two web-servers:

• The ASP.NET Development Server that comes built-into Visual Studio
• The IIS Web Server that comes built-into Windows

Both of the above options have their pros and cons, and many ASP.NET developers have told us: “I wish I could have the ease of use of the ASP.NET Development Server, but still have all the power and features of IIS”.  Today I’m happy to announce a new, free option that we are enabling – IIS Express - that combines the best characteristics of both, and which will make it easier to build and run ASP.NET sites and applications.

IIS Express will work with VS 2010 and Visual Web Developer 2010 Express, will run on Windows XP and higher systems, does not require an administrator account, and does not require any code changes to use.  You will be able to take advantage of it with all types of ASP.NET applications, and it enables you to develop using a full IIS 7.x feature-set.

How Things Work Today

Before I get into the details of IIS Express, let’s first quickly review how the ASP.NET Development Server and IIS options work today.

ASP.NET Development Server

Visual Studio’s built-in ASP.NET Development Server (also known as “Cassini”) has the benefit of being light-weight and easy to quickly run.  It doesn’t listen on remote ports (which makes it easier to get approved for many corporate security environments), works even when you are running under a non-administrator account, and doesn’t require a separate installation step. 

The fact that it is so easy to get running is a huge positive of it – and the reason it is the default web-server used by ASP.NET projects in Visual Studio when you press F5 to run them:

The downside with the ASP.NET Developer Server, though, is that it does not support a full set of web-server features.  For example, it doesn’t support SSL, URL Rewriting Rules (like the SEO URL Rewrite Rules I blogged about here), Custom Security Settings, and other richer features now offered with IIS 7.

IIS Web Server

IIS is the other option developers use when running and testing their applications with Visual Studio.  You can configure a web project within Visual Studio to use IIS by right-clicking on the project and pulling up its properties (and then by clicking on the “Web” tab within the properties window)":

Using IIS as your development server allows you to take full advantage of all web-server features (SSL, URL Rewrite Rules, etc).  IIS is a full-fledged web-server – which means you’ll get an experience closer to what it will work like when you deploy the application on a production server.

The downside with using the IIS option today, though, is that some companies don’t allow full web-servers to be installed on developer machines. IIS also requires administrator account access to setup and debug projects.  Different versions of Windows also support different versions of IIS.  For example, if you are running on Windows XP you have to use the IIS 5.1 web-server that comes with it – which doesn’t support all the new features of IIS 7.x.  Configuring a web project within VS to use IIS also requires some extra installation and configuration steps.

IIS Express – The Best of Both Options

We have been working on a new flavor of IIS 7.x that is optimized for developer scenarios that we are calling “IIS Express”. We think it combines the ease of use of the ASP.NET Web Server with the full power of IIS.  Specifically:

• It’s lightweight and easy to install (less than 10Mb download and a super quick install)
• It does not require an administrator account to run/debug applications from Visual Studio
• It enables a full web-server feature set – including SSL, URL Rewrite, Media Support, and all other IIS 7.x modules
• It supports and enables the same extensibility model and web.config file settings that IIS 7.x support
• It can be installed side-by-side with the full IIS web server as well as the ASP.NET Development Server (they do not conflict at all)
• It works on Windows XP and higher operating systems – giving you a full IIS 7.x developer feature-set on all OS platforms

IIS Express (like the ASP.NET Development Server) can be quickly launched to run a site from a directory on disk.  It does not require any registration/configuration steps. This makes it really easy to launch and run for development scenarios.

VS 2010 Integration

We are enabling IIS Express so that it can be easily used with Visual Studio 2010. You’ll be able to configure VS 2010 to use it instead of the ASP.NET Web Server as the default web-server on ASP.NET Projects.  Like the ASP.NET Development Server today, you won’t need to register a site or virtual directory to use IIS Express. It will support the same usage-model as the ASP.NET Development Server today – just with more feature support.

When you press F5 to run an ASP.NET project, Visual Studio can automatically launch IIS Express and use it to run/debug the application (no extra configuration required).  Like the ASP.NET Web Server, IIS Express will show up in your task-bar tray when running:

You can right-click and click “exit” on the icon above to quickly shutdown IIS Express.  You can also right-click and pull up a list of all sites running with it, as well as the directory location and .NET versions they are running under:

Two cool things to notice above:

1) The “Test Site” we are running, as well as IIS Express itself, live under the c:\users\[username] folder on disk. This enables non-administrator usage of IIS Express and sites – and enables a bunch of scenarios not possible with the full IIS today (including the ability to run IIS Express in both a locked-down enterprise environment as well as a locked-down school shared computer environment).

2) The “Test Site” we are running above using IIS Express supports both HTTP and HTTPS access.  IIS Express automatically installs a “self-signed certificate” and enables URL ACLs and SSL Certificates for ports so that developers (running as non-administrators on a machine) can use SSL without needing to elevate their accounts or setup any additional configuration.  This enables you to configure secure pages within your applications (like Logon forms) for SSL and run/test them at development time just like they’ll work on your real web-server.

IIS 7.x Feature Set

IIS Express is as easy to run and use as the ASP.NET Web Server you are familiar with today.  But because IIS Express is based on the IIS 7x codebase, you have a full web-server feature-set that you can use.  This means you can build and run your applications just they’ll work on a real production web-server.  In addition to scenarios like SSL, you can take advantage of the IIS 7.x URL Rewriter module, Media Extensions, Dynamic Compression, Advanced Logging, Custom Security and other rich modules now available.

In addition to supporting ASP.NET, IIS Express also supports Classic ASP and other file-types and extensions supported by IIS – which also makes it ideal for sites that combine a variety of different technologies.

Summary

We think IIS Express makes it even easier to build, run and test web applications.  It works with all versions of ASP.NET and supports all ASP.NET application types (including obviously ASP.NET Web Forms and ASP.NET MVC applications).  Best of all – you do not need to change any code to take advantage of it.  You’ll be able to optionally use it with all your current projects today.

We’ll be releasing the first public beta of IIS Express shortly. With the beta you’ll be able to right-click on a file-system folder and have IIS Express launch a web-site based on that file-system location. We’ll also be releasing a patch for VS 2010 and Visual Web Developer 2010 Express later this year that will enable you to automatically launch and use IIS Express in place of VS’s built-in ASP.NET Developer Server.  Future versions of Visual Studio will then ship with this functionality built-in.

Re-Register ASP.Net with IIS

Background Various error conditions during installation or running the VersionOne application may be caused by issues with the ASP.Net setup within IIS. These issues can often be solved by re-registering ASP.Net with IIS to ensure the correct files are recognized by the web server. Use the Procedure below to run the IIS Registration tool. Process ASP.NET can be re-registered with IIS. The specific method depends on the operating system being used. For more information on ASP.Net and the IIS Registration tool, see the related links below. Windows 2000/XP To fix this on Windows 2000 or Windows XP, run this command from the Start>Run box or a command prompt (assuming the system directory is C:\Windows): .Net 1.1: C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i .Net 2.0: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i Windows 2003 On Windows 2003, ASP.NET must be both installed and enabled.  To install ASP.NET: On the taskbar, click the Start button, point to Control Panel, and then click Add or Remove Programs. In the Add or Remove Programs dialog box, click Add/Remove Windows Components. In the Components box in the Windows Components Wizard, click the Web Application Server check box, and then click Next. When the Windows Components Wizard has finished configuring Windows Server 2003, click Finish. To enable ASP.NET, run this command from the Start>Run box or a command prompt (assuming the system directory is C:\Windows): .Net 1.1 (32-bit): C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i -enable .Net 2.0 (32-bit): C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i -enable .Net 2.0 (64-bit): C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i -enable

How to write to an event log by using Visual C#

This step-by-step article shows you how to add your own entries to the operating system's event log by using the Microsoft .NET Framework.

Requirements

The following list describes the recommended hardware, software, network infrastructure, and service packs that you will need:

• Microsoft Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows NT 4.0 Server
• Microsoft Visual Studio C#

Write to an event log

Event logging provides a standard, centralized way for your applications to record important software and hardware events. Windows supplies a standard user interface for viewing the logs, the Event Viewer. By using the common language's run-timeEventLog component, you can connect to existing event logs easily, on both local and remote computers, and write entries to these logs. You can also read entries from existing logs and create your own custom event logs. In its simplest form, writing to an event log involves only a few steps to create a sample application. To do this, follow these steps:

1. Open Visual Studio C#.
2. Create a new Console application in Visual C#. The Console application creates a public class and an empty Mainmethod for you.
3. Verify that the project references at least the System.dll file.
4. Use the using directive on the System and System.Diagnostics namespaces so that you do not have to qualify declarations from these namespaces later in your code. You must use these statements before any other declarations.
   
   

   using System;
   using System.Diagnostics;
        

5. To write to an event log, you must have several pieces of information: Your message, the name of the log you to which you want to write (which will be created if it does not already exist), and a string that represents the source of the event. You can register a particular source with only a single event log; if you want to write messages to more than one log, you must define multiple sources.
   
   

   string sSource;
   string sLog;
   string sEvent;
   
   sSource = "dotNET Sample App";
   sLog = "Application";
   sEvent = "Sample Event";
        

6. Use two static methods of the EventLog class to check whether your source exists, and then, if the source does not exist, to create this source that is associated with a particular event log. If the log name that you specify does not exist, the name is created automatically when you write your first entry to the log. By default, if you do not supply a log name to the CreateEventSource method, the log file is named "Application Log."
   
   

   if (!EventLog.SourceExists(sSource))
    EventLog.CreateEventSource(sSource,sLog);
        

7. To write a message to an event log, you can use the EventLog.WriteEntry static method. This method has several different overloaded versions. The following sample code shows the simplest method, which takes a source string and your message, and one of the more complex methods, which supports specifying the event ID and event type:
   
   

   EventLog.WriteEntry(sSource,sEvent);
   EventLog.WriteEntry(sSource, sEvent, EventLogEntryType.Warning,  234);
        

8. Save your application. Run your application, and then check the Application log in the Event Viewer to see your new events.

Complete code listing

using System;
using System.Diagnostics;

namespace WriteToAnEventLog_csharp
{
 /// Summary description for Class1.
 class Class1
 {
  static void Main(string[] args)
  {
   string sSource;
   string sLog;
   string sEvent;

   sSource = "dotNET Sample App";
   sLog = "Application";
   sEvent = "Sample Event";

   if (!EventLog.SourceExists(sSource))
    EventLog.CreateEventSource(sSource,sLog);

   EventLog.WriteEntry(sSource,sEvent);
   EventLog.WriteEntry(sSource, sEvent,
    EventLogEntryType.Warning, 234);
  }
 }
}
    

How to view and manage event logs in Event Viewer in Windows XP

Event Viewer

In Windows XP, an event is any significant occurrence in the system or in a program that requires users to be notified, or an entry added to a log. The Event Log Service records application, security, and system events in Event Viewer. With the event logs in Event Viewer, you can obtain information about your hardware, software, and system components, and monitor security events on a local or remote computer. Event logs can help you identify and diagnose the source of current system problems, or help you predict potential system problems.

Event Log Types

A Windows XP-based computer records events in the following three logs:

• Application log
  
  The application log contains events logged by programs. For example, a database program may record a file error in the application log. Events that are written to the application log are determined by the developers of the software program.
• Security log
  
  The security log records events such as valid and invalid logon attempts, as well as events related to resource use, such as the creating, opening, or deleting of files. For example, when logon auditing is enabled, an event is recorded in the security log each time a user attempts to log on to the computer. You must be logged on as Administrator or as a member of the Administrators group in order to turn on, use, and specify which events are recorded in the security log.
• System log
  
  The system log contains events logged by Windows XP system components. For example, if a driver fails to load during startup, an event is recorded in the system log. Windows XP predetermines the events that are logged by system components.

How to View Event Logs

To open Event Viewer, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, click Event Viewer.
   
   The Application, Security, and System logs are displayed in the Event Viewer window.

How to View Event Details

To view the details of an event, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, expand Event Viewer, and then click the log that contains the event that you want to view.
3. In the details pane, double-click the event that you want to view.
   
   The Event Properties dialog box containing header information and a description of the event is displayed.
   
   To copy the details of the event, click the Copy button, then open a new document in the program in which you want to paste the event (for example, Microsoft Word), and then click Paste on the Edit menu.
   
   To view the description of the previous or next event, click the UP ARROW or DOWN ARROW.

How to Interpret an Event

Each log entry is classified by type, and contains header information, and a description of the event.

Event Header

The event header contains the following information about the event:

• Date
  
  The date the event occurred.
• Time
  
  The time the event occurred.
• User
  
  The user name of the user that was logged on when the event occurred.
• Computer
  
  The name of the computer where the event occurred.
• Event ID
  
  An event number that identifies the event type. The Event ID can be used by product support representatives to help understand what occurred in the system.
• Source
  
  The source of the event. This can be the name of a program, a system component, or an individual component of a large program.
• Type
  
  The type of event. This can be one of the following five types: Error, Warning, Information, Success Audit, or Failure Audit.
• Category
  
  A classification of the event by the event source. This is primarily used in the security log.

Event Types

The description of each event that is logged depends on the type of event. Each event in a log can be classified into one of the following types:

• Information
  
  An event that describes the successful operation of a task, such as an application, driver, or service. For example, an Information event is logged when a network driver loads successfully.
• Warning
  
  An event that is not necessarily significant, however, may indicate the possible occurrence of a future problem. For example, a Warning message is logged when disk space starts to run low.
• Error
  
  An event that describes a significant problem, such as the failure of a critical task. Error events may involve data loss or loss of functionality. For example, an Error event is logged if a service fails to load during startup.
• Success Audit (Security log)
  
  An event that describes the successful completion of an audited security event. For example, a Success Audit event is logged when a user logs on to the computer.
• Failure Audit (Security log)
  
  An event that describes an audited security event that did not complete successfully. For example, a Failure Audit may be logged when a user cannot access a network drive.

How to Find Events in a Log

The default view of event logs is to list all its entries. If you want to find a specific event, or view a subset of events, you can either search the log, or you can apply a filter to the log data.

How to Search for a Specific Log Event

To search for a specific log event, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, expand Event Viewer, and then click the log that contains the event that you want to view.
3. On the View menu, click Find.
4. Specify the options for the event that you want to view in the Find dialog box, and then click Find Next.

The event that matches your search criteria is highlighted in the details pane. Click Find Next to locate the next occurrence of an event as defined by your search criteria.

How to Filter Log Events

To filter log events, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, expand Event Viewer, and then click the log that contains the event that you want to view.
3. On the View menu, click Filter.
4. Click the Filter tab (if it is not already selected).
5. Specify the filter options that you want, and then click OK.

Only events that match your filter criteria are displayed in the details pane.

To return the view to display all log entries, click Filter on the View menu, and then click Restore Defaults.

How to Manage Log Contents

By default, the initial maximum of size of a log is set to 512 KB, and when this size is reached, new events overwrite older events as needed. Depending on your requirements, you can change these settings, or clear a log of its contents.

How to Set Log Size and Overwrite Options

To specify log size and overwrite options, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, expand Event Viewer, and then right-click the log in which you want to set size and overwrite options.
3. Under Log size, type the size that you want in the Maximum log size box.
4. Under When maximum log size is reached, click the overwrite option that you want.
5. If you want to clear the log contents, click Clear Log.
6. Click OK.

How to Archive a Log

If you want to save your log data, you can archive event logs in any of the following formats:

• Log-file format (.evt)
• Text-file format (.txt)
• Comma-delimited text-file format (.csv)

To archive a log, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, expand Event Viewer, and then right-click the log in which you want to archive, and then click Save Log File As.
3. Specify a file name and location where you want to save the file. In the Save as type box, click the format that you want, and then click Save.

The log file is saved in the format that you specified.

JQuery - BlockUI for Process loading Image

Steps to run Block UI:

Step 1: Copy and add the jquery.blockUI.js in project from the below code
Step 2: Add $.blockUI() to start loading image & $.unblockUI() to stop loading image

Note: We can modify the jquery.blockUI to add our custom messages

What is jQuery BlockUI?

The jQuery BlockUI Plugin lets you simulate synchronous behavior when using AJAX, without locking the browser^[*]. When activated, it will prevent user activity with the page (or part of the page) until it is deactivated. BlockUI adds elements to the DOM to give it both the appearance and behavior of blocking user interaction.

Usage is very simple; to block user activity for the page:

$.blockUI();

Blocking with a custom message:

$.blockUI({ message: '<h1><img src="busy.gif" /> Just a moment...</h1>' });

Blocking with custom style:

$.blockUI({ css: { backgroundColor: '#f00', color: '#fff'} });

To unblock the page:

$.unblockUI();

If you want to use the default settings and have the UI blocked for all ajax requests, it's as easy as this:

$(document).ajaxStart($.blockUI).ajaxStop($.unblockUI);

[*] Using the XMLHttpRequest object in synchronous mode causes the entire browser to lock until the remote call completes. This is usually not a desirable behavior.

jquery.blockUI.js

/*!

* jQuery blockUI plugin

* Version 2.50 (04-OCT-2012)

* @requires jQuery v1.3 or later

*

* Examples at:
http://malsup.com/jquery/block/

* Copyright (c) 2007-2012 M. Alsup

* Dual licensed under the MIT and
GPL licenses:

*
http://www.opensource.org/licenses/mit-license.php

*
http://www.gnu.org/licenses/gpl.html

*

* Thanks to Amir-Hossein Sobhi for
some excellent contributions!

*/



; (function () {

    "use strict";



    function setup($) {

        if (/^1\.(0|1|2)/.test($.fn.jquery)) {

            /*global alert:true */

           
alert('blockUI requires jQuery v1.3 or
later!  You are using v' +
$.fn.jquery);

            return;

        }



       
$.fn._fadeIn = $.fn.fadeIn;



        var noOp = $.noop || function
() { };



        // this bit is to ensure we don't call setExpression
when we shouldn't (with extra muscle to handle

        // retarded userAgent strings on Vista)

        var msie = /MSIE/.test(navigator.userAgent);

        var ie6 = /MSIE 6.0/.test(navigator.userAgent);

        var mode = document.documentMode || 0;

        // var setExpr = msie && (($.browser.version
< 8 && !mode) || mode < 8);

        var setExpr = $.isFunction(document.createElement('div').style.setExpression);



        // global $ methods for blocking/unblocking the entire
page

       
$.blockUI = function (opts) {
install(window, opts); };

       
$.unblockUI = function (opts) {
remove(window, opts); };



        // convenience method for quick growl-like notifications  (http://www.google.com/search?q=growl)

       
$.growlUI = function (title, message,
timeout, onClose) {

            var $m = $('<div
class="growlUI"></div>');

            if (title) $m.append('<h1>'
+ title + '</h1>');

            if (message) $m.append('<h2>'
+ message + '</h2>');

            if (timeout === undefined) timeout = 3000;

           
$.blockUI({

               
message: $m, fadeIn: 700, fadeOut: 1000, centerY: false,

               
timeout: timeout, showOverlay: false,

                onUnblock: onClose,

               
css: $.blockUI.defaults.growlCSS

           
});

        };



        // plugin method for blocking element content

       
$.fn.block = function (opts) {

            var fullOpts = $.extend({}, $.blockUI.defaults, opts
|| {});

            this.each(function ()
{

               
var $el = $(this);

               
if (fullOpts.ignoreIfBlocked &&
$el.data('blockUI.isBlocked'))

                   
return;

               
$el.unblock({ fadeOut: 0 });

           
});



            return this.each(function () {

               
if ($.css(this,
'position') == 'static')

                   
this.style.position = 'relative';

               
this.style.zoom = 1; // force 'hasLayout' in ie

               
install(this, opts);

            });

        };



        // plugin method for unblocking element content

       
$.fn.unblock = function (opts) {

            return this.each(function () {

               
remove(this, opts);

           
});

        };



       
$.blockUI.version = 2.50; // 2nd
generation blocking at no extra cost!



        // override these in your code to change the default
behavior and style

       
$.blockUI.defaults = {

            // message displayed when blocking (use null for no
message)

           
message: '<h1>Please
wait...</h1>',



           
title: null,   // title string; only used when theme
== true

           
draggable: true, // only used when theme == true (requires jquery-ui.js to be loaded)



           
theme: false, //
set to true to use with jQuery UI themes



            // styles for the message when blocking; if you wish to
disable

            // these and use an external stylesheet then do this in
your code:

            // $.blockUI.defaults.css = {};

           
css: {

               
padding: 0,

               
margin: 0,

               
width: '30%',

               
top: '40%',

               
left: '35%',

               
textAlign: 'center',

               
color: '#000',

               
border: '3px solid #aaa',

               
backgroundColor: '#fff',

               
cursor: 'wait'

           
},



            // minimal style set used when themes are used

           
themedCSS: {

               
width: '30%',

               
top: '40%',

                left: '35%'

           
},



            // styles for the overlay

           
overlayCSS: {

               
backgroundColor: '#000',

               
opacity: 0.6,

               
cursor: 'wait'

           
},



            // styles applied when using $.growlUI

           
growlCSS: {

               
width: '350px',

               
top: '10px',

               
left: '',

               
right: '10px',

               
border: 'none',

               
padding: '5px',

                opacity: 0.6,

               
cursor: 'default',

               
color: '#fff',

               
backgroundColor: '#000',

               
'-webkit-border-radius': '10px',

               
'-moz-border-radius': '10px',

               
'border-radius': '10px'

           
},



            // IE issues: 'about:blank' fails on HTTPS and
javascript:false is s-l-o-w

            // (hat tip to Jorge H. N. de Vasconcelos)

            /*jshint scripturl:true */

           
iframeSrc: /^https/i.test(window.location.href || '') ? 'javascript:false'
: 'about:blank',



            // force usage of iframe in non-IE browsers (handy for
blocking applets)

           
forceIframe: false,



            // z-index for the blocking overlay

           
baseZ: 1000,



            // set these to true to have the message automatically
centered

           
centerX: true, //
<-- only effects element blocking (page block controlled via css above)

           
centerY: true,



            // allow body element to be stetched in ie6; this makes
blocking look better

            // on "short" pages.  disable if you wish to prevent changes to the
body height

           
allowBodyStretch: true,



            // enable if you want key and mouse events to be
disabled for content that is blocked

           
bindEvents: true,



            // be default blockUI will supress tab navigation from
leaving blocking content

            // (if bindEvents is true)

           
constrainTabKey: true,



            // fadeIn time in millis; set to 0 to disable fadeIn on
block

           
fadeIn: 200,



            // fadeOut time in millis; set to 0 to disable fadeOut
on unblock

           
fadeOut: 400,



            // time in millis to wait before auto-unblocking; set
to 0 to disable auto-unblock

           
timeout: 0,



            // disable if you don't want to show the overlay

           
showOverlay: true,



            // if true, focus will be placed in the first available
input field when

            // page blocking

           
focusInput: true,



            // suppresses the use of overlay styles on FF/Linux
(due to performance issues with opacity)

            // no longer needed in 2012

            // applyPlatformOpacityRules: true,



            // callback method invoked when fadeIn has completed
and blocking message is visible

           
onBlock: null,



            // callback method invoked when unblocking has
completed; the callback is

            // passed the element that has been unblocked (which is
the window object for page

            // blocks) and the options that were passed to the
unblock call:

            //       onUnblock(element,
options)

           
onUnblock: null,



            // don't ask; if you really must know:
http://groups.google.com/group/jquery-en/browse_thread/thread/36640a8730503595/2f6a79a77a78e493#2f6a79a77a78e493

           
quirksmodeOffsetHack: 4,



            // class name of the message block

           
blockMsgClass: 'blockMsg',



            // if it is already blocked, then ignore it (don't
unblock and reblock)

           
ignoreIfBlocked: false

        };



        // private data and functions follow...



        var pageBlock = null;

        var pageBlockEls = [];



        function install(el, opts) {

            var css, themedCSS;

            var full = (el == window);

            var msg = (opts && opts.message !== undefined
? opts.message : undefined);

           
opts = $.extend({}, $.blockUI.defaults, opts || {});



            if (opts.ignoreIfBlocked && $(el).data('blockUI.isBlocked'))

               
return;



           
opts.overlayCSS = $.extend({}, $.blockUI.defaults.overlayCSS,
opts.overlayCSS || {});

           
css = $.extend({}, $.blockUI.defaults.css, opts.css || {});

           
themedCSS = $.extend({}, $.blockUI.defaults.themedCSS, opts.themedCSS ||
{});

           
msg = msg === undefined ? opts.message : msg;



            // remove the current block (if there is one)

            if (full && pageBlock)

               
remove(window, { fadeOut: 0 });



            // if an existing element is being used as the blocking
content then we capture

            // its current place in the DOM (and current display
style) so we can restore

            // it when we unblock

            if (msg && typeof
msg != 'string' && (msg.parentNode ||
msg.jquery)) {

               
var node = msg.jquery ? msg[0] : msg;

               
var data = {};

               
$(el).data('blockUI.history', data);

                data.el = node;

               
data.parent = node.parentNode;

               
data.display = node.style.display;

               
data.position = node.style.position;

               
if (data.parent)

                   
data.parent.removeChild(node);

            }



           
$(el).data('blockUI.onUnblock',
opts.onUnblock);

            var z = opts.baseZ;



            // blockUI uses 3 layers for blocking, for simplicity
they are all used on every platform;

            // layer1 is the iframe layer which is used to supress
bleed through of underlying content

            // layer2 is the overlay layer which has opacity and a
wait cursor (by default)

            // layer3 is the message content that is displayed
while blocking

            var lyr1, lyr2, lyr3, s;

            if (msie || opts.forceIframe)

               
lyr1 = $('<iframe
class="blockUI" style="z-index:' + (z++) + ';display:none;border:none;margin:0;padding:0;position:absolute;width:100%;height:100%;top:0;left:0"
src="' + opts.iframeSrc + '"></iframe>');

            else

               
lyr1 = $('<div class="blockUI"
style="display:none"></div>');



            if (opts.theme)

               
lyr2 = $('<div class="blockUI
blockOverlay ui-widget-overlay" style="z-index:' + (z++) + ';display:none"></div>');

            else

               
lyr2 = $('<div class="blockUI
blockOverlay" style="z-index:' + (z++) + ';display:none;border:none;margin:0;padding:0;width:100%;height:100%;top:0;left:0"></div>');



            if (opts.theme && full) {

               
s = '<div class="blockUI ' +
opts.blockMsgClass + ' blockPage ui-dialog ui-widget
ui-corner-all" style="z-index:' + (z + 10) + ';display:none;position:fixed">';

               
if (opts.title) {

                   
s += '<div class="ui-widget-header
ui-dialog-titlebar ui-corner-all blockTitle">' + (opts.title || '&nbsp;') + '</div>';

               
}

               
s += '<div class="ui-widget-content
ui-dialog-content"></div>';

               
s += '</div>';

            }

            else if (opts.theme) {

               
s = '<div class="blockUI ' +
opts.blockMsgClass + ' blockElement ui-dialog
ui-widget ui-corner-all" style="z-index:' + (z + 10) + ';display:none;position:absolute">';

               
if (opts.title) {

              
     s += '<div
class="ui-widget-header ui-dialog-titlebar ui-corner-all
blockTitle">' + (opts.title || '&nbsp;')
+ '</div>';

               
}

               
s += '<div class="ui-widget-content
ui-dialog-content"></div>';

               
s += '</div>';

            }

            else if (full) {

               
s = '<div class="blockUI ' +
opts.blockMsgClass + ' blockPage"
style="z-index:' + (z + 10) + ';display:none;position:fixed"></div>';

            }

            else {

               
s = '<div class="blockUI ' +
opts.blockMsgClass + ' blockElement"
style="z-index:' + (z + 10) + ';display:none;position:absolute"></div>';

            }

           
lyr3 = $(s);



            // if we have a message, style it

            if (msg) {

               
if (opts.theme) {

                   
lyr3.css(themedCSS);

                   
lyr3.addClass('ui-widget-content');

               
}

               
else

                   
lyr3.css(css);

            }



            // style the overlay

            if (!opts.theme /*&&
(!opts.applyPlatformOpacityRules)*/)

               
lyr2.css(opts.overlayCSS);

           
lyr2.css('position', full ? 'fixed' : 'absolute');



            // make iframe layer transparent in IE

            if (msie || opts.forceIframe)

                lyr1.css('opacity',
0.0);



            //$([lyr1[0],lyr2[0],lyr3[0]]).appendTo(full ? 'body' :
el);

            var layers = [lyr1, lyr2, lyr3], $par = full ? $('body') : $(el);

           
$.each(layers, function () {

               
this.appendTo($par);

           
});



            if (opts.theme && opts.draggable &&
$.fn.draggable) {

               
lyr3.draggable({

                   
handle: '.ui-dialog-titlebar',

                   
cancel: 'li'

               
});

            }



            // ie7 must use absolute positioning in quirks mode and
to account for activex issues (when scrolling)

            var expr = setExpr && (!$.support.boxModel ||
$('object,embed', full ? null : el).length > 0);

            if (ie6 || expr) {

              
 //
give body 100% height

               
if (full &&
opts.allowBodyStretch && $.support.boxModel)

                   
$('html,body').css('height', '100%');



               
// fix ie6 issue when blocked element has
a border width

               
if ((ie6 || !$.support.boxModel)
&& !full) {

                   
var t = sz(el, 'borderTopWidth'),
l = sz(el, 'borderLeftWidth');

                   
var fixT = t ? '(0
- ' + t + ')' : 0;

                   
var fixL = l ? '(0
- ' + l + ')' : 0;

               
}



               
// simulate fixed position

               
$.each(layers, function (i, o) {

                   
var s = o[0].style;

                   
s.position = 'absolute';

                   
if (i < 2) {

                        if (full)

                            s.setExpression('height', 'Math.max(document.body.scrollHeight,
document.body.offsetHeight) - (jQuery.support.boxModel?0:' +
opts.quirksmodeOffsetHack + ') + "px"');

                        else

                            s.setExpression('height', 'this.parentNode.offsetHeight
+ "px"');

                        if (full)

                            s.setExpression('width', 'jQuery.support.boxModel
&& document.documentElement.clientWidth || document.body.clientWidth +
"px"');

              
         else

                            s.setExpression('width', 'this.parentNode.offsetWidth
+ "px"');

                        if (fixL) s.setExpression('left',
fixL);

                        if (fixT) s.setExpression('top',
fixT);

                   
}

                   
else if
(opts.centerY) {

                        if (full) s.setExpression('top',
'(document.documentElement.clientHeight ||
document.body.clientHeight) / 2 - (this.offsetHeight / 2) + (blah =
document.documentElement.scrollTop ? document.documentElement.scrollTop :
document.body.scrollTop) + "px"');

                        s.marginTop = 0;

                   
}

                   
else if
(!opts.centerY && full) {

                        var top = (opts.css && opts.css.top) ? parseInt(opts.css.top,
10) : 0;

                        var expression = '((document.documentElement.scrollTop
? document.documentElement.scrollTop : document.body.scrollTop) + ' +
top + ') + "px"';

                        s.setExpression('top', expression);

                   
}

               
});

            }



            // show the message

            if (msg) {

               
if (opts.theme)

                   
lyr3.find('.ui-widget-content').append(msg);

               
else

                   
lyr3.append(msg);

               
if (msg.jquery || msg.nodeType)

                   
$(msg).show();

            }



            if ((msie || opts.forceIframe) &&
opts.showOverlay)

               
lyr1.show(); // opacity is zero

            if (opts.fadeIn) {

               
var cb = opts.onBlock ? opts.onBlock :
noOp;

               
var cb1 = (opts.showOverlay &&
!msg) ? cb : noOp;

               
var cb2 = msg ? cb : noOp;

               
if (opts.showOverlay)

                   
lyr2._fadeIn(opts.fadeIn, cb1);

               
if (msg)

                   
lyr3._fadeIn(opts.fadeIn, cb2);

            }

            else {

               
if (opts.showOverlay)

                   
lyr2.show();

               
if (msg)

                   
lyr3.show();

                if
(opts.onBlock)

                   
opts.onBlock();

            }



            // bind key and mouse events

           
bind(1, el, opts);



            if (full) {

               
pageBlock = lyr3[0];

               
pageBlockEls = $(':input:enabled:visible',
pageBlock);

               
if (opts.focusInput)

                   
setTimeout(focus, 20);

            }

            else

               
center(lyr3[0], opts.centerX, opts.centerY);



            if (opts.timeout) {

               
// auto-unblock

               
var to = setTimeout(function () {

                   
if (full)

                        $.unblockUI(opts);

                   
else

                        $(el).unblock(opts);

               
}, opts.timeout);

                $(el).data('blockUI.timeout',
to);

            }

        }



        // remove the block

        function remove(el, opts) {

            var full = (el == window);

            var $el = $(el);

            var data = $el.data('blockUI.history');

            var to =
$el.data('blockUI.timeout');

            if (to) {

               
clearTimeout(to);

               
$el.removeData('blockUI.timeout');

            }

           
opts = $.extend({}, $.blockUI.defaults, opts || {});

           
bind(0, el, opts); // unbind events



            if (opts.onUnblock === null)
{

               
opts.onUnblock = $el.data('blockUI.onUnblock');

               
$el.removeData('blockUI.onUnblock');

            }



            var els;

            if (full) // crazy selector to handle odd field errors in ie6/7

               
els = $('body').children().filter('.blockUI').add('body
> .blockUI');

            else

               
els = $el.find('>.blockUI');



            if (full)

               
pageBlock = pageBlockEls = null;



            if (opts.fadeOut) {

               
els.fadeOut(opts.fadeOut);

               
setTimeout(function () { reset(els,
data, opts, el); }, opts.fadeOut);

            }

            else

               
reset(els, data, opts, el);

        }



        // move blocking element back into the DOM where it
started

        function reset(els, data, opts, el) {

           
els.each(function (i, o) {

               
// remove via DOM calls so we don't lose
event handlers

               
if (this.parentNode)

                   
this.parentNode.removeChild(this);

           
});



            if (data && data.el) {

               
data.el.style.display = data.display;

               
data.el.style.position = data.position;

                if
(data.parent)

                   
data.parent.appendChild(data.el);

               
$(el).removeData('blockUI.history');

            }



            if (typeof
opts.onUnblock == 'function')

               
opts.onUnblock(el, opts);



            // fix issue
in Safari 6 where block artifacts remain until reflow

            var body = $(document.body), w = body.width(), cssW =
body[0].style.width;

           
body.width(w - 1).width(w);

           
body[0].style.width = cssW;

        }



        // bind/unbind the handler

        function bind(b, el, opts) {

            var full = el == window, $el = $(el);



            // don't bother unbinding if there is nothing to unbind

            if (!b && (full && !pageBlock ||
!full && !$el.data('blockUI.isBlocked')))

               
return;



           
$el.data('blockUI.isBlocked', b);



            // don't bind events when overlay is not in use or if
bindEvents is false

            if (!opts.bindEvents || (b &&
!opts.showOverlay))

               
return;



            // bind anchors and inputs for mouse and key events

            var events = 'mousedown
mouseup keydown keypress touchstart touchend touchmove';

            if (b)

               
$(document).bind(events, opts, handler);

            else

               
$(document).unbind(events, handler);



            // former impl...

            //             var
$e = $('a,:input');

            //             b ?
$e.bind(events, opts, handler) : $e.unbind(events, handler);

        }



        // event handler to suppress keyboard/mouse events when
blocking

        function handler(e) {

            // allow tab navigation (conditionally)

            if (e.keyCode && e.keyCode == 9) {

               
if (pageBlock &&
e.data.constrainTabKey) {

               
    var
els = pageBlockEls;

                   
var fwd = !e.shiftKey &&
e.target === els[els.length - 1];

                   
var back = e.shiftKey &&
e.target === els[0];

                   
if (fwd || back) {

                        setTimeout(function () { focus(back); }, 10);

                        return false;

                   
}

               
}

            }

            var opts = e.data;

            // allow events within the message content

            if ($(e.target).parents('div.'
+ opts.blockMsgClass).length > 0)

               
return true;



            // allow events for content that is not being blocked

            return $(e.target).parents().children().filter('div.blockUI').length === 0;

        }



        function focus(back) {

            if (!pageBlockEls)

               
return;

            var e = pageBlockEls[back === true ? pageBlockEls.length - 1 : 0];

            if (e)

               
e.focus();

        }



        function center(el, x, y) {

            var p = el.parentNode, s = el.style;

            var l = ((p.offsetWidth - el.offsetWidth) / 2) -
sz(p, 'borderLeftWidth');

            var t = ((p.offsetHeight - el.offsetHeight) / 2) -
sz(p, 'borderTopWidth');

            if (x) s.left = l > 0 ? (l + 'px') : '0';

            if (y) s.top = t > 0 ? (t + 'px') : '0';

        }



        function sz(el, p) {

            return parseInt($.css(el, p), 10) || 0;

        }



    }





    /*global define:true */

    if (typeof define ===
'function' && define.amd &&
define.amd.jQuery) {

       
define(['jquery'], setup);

    } else {

       
setup(jQuery);

    }



})();