Development World

New Development Technologies , Computer Last News , Tips & Tricks , UI , CSS , HTML , ASP , C# , .net Framework , Patterns & Practices & etc

How to: Create Synchronous HTTP Handlers

This topic illustrates the code for an HTTP handler that performs synchronous processing of requests for resources in an ASP.NET application whose URL ends with .sample. The code example illustrates the following:

  • The code for an HTTP handler class. The class must implement the ProcessRequest method and the IsReusable property.

  • The elements that are required in a Web.config file to register the handler and map the .sample file name extension to it.

  • In Internet Information Services (IIS), how to map the .sample file name extension to ASP.NET.


The ASP.NET Development Server will serve the request for the new resource after the configuration file is changed to include a reference to the new handler. To enable IIS to serve the request, see the procedure below.

When users request a resource whose URL ends in .sample, the Web server forwards the request to ASP.NET. ASP.NET then calls the HTTP handler, which returns a response. The response is created dynamically by the handler; there is no need for a file with the file name extension .sample to exist. For more information about how ASP.NET interacts with the Web server, see ASP.NET Life Cycle.

To create the custom HelloWorldHandler HTTP handler class

  1. In your Web site's App_Code directory, create a class named HelloWorldHandler.

  2. Add the following code to your class file.

    using System.Web;
    public class HelloWorldHandler : IHttpHandler
        public HelloWorldHandler()
        public void ProcessRequest(HttpContext context)
            HttpRequest Request = context.Request;
            HttpResponse Response = context.Response;
            // This handler is called whenever a file ending
            // in .sample is requested. A file with that extension
            // does not need to exist.
            Response.Write("<h1>Hello from a synchronous custom HTTP handler.</h1>");
        public bool IsReusable
            // To enable pooling, return true here.
            // This keeps the handler in memory.
            get { return false; }

Registering a Custom HTTP Handler

After you have created the custom HTTP handler class, you must register it in the application's Web.config file. This allows ASP.NET to find the handler when ASP.NET receives requests made to resources whose URL ends with .sample.

To register a custom HTTP handler in the Web.config file

  1. Add a Web.config file to your Web site if one does not already exist.

  2. Add the following highlighted element to your Web.config file.

                <add verb="*" path="*.sample" 

    The code registers your custom handler by class name and maps the .sample file name extension to that handler.

Configuring IIS 6.0 for an HTTP Handler Extension

IIS passes requests for only certain file types to ASP.NET to service. By default, files with file name extensions such as .aspx, .ascx, .asmx, are already mapped in IIS 6.0 to the ASP.NET ISAPI extension (Aspnet_isapi.dll). However, if you want ASP.NET to handle custom URL extensions, you must map the extensions in IIS. For more information, see ASP.NET Life Cycle.

To map the .sample file name extension to ASP.NET in IIS 6.0

  1. Open Internet Information Services (IIS) Manager.

  2. Right-click the name of your application, and then click Properties.


    For instructions for creating an ASP.NET application, see How to: Create and Configure Local ASP.NET Web Sites in IIS.

  3. Click the Virtual Directory tab, and then click Configuration.

  4. On the Mappings tab, click Add.

    The Add/Edit Application Extension Mapping dialog box is displayed.

  5. In the Executable box, type or browse to the file Aspnet_isapi.dll. By default, the file is in the following location.


    You can get the complete path and file name from other mappings, such as the mapping to .aspx files.

  6. In the Extension box, type .sample.

  7. Clear the Verify that file exists check box.

  8. Click OK and then close IIS Manager.

Testing the Custom HTTP Handler

After you have created and registered your custom HTTP handler, you can test it by requesting a resource that has a .sample file name extension.

To test your custom HTTP handler

  • In your browser, enter a URL that points to your Web application and that ends in .sample, such as the following:


    The text defined in the HelloWorldHandler class is displayed.

Reference : MSDN

Visual Studio Can not Display Web Application :-: Webdev can not connect to site

Hey There , I had a problem that I've posted another post for this same problem Unable to connect to Visual Studio's Localhost Web Server , mY problem solved but after a while my problem backed again , wow whats up, the bug happens when I wanted to  view my result in a browser , a blank page open and try to connect to website but nothing happen ,

this is simple to solve this problem just change Localhost with , now youv'e done the impossible !!

Specially I have to thanks , ( Master ) Afshar Mohebbi to help me to solve this problem , Thank You Man ;)

also I'll post another topic in this problem after a while

Comment here and say thank's to my friend

Console window for a Windows application in .NET

Have your ever felt the need to attach a Console window to your winform application?  If this is what you want, here is a article just for you.

I have not come across any possible way to show the Console window for a Windows application. So I tried my way with the help of Win32 API calls. Here is the list of APIs which will be needed:

public static extern Boolean AllocConsole();

public static extern Boolean FreeConsole();

public static extern IntPtr GetStdHandle(int nStdHandle);

public static extern bool SetConsoleTitle(String lpConsoleTitle);

[DllImport("kernel32.dll", SetLastError = true)]
public static extern bool SetConsoleTextAttribute(IntPtr hConsoleOutput, CharacterAttributes wAttributes);

//And here is the enumeration CharacterAttributes

public enum CharacterAttributes

private void Form1_Load(object sender, EventArgs e)
    bool flag = AllocConsole();

private void Form1_FormClosing(object sender, CancelEventArgs e)

    bool flag = FreeConsole();

//Put a button on the form and write the following code in to the Click event handler of the button.

private void button1_Click(object sender, EventArgs e)
    IntPtr hStdWin = GetStdHandle(-11);
   SetConsoleTitle(“My Console :)”);
   Console.WriteLine(”Hi from Window application.”);


//code ends here

Check this out, and if this is not you expected, then put your comments.

Reference :

5 Things You'll Love about Firefox 3

From the "Awesome Bar" to just plain better performance, the latest version of the open source browser includes some great improvements

A couple of months ago, I downloaded a beta version of Firefox 3 just to look at the new ideas Mozilla was working on. My intention was to try it for a couple days, then switch back to Firefox 2. I wasn't worried about stability (it's a browser after all -- what's the worst that can happen?). But the beta wasn't compatible with lots of my favorite extensions and who wants to live without them?

As it turns out, I'm still using a prerelease version of Firefox (they're at Release Candidate 1 now) and loving it, even without my beloved add-ons. The improvements Mozilla has made to the browser, while subtle, are so helpful that I didn't want to give them up. Here are five of my favorites.

1. Much Better Performance

Firefox in Task Manager

If you've used previous versions of Firefox you've likely had this experience, perhaps frequently: you're working away, but gradually become aware that something is horribly wrong with your PC. It's sluggish and apps take forever to load. You open up Task Manager and find that Firefox is chewing up 95 percent of your CPU cycles. Once you kill the browser and start over, you're running fine again.

I can't remember the last time I've had that experience with the Firefox 3 betas. Mozilla developers borrowed some memory management tricks from the Free BSD operating system for the Windows and Linux versions of Firefox. (They say memory management on Macs already worked pretty well.) The effect is clear. The browser is much less likely to commandeer too many system resources. And Firefox's developers worked to make sure that add-ons, notorious memory thieves, don't cause problems either. They've rolled in cycle collectors that help prevent extensions from locking up RAM and not giving it back. They're also distributing tools to third-party developers that will help them build more abstemious add-ons.

2. The "Awesome Bar"

Firefox's Location Bar

Okay, so the official name is the Location Bar, the field where you enter URLs you want to visit. But beta testers have nicknamed it the Awesome Bar and it is, well, pretty awesome. Enter text in the Location Bar and a dropdown list appears of pages from your browsing history that include that text, not just in the URL, but in the page title or the page's tag (see #4 below). The list even includes Gmail messages that include that word in the subject line. If you've already visited a Web page, there's a good chance it's useful to you. The Location Bar lets you very quickly search that useful subset of the Web.

3. Can't Miss Warnings

Firefox's malware warning screen

Lots of browsers have had phishing warnings before (including Firefox), but they've been wimpy. Usually they involve some part of the address bar changing color or some icon popping up near the URL. The problem is they're too easy to miss. I'm not looking at the address bar when I'm waiting for a page to load. I'm looking at the main well of the browser where the page will display.

But there's no danger of missing one of Firefox's new warnings. When you enter the URL of a suspected attack site, Firefox brings up a full-page warning. With a click, you can see a detailed explanation of why the site was blocked. Or you can just click "Get me out of here," which takes you to Firefox's start page. If you really want to live dangerously, there's a small link that lets you ignore the warning and proceed to the suspect site.

4. Better Bookmarks

Firefox's quick bookmarking

If you like a page, you just click the star in the Location Bar and it's a favorite. A dropdown box lets you name it, choose a folder to put it in or add a tag to categorize it. Bookmarks (and your browsing history) are now stored in a database, which means you don't have to spend so much time organizing bookmark folders. You can perform detailed searches of your bookmarks, then save that search as a special folder. Any new bookmarked page that fits the criteria automatically goes in the folder.

5. Whole-page Zooming

Zoom image in Firefox 2

If your eyes aren't what they used to be, it's nice to bump up the size of text on Web pages, as Firefox 2 will do. But it only changes the text size -- the other elements remain the same size. That makes for pages that look like The Incredible Hulk, with words bursting through the boxs and tabs that are supposed to contain them.

The new Firefox magnifies everything on the page equally. Everything remains in proportion, but becomes easier to read. And the next time you visit that page, it'll display at the same level of zoom.

Reference : PC World
نویسنده : Nasser Hajloo : ۱٠:٥۳ ‎ق.ظ ; ۱۳۸٧/۳/٤
Comments پيام هاي ديگران ()      لینک دائم

Windows Features Comparison



This white paper helps customers compare Windows Vista® advancements with Microsoft® Windows® XP Professional. Using this comparison, customers can adjust their expectations for the security, management, deployment, mobility, and productivity of either operating system. During the past year, Microsoft and its ecosystem has made great progress in improving the overall quality and performance of Windows Vista, making the Windows Vista Service Pack 1 (SP1) release a key milestone for broad enterprise deployments of Windows Vista. Microsoft recommends that all business customers who have not started to evaluate Windows Vista should start deployment planning and piloting Windows Vista with SP1. Windows Vista offers customers unique value—from increased security and data protection to improved mobility and productivity to capabilities that customers can use to optimize desktop infrastructures and reduce management costs. Microsoft knows that many customers will adopt Windows Vista gradually, through hardware refreshes (i.e., attrition). During hardware refresh, customers will co-manage Windows Vista and Windows XP. Enhancements to Windows XP with Service Pack 3 (SP3), such as Network Access Protection (NAP), make it easier for customers to more securely integrate both operating systems into their environments. During the transition, using Windows XP with SP3 will help ensure that client computers still running the Windows XP operating system have the most recent security and software updates. The remaining sections in this white paper compare the following features and capabilities of Windows XP with SP3 and Windows Vista with SP1: security, management, deployment, mobility, and productivity. For each feature or capability, each section compares key Windows Vista advancements against Windows XP.

Windows Feature Comparison







Windows XP with SP3


Windows Vista with SP1


Key differences


Security Development Lifecycle (SDL)


Developed for Windows XP with SP2.


The Microsoft SDL makes security a top priority throughout the development cycle by mandating a repeatable engineering process that every developer must follow, and by verifying that process before product release. The SDL is an evolving process that implements rigorous standards of secure design, coding, testing, review, and response for all Microsoft products. The SDL helps remove vulnerabilities and minimize the surface area for attacks, improves system and application integrity, and helps organizations more securely manage and isolate their networks.


  1. Although Microsoft has used the SDL extensively on several key products, Windows Vista is the first client operating system to be developed from start to finish using this new approach.



Windows Feature Comparison






Windows XP with SP3


Windows Vista with SP1


Key differences


Defense in depth


Buffer overruns trick software into running code that has been placed in areas of the computer’s memory that are set aside for data storage. The Data Execution Prevention (DEP) feature, which uses the no-execute (NX) feature of some processors, can reduce the impact of such vulnerabilities. Windows XP with SP3 supports DEP but does not enable it by default.


In Windows Vista, DEP is enabled by default for most components. Windows Vista introduces additional DEP policies that allow software developers to enable DEP in code, independent of system-wide compatibility-enforcement controls. This capability enables a higher percentage of NX-protected code in the software ecosystem. DEP works best with Address Space Layout Randomization (ASLR), another defense capability in Windows Vista that makes it more difficult for malicious code to exploit a system function. ASLR randomly assigns executable images, such as .dll and .exe files, to one of 256 possible locations in memory. This makes it more difficult for malicious code to locate and take advantage of functionality inside the executables. Because system services typically run with high system rights, these services have been a major target for malicious software attacks. To mitigate the threat, Windows Vista has introduced the concept of restricted services, or

service hardening. Restricted services can run under only the most restrictive rights possible, and they limit their activities to the minimum local computer or network resources that are required to fulfill their task.

  1. In Windows Vista, DEP is enabled by default for most components, and the operating system allows developers to enable DEP in their code.
  2.  Windows Vista includes ASLR, which makes it difficult for malicious code to exploit system functions.
  3.  Windows Vista introduces service hardening, which restricts the rights available to some system services.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Windows BitLocker™Drive Encryption




BitLocker Drive Encryption is a new data-protection feature in the Windows Vista Enterprise and Windows Vista Ultimate operating systems. The feature provides whole-volume encryption and supports encryption of multiple partitions. BitLocker Drive Encryption addresses the very real threats of data theft and data disclosure from lost, stolen, or inappropriately decommissioned computer hardware. This tightly integrated solution also provides for integrity checking of early boot components. Because businesses use of portable computers increases each year, the potential exposure of data on users’ computers presents a growing problem for organizations. Organizations can use BitLocker Drive Encryption to realize the benefits of mobile computing while helping to reduce risk and enable better compliance with corporate data-protection best practices.


  1. Windows Vista helps secure data by providing whole-volume encryption and protection of early boot components.
  2.  BitLocker Drive Encryption supports encryption of multiple volumes.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Windows Firewall


Windows XP provides firewall functionality that is enabled by default and that begins protecting users’ computers as soon as the operating system starts. In Windows XP, Windows Firewall includes inbound filtering.


Windows Vista provides firewall functionality that is enabled by default and that begins helping to protect a user’s computer as soon as Windows starts. Windows Firewall includes both inbound and outbound filtering and can prevent data from entering or leaving the computer. Windows Firewall also allows information technology (IT) professionals and home users to block applications, such as peer-to-peer sharing or instant messaging applications, from contacting or responding to other computers. Windows Firewall in Windows Vista is fully manageable through Group Policy and is dynamic, based on network type. Administrators can put different firewall rules into effect, depending on whether the computer is connected to a corporate (domain) network, a private (home) network, or a public (hotspot) network.


  1. Both operating systems include firewall functionality, but Windows Vista includes inbound and outbound filtering, whereas Windows XP includes only inbound filtering.
  2.  Windows Firewall in Windows Vista can dynamically apply rules based on the current network type, making the computer more secure on public networks.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Windows Internet Explorer® 7 Protected Mode




Internet Explorer 7 Protected Mode in Windows Vista provides additional defenses against malicious attackers who attempt to take over a user’s Web browser and run malicious code by using elevated rights. In Protected Mode, Internet Explorer 7 runs with reduced rights to help prevent user or system files and settings from being changed without the user’s explicit permission. The new Web browser architecture also introduces a

broker process that helps existing applications more securely elevate themselves above Protected Mode, if necessary. This additional defense helps verify that scripted actions or automatic processes are prevented from downloading data outside low-rights directories such as the Temporary Internet Files folder.

  1. Using Internet Explorer 7 to browse the Internet is more secure in Windows Vista than in Windows XP.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Microsoft ActiveX® Installer Service




Many organizations must install ActiveX controls on client computers to ensure that vital programs work properly. However, most ActiveX controls must be installed by a member of the Administrators group, and many organizations have configured or want to configure their users to run as standard users. As a result, organizations must repackage and deploy the ActiveX controls to the users. In addition, many of these ActiveX controls must be regularly updated. Many organizations find this to be a difficult and costly process to manage for standard users. With Windows Vista, IT pros can now easily deploy and update ActiveX controls in a standard user environment. The ActiveX Installer Service enables IT pros to use Group Policy to define approved host URLs that standard users can then use to install ActiveX controls.


  1. In Windows Vista, organizations can deploy, update, and manage ActiveX controls in environments that use standard user accounts.
  2.  In Windows Vista, organizations can use Group Policy to manage the installation of ActiveX controls.




Windows Feature Comparison






Windows XP with SP3


Windows Vista with SP1


Key differences


Group Policy settings


Group Policy helps IT professionals manage client computer configurations by allowing them to enforce thousands of Windows and application security and configuration settings. Examples include standard configuration enforcement, security settings and controls (ranging from public key policies to password policies), resource access, wireless networking, software installation, and user experience.


Managing client computer configurations with Windows Vista takes less time and is more effective, because hundreds more settings that target more scenarios are available in Group Policy. Areas with richer settings include wireless networking, removable storage device installation and use, Internet Explorer 7, printers, and power management.


  1. Windows Vista has more than 500 additional Group Policy settings compared to Windows XP.
  2.  In Windows Vista, Group Policy settings are better targeted at specific scenarios, such as wireless networking, power management, removable storage, and printer management.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Standard user accounts


Deploying standard user accounts was traditionally impractical, partly because users can’t change many common settings and partly because many applications require Administrator access to portions of the registry or file system (for example, C:\Program Files). As a result, many companies deploy Administrator accounts to users, reducing manageability and increasing security risk. Some companies overcome these challenges by deploying standard user accounts, and then punching specific holes in access control lists (ACLs), at a significant cost.


Windows Vista User Account Control (UAC) makes it more practical for companies to allow users, running under standard user accounts, to run applications and perform many common system configuration tasks, such as changing the time zone or installing a supported printer. Limiting the use of Administrator accounts to true administrators helps prevent users from making unauthorized system changes or installing unapproved programs that may contain a virus or spyware. In addition, file and registry redirection (virtualization) enables older applications to run in a standard user environment by redirecting the writes to a virtual store, thereby helping applications run as expected without modification. This capability provides application compatibility for earlier applications.


  1. Windows Vista makes using standard user or least-privilege user accounts more practical than in the past.
  2.  UAC notifies standard users and administrators before an administrative action is performed.
  3.  File and registry redirection helps ensure that applications write to user-specific file locations.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Reliability and diagnostics


Windows XP includes basic troubleshooting tools. However, a limited number of these tools automatically detect and repair common support problems. Windows XP can send basic telemetry data that helps Microsoft diagnose customer problems.


Windows Vista includes built-in diagnostics that automatically detect and diagnose common support problems and help users resolve the problems on their own. Problems that Windows Vista diagnostics address include failing disks, degraded performance, lack of network connectivity, and failure to start up properly. Windows Vista provides a broad set of troubleshooting tools, such as the following:

  1.  Windows Recovery Environment
  2.  Performance Monitor

Also, Windows Vista can optionally send telemetry data, including reliability data, which helps Microsoft improve customers’ experience with the operating system. Examples are the Customer Experience Improvement Program (CEIP) and Windows Error Reporting (WER), both of which are opt-in.


  1. Windows Vista automatically detects and repairs more support problems than Windows XP does, helping reduce support costs.
  2.  Windows Vista provides advanced troubleshooting tools, such as WER.
  3.  Windows Vista telemetry data helps Microsoft better identify and diagnose issues that affect customers.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Event management


Windows XP provides basic event management through Event Viewer. By using Event Viewer, users can view, filter, and archive events. Event logging in Windows XP remains largely unchanged from earlier Windows versions, and many Windows components still store event information in scattered text files.


Event Viewer has been completely rewritten to allow IT pros to create custom views that combine events from individual logs, discover events more easily, and link to scheduled tasks or scripts that should run when an event occurs. This new Windows Eventing system makes it much more practical for IT pros to use the event log to troubleshoot users’ problems. Windows Eventing also provides a central unified event store that developers can easily use for their applications, continuing to make troubleshooting easier for IT pros. And events are based on XML, which enables better integration with management tools. By using event forwarding, IT pros can centrally manage events from their computers, more easily and proactively identifying problems and correlating problems that affect multiple computers. Customers can forward events to computers running the Windows Server® 2008 operating system.


  1. Windows Vista introduces event forwarding, a new Event Viewer, and event automation.
  2.  In Windows Vista, XML-based events enable better integration with management tools.
  3.  Windows Vista consolidates events from most Windows components in the event log instead of in text files.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Task scheduling


The Task Scheduler in Windows XP provides essential scheduling capabilities. Users can schedule jobs to run daily, weekly, and so on. IT pros cannot easily create and manage tasks by using scripts, however. Instead, they must use a command-line program to manage tasks.


The Windows Vista Task Scheduler is backward-compatible with Windows XP. IT pros can also schedule tasks to launch in situations including the following:

  1.  When a specific event occurs
  2.  When users lock or unlock sessions
  3.  When the computer is idle
  4.  When the computer is on the corporate network

In addition, tasks can be run in sequence, enabling IT pros to schedule multiple tasks with the confidence that the tasks will not run simultaneously. To improve security and reduce maintenance related to password expirations, IT pros can run a task by using domain credentials instead of a local account that needs to be managed.


  1. Windows Vista enables IT pros to script tasks.
  2.  Windows Vista provides new scheduling options and the ability to run tasks in sequence.




Windows Feature Comparison






Windows XP with SP3


Windows Vista with SP1


Key differences


Image-based setup (IBS)


Windows XP is not delivered as an image. Instead, the Setup program installs and configures each Windows component. Non-Microsoft imaging tools are available for creating images, but these products are predominantly sector based. Tools included in the Windows Automated Installation Kit (Windows AIK) and Microsoft Deployment Toolkit (MDT) 2008 do support creating file-based Windows XP images, but these images are not componentized in a way that allows IT pros to inject drivers, updates, and other packages offline. This usually means that Windows XP images require frequent updates.


Windows Vista is distributed using the new file-based image format, Windows Imaging Format (WIM). This file format supports multiple images in a single, highly compressed file. A key benefit of WIM with Windows Vista is that it helps enable hardware independence because it’s a file-based image format. Hardware independence helps significantly reduce the number of images that corporate customers must maintain and deploy. The WIM file format also enables IT pros to service images offline, adding optional components such as device drivers and updates without having to continually recapture or create a new image. This capability dramatically improves maintenance and reduces costs.


  1. Windows Vista is distributed as a WIM image file and is installed by using IBS, resulting in a quicker and more streamlined installation process that requires fewer operating system images.
  2.  Windows XP is not distributed as a WIM image, nor does it use IBS. Microsoft tools support the creation of WIM images of Windows XP but don’t offer the offline-servicing benefits of Windows Vista images.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Deployment, compatibility, and asset-inventory tools


The Windows XP Corporate Deployment Tools ( ship on the Windows XP media and are available from the Microsoft Download Center. These tools include Setup Manager, the System Preparation Tool (Sysprep), and the

Microsoft Windows Corporate Deployment Tools User’s Guide. Also, MDT 2008 and the Microsoft System Center products support imaging and deployment of Windows XP. Customers can use many of the Windows Vista deployment tools, including those in the Windows AIK, to deploy Windows XP. For example, customers can use Windows Preinstallation Environment (Windows PE) 2.1, ImageX, Windows Deployment Services, Microsoft Deployment, and the Application Compatibility Toolkit (ACT) 5.0 to deploy Windows XP. However, not all Windows Vista capabilities are available when using these tools with Windows XP.

Windows Vista provides a new set of deployment tools. Some of these tools, such as Sysprep, now ship as core parts of the operating system. The remaining tools are in the Windows AIK and include Windows PE 2.1, Windows System Image Manager (Windows SIM), and ImageX. These tools are optimized so that business customers can reduce the number of images they maintain and so that servicing those images is easier. And MDT 2008—the next version of Microsoft Business Desktop Deployment (BDD)—takes full advantage of Windows Vista’s deployment improvements while integrating and extending the capabilities of the Windows AIK tools. Still other tools are available to streamline the Windows Vista deployment process:

  1.  Windows Deployment Services
  2.  ACT
  3.  Microsoft Assessment and Planning Solution Accelerator


  1. Windows Vista imaging and installation tools support WIM and take full advantage of WIM benefits, enabling a more consistent, reliable experience across different deployment scenarios. Additionally, with Windows PE 2.1, administrators can co-manage Windows Vista and Windows XP in a unified way, allowing for better management of heterogeneous environments.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Windows Setup


In Windows XP, Windows Setup installs and configures components on the destination computer. The process does not use IBS and does not support all the scenarios that organizations use to deploy the Windows operating system, such as scenarios that require non-destructive installation (e.g., Computer Refresh or In-place Wipe and Load scenarios, in which user files and settings remain local on the computer). Windows XP uses multiple answer files, each with different formats and syntax, for various installation phases. For example, Windows XP uses unattend.txt for installation from the distribution media and uses sysprep.inf for image installation. Using multiple answer files that contain similar settings leads to more difficult maintenance. Setup Manager, the tool that creates and edits unattend.txt files, does not support all the settings available and does not validate the contents of those files. Other than editing unattend.txt, Setup Manager provides only basic capabilities to create and manage distribution shares.


Windows Vista uses IBS, providing a more consistent and streamlined installation. It supports all the deployment scenarios that most companies use when deploying the Windows operating system, including those that require non-destructive installation. Windows Vista installation can be faster than Windows XP installation because Windows Vista uses IBS. Windows Setup uses an XML-based answer file (unattend.xml) for all configuration passes. This drives consistency across all passes. Also, Windows Vista supports more settings in unattend.xml than Windows XP supported in unattend.txt, so deploying the correct configuration requires nothing more than a properly configured answer file. Windows SIM is the tool that creates and edits unattend.xml files and distribution shares in a simple graphical user interface (GUI). Windows SIM supports all the settings that each Windows component exposes during deployment and helps to create and manage distribution shares.


  1. Windows Vista uses IBS and supports more deployment scenarios than Windows XP does.
  2.  Windows Vista uses a single XML-based answer file, providing a more consistent installation; Windows XP uses multiple text-based answer files.
  3.  Windows SIM supports all the settings that Windows Vista exposes for deployment for all configuration passes, while Setup Manager supports only a subset of Windows XP settings.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Worldwide single-image deployment


Windows XP provided nominal help for reducing the number of images that organizations maintain. For example, Sysprep prepares images to support computers with a variety of mass-storage devices. However, organizations must prepare one image for each type of hardware abstraction layer (HAL) in the production environment. Additionally, organizations must prepare an individual image for each language. MDT 2008 helps organizations using Windows XP get closer to thin-image strategies. Guidance and tools are provided to reduce image count, but the limitations of HAL- and language-dependence remain.


Windows Vista includes advanced features and capabilities that help organizations reduce the number of images they maintain. First, Windows Vista is hardware agnostic. Therefore, organizations don’t need to create images for each type of HAL in the production environment. Second, Windows Vista Enterprise and Windows Vista Ultimate enable organizations to deploy a single image that contains multiple Microsoft user interface languages, enabling worldwide deployment to all client computers by using a single image. MDT 2008 enables organizations to use thin-imaging and deploy-time customization techniques to deploy and customize a single worldwide image. For example, during deployment, organizations can target virtual private network (VPN) software to portable computers and accounting software to the Accounting department.


  1. Windows Vista enables organizations to create and deploy a single worldwide image, whereas Windows XP often requires numerous images for a worldwide deployment.
  2.  MDT 2008 enables companies to use thin-imaging techniques to reduce both Windows XP and Windows Vista image counts.




Windows Feature Comparison






Windows XP with SP3


Windows Vista with SP1


Key differences


Windows Mobility Center


Windows XP does not provide a central location for managing common mobility settings. Instead, users must open various programs and Control Panel items to manage mobility settings.


Windows Mobility Center, which original equipment manufacturers (OEMs) can customize, puts the most frequently used portable-computer settings in a single location. Now, users can change and synchronize display brightness, volume, power plan, wireless network, desktop wallpaper, external display (such as a network projector or additional monitor), all from one location. Presentation Mode allows users to quickly turn off the screen saver, turn off system notifications, and prevent the portable computer from going to sleep. This feature enables users to prepare quickly for giving presentations. Users can customize additional presentation settings, such as the desktop background and volume level. When using a Tablet PC, users can rotate their displays. No more hunting through Control Panel or notification area icons to find what you need. All the important mobile settings are in Windows Mobility Center. Windows Mobility Center is available only on portable computers.


  1. Windows Vista provides one location for managing common mobility settings, whereas Windows XP requires users to open various Control Panel items to change these settings.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Sync Center


Windows XP provides the ability to synchronize offline files or mobile devices, but the operating system does not provide a central location for managing all sync relationships. Users must use different programs to synchronize different devices.


Windows Vista gives users one place—the new Sync Center—to manage data synchronization between computers, between computers and servers, and between computers and devices. This capability has become increasingly important as the range of computers, devices, locations, and data sources that customers want to synchronize has expanded. Until now, there has been no easy way to manage all these individual sync relationships, so users have had to deal with many different sync experiences, depending on their devices or data sources.


  1. Windows Vista provides a single location for managing sync relationships, whereas Windows XP users must rely on different programs for different devices.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Offline files


Offline files and folders allow users to create a sync relationship between their computers and a remote location. The sync infrastructure and user interface (UI) track changes between the local version and the remote version and enable users to reconcile versions if conflicts exist. Users can specify which network-based files and folders they would like to use when working offline. In addition, offline folders can be encrypted to provide a higher level of security. The entire file is synchronized, even if a user made only a few changes. This can make synchronization a time-consuming process, especially when users have many documents to sync.


Windows Vista improves offline files and folders. First, it makes the sync process for offline folders much faster, with support for Delta Sync. Delta Sync synchronizes only the changed blocks of a file, rather than the whole file, when users synchronize client changes to the server. The advanced sync algorithm in Windows Vista is also better at determining which files or directories need to be synchronized, adding even more efficiency. This efficiency enables the synchronization of additional larger files, such as Microsoft Office Outlook® .pst and .ost files. Second, Windows Vista supports

ghosting of online files and folders. When users make only a few files from a directory available offline, Windows Vista creates ghosted entries of the remaining items to preserve the online context for users. When users are not connected to the remote data source and navigate to the remote location, they see these ghosted online items alongside the offline files. Third, Windows Vista makes managing offline files and folders easier. Users manage sync relationships by using the Sync Center. Users can see the offline status of any file or folder in Windows Explorer. And the transition between online and offline is now completely transparent and seamless.

  1. Synchronizing changes in offline files and folders is much faster in Windows Vista than in Windows XP because Delta Sync synchronizes only changed files blocks instead of the entire file.
  2.  Windows Vista supports ghosting, which provides a context for offline files and folders.
  3.  Windows Vista provides an improved UI for using and managing offline files and folders.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Network Projection




Windows Vista makes it easy to give a presentation from a portable computer. By using the Connect to a Network Projector Wizard, users can connect to any Windows-compatible network projector over a wireless or wired network. A network projector is a shared resource much like a printer on a network. Users can also use this feature in Windows Meeting Space, enabling them to stream content to a Windows Meeting Space session.


  1. Windows Vista makes it easier to give presentations from users’ computers.

Secure Sockets Tunnel Protocol (SSTP)


Windows XP supports Point-to-Point Tunneling Protocol (PPTP) and Layer-2 Tunneling Protocol (L2TP) VPN connections. In both cases, users often cannot connect successfully through some network configurations, such as those in public locations.


SSTP is a new tunneling protocol that uses Hypertext Transfer Protocol (HTTP) encapsulation over a Secure Sockets Layer (SSL) channel. Because SSTP uses SSL traffic (TCP port 443), SSTP can be used in many different network configurations—for example, when VPN clients or servers are behind network address translation (NAT) devices, firewalls, or proxy servers. SSTP requires Windows Server 2008 and Windows Vista with SP1.


  1. By supporting SSTP, Windows Vista enables users to create VPN connections in locations where they can’t connect when using Windows XP.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Power management


Windows XP made great strides in improving power management. However, data about remaining battery power was not always accurate. Also, standard users were not able to change power settings.


By intelligently monitoring CPU state, Windows Vista can reduce the amount of power it uses. Windows Vista also provides more accurate data about the amount of power a computer has left, helping prevent a system from shutting down prematurely. Also, the operating system allows standard users to change power settings. In addition, Windows Vista enables organizations to use Group Policy to manage power settings.


  1. Windows Vista reduces power consumption.
  2.  Windows Vista provides more accurate reports about remaining power.
  3.  Windows Vista enables standard users to change power settings.
  4.  Windows Vista enables Group Policy management of power settings.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


Wireless networking


Windows XP provides support for the most recent wireless networking standards and security. It also includes device drivers from most popular wireless network adapters in the box.


Windows Vista improves the wireless network experience in several ways. Users’ data is also more secure because of enhanced support for the most recent wireless security protocols, including Wi-Fi Protected Access 2 (WPA2). Windows Vista helps users avoid connections to fraudulent wireless networks that seem to be legitimate hotspots but are not. Windows Vista also provides an easy way to create ad hoc wireless networks to use peer-to-peer applications such as file sharing and application collaboration. Windows Vista introduces other networking innovations. The new networking stack can auto-tune key performance settings, such as the TCP receive window. It also adds support for a dual IP layer architecture that supports both TCP/IP version 4 (IPv4) and version 6 (IPv6). Windows Vista provides new ways to manage wireless networking by using Group Policy and command-line configuration tools. Wireless networking is now standard across hardware vendors.


  1. In Windows Vista, Network Awareness automatically chooses the best network connection to use when multiple connections are available to applications.
  2.  Windows Vista helps protect users from connection to malicious wireless networks that masquerade as public wireless networks.
  3.  Windows Vista has a new networking stack that supports auto-tuning and a dual IP (IPv4 and IPv6) layer architecture.
  4.  Windows Vista has an improved UI for creating and managing wireless network connections.




Windows Feature Comparison






Windows XP with SP3


Windows Vista with SP1


Key differences




Windows XP provides a basic, indexed search feature that can help users find files by name or content.


Windows Vista introduces enhanced desktop search and organization that helps users locate files and emails on their computers. If users remember anything about a file, Windows Vista can instantly find it. Users can add and change metadata for files, and then use that metadata to find and organize files regardless of location. (Different file types have different metadata, but examples include the title and author for a document.) Users can edit metadata in the Common File dialog box, Details Pane of Windows Explorer, Windows Media® Player 11, Windows Photo Gallery, and so on. Additionally, Windows Vista allows users to save search queries as Search Folders. Opening a Search Folder displays the files that match the search query. For example, users can create a Search Folder that finds files created within a certain date range, containing a specific keyword, or authored by a particular person. Search is extensible. For example, Windows Vista allows third-party content and file types to be included in the system index so that they can also be searched.


  1. In Windows Vista, Search integrates completely into the user interface. For example, users can search their computers instantly from the Start menu.
  2.  In Windows Vista, users can tag files with metadata, and then use that metadata to quickly find files on their computers.
  3.  In Windows Vista, users can save a search as a Search Folder, and then quickly repeat that query by opening the Search Folder.



Windows Feature Comparison





Windows XP with SP3


Windows Vista with SP1


Key differences


User interface and navigation




Microsoft designed Windows Vista to provide easier access to the applications and information users want. From the Start Menu to the files in Explorers, users can more easily access what they need and complete tasks more directly. User interface improvements include the following:

  1. Start Menu. Streamlined to make browsing (looking for a specific application, file, email, Control Panel item, or Internet favorite) easier.
  2. Explorers. A streamlined and consistent set of tools for finding, viewing, and managing information and resources.
  3. Dialog boxes and wizards. Redesigned to be clearer and more functional, and easier for developers to customize to optimize the user experience.
  4. Programs Explorer and Control Panel. Programs Explorer (which replaces the Add or Remove Programs control) and Control Panel use the Explorer interface to help users more easily and quickly manage applications and settings.

    Within Explorers, Windows provides numerous user interface and navigation improvements. For example, the Command Bar is a new bar that displays contextual, one-click tasks based on the content displayed. The Details Pane enables users to view and change metadata on one or more files without having to open the Properties dialog box. Live Icons show the actual first page of a document and the actual photo, video screen capture, or album art for individual songs (rather than generic icons).


  1. Windows Vista improves significant parts of the UI, such as the Start Menu, Explorers, dialog boxes and wizards, and the Control Panel.
  2.  Windows Vista improves Explorer user interface and navigation with features such as the Command Bar, Details Pane, Live Icons, and an improved address bar.





  2. Windows Feature Comparison




    This white paper compares the capabilities of key features in Windows XP with SP3 and Windows Vista with SP1 to help organizations as they are evaluating Windows Vista and planning deployment in their company. For more information about Windows Vista, see the following resources:

Windows Vista TechCenter at

  • Springboard Series: The On-Ramp for IT Pros at
  • Windows Vista Product Overview for IT Professionals at
  • Windows Vista: Common Deployment Questions Answered at
  • What's New in Group Policy in Windows Vista at
  • TechNet Virtual Labs: Windows Vista at
  • Microsoft Desktop Optimization Pack for Software Assurance at

  • Reference :

    How To Create a 404 Error Handler For Your .NET Application

    Use of 404 Error Handlers

    I've always liked custom 404 error handlers. I've never liked to give a user a 404 - Page Not Found Error. One of my very earliest websites included a 404 handler that tried to intelligently redirect the user to something related to the wrong URL they'd tried to jump to.

    The best 404 error handlers are probably dynamic scripts that try to supply context sensitive information to the user. But handling mistyped urls is only one use of a 404 error handler.

    Another improtant use for error 404 handlers is to put friendly urls on top of script generated output. Until recently, some search engines were unable to spider script type urls with parameters. When an error404 handler is used to return web pages for normal URLs, this can make content more easily digested by various web spiders.

    Many wikis have URLs that look like this:

    By having the wiki program respond as a 404 handler, it is possible to use much simplier URLs such as

    Setting Up The 404 Error Handler

    • Configuring Error 404 Handler For Apache

    It is easy to configure an Apache webserver to use a 404 error handler. It can be done as simply as including a single line in an .htaccess in an http file directory, such as the root directory of a virtual web host:

    ErrorDocument?Create 404 /cgi-bin/

    • Configuring Error 404 Handler For IIS

    On Microsoft IIS web servers, use the Internet Information Services (IIS6) Manager to configure a 404 handler for any directory, virtual root, or entire website.

    Right click on any folder, select Properties. Select the Custom Errors tab. From the list of errors, select HTTP Error 404. Then click on "Edit...". Select message type of URL, then enter path and file of the error 404 handler. With .NET, your error handler page might be named Error404.aspx, so you might enter /Error404?Create.aspx for the file in the root directory. If you are setting up the 404 error handler just for your own application subdirectory, you might enter /YourApp?Create/Error404?Create.aspx

    Programming The Error 404 Handler

    One of the first things you will want to do is write a small program to show you all the server variables that are available to you from within the error handler script.

    Here is some sample C Sharp (C#) to return a string containing all the server variables. Put this code in your Error404.aspx.cs file:

    protected string GetServerVars()
             string S="";
             int i=1;
            System.Collections.IEnumerator myEnumerator = Request.ServerVariables.AllKeys.GetEnumerator();
      while (( myEnumerator.MoveNext() ) && ( myEnumerator.Current != null ))
                         S=S+String.Format( "[{0}] {1}={2}<br>\n", i++, myEnumerator.Current, Request.ServerVariables[myEnumerator.Current.ToString()] );
                        return S;

    It's very simple to put this into your page. Put the following line into your Error404.aspx page:

    <% =GetServerVars() %>

    The most interesting variable will be the QUERY_STRING variable:

    [32] QUERY_STRING=404;http://localhost/Hive/HomePage.htm

    It is easy to pick this apart, and create a new URI object to use with the URL that generated the 404 error:

    string S=Request.ServerVariables["QUERY_STRING"];
    S=S.Split(new Char[] {';', ' '}, 2)[1];
    Uri QUri=new Uri(S);

    Other related issues:

    • How to setup a 404 handler that works with the development server that comes with Visual Studio 2005. Because projects under that environment usualy include a path, it is sometimes difficult to deal with applications that depend on 404 handling, since there isn't a console for the development server to set a 404 handler. Whereas an application might see the URL /home in its 404 handling routines, when debugged from the development server, it may see something like http://localhost:9384/AppName/home
      • Google search - "ASP development server" 404 handler - No results
      • Google search - " development server" 404 handler
    Reference :

    26 Tricks to Help You Tame Google Calendar

    Google's free online calendar makes it easy track your schedule from anywhere, but many of its best features lurk beneath the surface. Here's how to handle Gcal like a pro.

    Desktop calendar applications are great if you're always at your desk or if you're diligent about syncing with your PDA or phone. But if you like to travel light, it may be time for you to switch to a calendar that you can access from any Internet terminal. Google's free Google Calendar is one of the most robust online calendars available. And I have the goods on how to get the most from Gcal's advanced features.

    Getting started with Google Calendar is easy. If you already have a Google account (for Gmail, say), you don't even need to sign up. Just click Calendar at the top of the Gmail screen, or surf to and log in. If you don't have an account yet, click Sign up for Gmail on the home page, enter your name, create a log-in name, and choose a password and security question.

    Choose Your Views

    Agenda view: Once you're logged into Google Calendar, you can quickly switch between day, week, month, and other views by clicking the tabs along the top of the calendar. The Agenda view conveniently displays your appointments in chronological order, starting with the present date, without the screen clutter of a day, week, or month view.

    Custom view: The tab marked 'Next 4 Days' may seem arbitrary, but it's a gem of a feature. You can customize the tab to display your preferred time period, from two days to four weeks. Click Settings in the upper right corner of the screen (or press s), and then scroll down to 'Custom view' on the General tab. Choose an option from the drop-down list and click Save.

    Quick customization; click for enlarged image.

    Quick selection: A cool way to display a relevant stretch of days is to click and swipe over the minicalendar on the left, selecting just the days you want; the main display reflects your selection.

    Hotkey navigation: It's easy to use the keyboard to navigate through your calendar. Just press d, w, m, x, or a to jump to day, week, month, custom, or agenda views, respectively. Press n (for "next") or p (for "previous") to go forward or backward, respectively. (Or press the j and k keys to accomplish the same things.) Press t to jump to today's date.

    Make Dates With Destiny

    Quick additions: Google Calendar provides a couple of easy ways to add items: One way is to click Quick Add in the upper left area of the calendar page (or press q) and start typing. Like a real person, Google Calendar assumes that words such as "Monday" and "Wednesday" refer to days of the current week; and in keeping with this understanding it adds the item to the appropriate day.

    Click and go: A second approach is to click a day or time (depending on your view) in the main calendar and to start typing in the box that opens. Google Calendar recognizes most expressions of time (7:00 PM, 7p, and so on), and it schedules the associated calendar events accordingly.

    Drag and drop: Need to reschedule? You can easily change dates and times by dragging and dropping an appointment. If a whole month is visible, dragging changes only the day. But if a day or week schedule is displayed, you can drop on any time to change the time, too.

    Easy edit and delete; click for enlarged image.

    View and edit: Double-click any event to see all of its associated details. You can change some details on this page; but for major modifications, you must click the event and choose edit event details.

    Easy erase: Need to cancel an event? Click an item once and click Delete to zap it. Then click Delete (or press the spacebar) to confirm the deletion.


    Share and Share Alike

    By default, only you can see events on your calendar. But you can make entire calendars--or just individual events--public if you like.

    To change the default setting, click Settings in the upper right (or press s). Click the Calendars tab. Click the link under Sharing to open the appropriate calendar. Then use the checkboxes to instruct Google Calendar whether to share everything with the whole world or just a subset thereof. To share with specific people only, leave those checkboxes empty and use the controls underneath to add the names of the privileged few. Then click Save.

    Seeing Multiple

    You may need different calendars for different purposes--work life and social life, for example. To accommodate such divisions, click Add below the minicalendar on the left. Having multiple calendars lets you establishcustom privacy, sharing, and other settings for each one.

    Living color: You can give the text of each of your calendars a custom color (use the pop-up menu to the right of the calendar name), or you can use the checkbox to the left of the name to show or hide events on that calendar. This color-coding makes all of the entries for a given calendar easy to identify at a glance.

    Choose a calendar: When you have multiple calendars, Google Calendar adds a drop-down list to the New Event popup balloon so you can specify which calendar should display the new event. The Quick Add box is less flexible, however. If you use Quick Add (press q) to create an item, the program will add your event to your first (uppermost) or main calendar, even if you've hidden its events.

    Switch calendars: To move an event from one calendar to another, click the event and then click edit event details. Choose another calendar from the Calendar drop-down list, and click Save.

    Public calendars: You can make your calendar automatically display holidays, sports events, television shows, or other items of special interest to you. Just click Add above your calendar list, and choose Add a public calendar. In the 'Add a Public Calendar' page, select a category on the left, and then click Add to Calendar for each calendar you want to add. You have hundreds of options to choose from, ranging from schedules for your favorite sports teams to concert tour dates to campaign stops for political candidates.

    Add iCal calendars: Want to integrate a Web-based calendar set up in the iCalendar format that Apple's iCal and Microsoft's Windows Calendar use? Just choose Add by URL from the Add menu, and type the desired Web address.

    Change your mind? To hide or delete any calendar from your list, click Settings on the upper right (or press s) and click the Calendars tab. Then click Hide or click the trash can icon to the far right of the calendar that you want to suppress or zap, respectively

    Events and Invites

    A young friend of mine recently referred to as "old school." With the latest tools for sending invitations built into sites like Facebook and Google Calendar, he may be right. To invite people to an event in your calendar, simply type their e-mail addresses into the Guest box provided on the event details page. Click Save, and Google Calendar will offer to send them an invitation.

    If a recipient uses a Gmail account, the event will appear in the invitee's calendar (as well as in the invitee's e-mail Inbox) with a question mark icon. The recipient can click the event and choose Yes, No, Maybe, or Delete directly in the calendar. Invitees can also use the 'Add a comment' feature under 'Discuss this event' to leave notes for the group to read.

    RSVP notifications: To receive notifications about invitations and replies, click the arrow next to the calendar name, and choose Notifications from the pop-up menu. (Or click Manage calendars under the list of calendars, and then click the Notifications link on the right for the desired calendar.) Use the controls at the bottom of this page to specify whether you wish to be notified by e-mail or by SMS. (For more about SMS messages, see "Going Mobile," below.) Naturally these settings affect only how you are notified, not how your guests are. They'll have to set up their preferences on their own calendars.

    Snooze alerts: At posting time for this article, Google had just added a new feature to Google Talk Labs Edition. If you use Google Talk, the new feature sends Calendar notifications to your desktop and lets you snooze reminders with a single click. This Windows-only utility makes handling notifications in Gcal far more convenient.

    Take It Outside

    Maybe you need your calendar information to appear somewhere other than in Google Calendar. Google Calendar permits you to print, save, and embed your calendar in other Web sites. The print icon (next to the Day, Week, and Month tabs) lets you print your current view or export it as an Acrobat PDF, whether you have Acrobat installed on your system or not.

    If your calendar is designated as public (see "Share and Share Alike"), you can embed it in another Web site or blog. Click the arrow to the right of your calendar name and choose Calendar settings. Scroll down the page that appears and copy the code next to Embed This Calendar to publish the information on a Web site. Click the button for the appropriate format (XML, iCal, or HTML) to obtain the address of your calendar for that format so you can provide calendar access to feed readers and other software.

    If you want to be able to check your calendar without logging in, use the buttons in the Private Address section to get the URL for a read-only version of your calendar.

    Going Mobile

    If your existing calendar can't sync with your cell phone or other mobile device, you'll find Google Calendar especially handy. You can use your phone's text messaging feature to get reminders of upcoming appointments or to send new ones to Google Calendar. Though Google Calendar is free, having text messages sent to your phone may cost you, depending on your cell phone carrier's plan.

    To get these features, you must register your phone with Google Calendar. Click Settings or press s under Calendar Settings, and then click the Mobile Setup tab. Fill out the information for your country, phone number, and carrier. You can consult a full list by clicking What carriers are supported?; then click Send Verification Code. When you receive the code as a text message on your phone, make a note of that number and enter it in the Verification Code box. Click Finish Setup, and then click Save.

    Once you've registered your phone number with Google Calendar, you can use it for common calendar chores. For example, get information from your phone by sending a text message to 48368 (GVENT): Enter next to get the next scheduled item on your calendar, day (to get all the day's agenda, or nday to get tomorrow's agenda. If you send something more prosaic like "Get a haircut at Joe's on Tuesday at 11 am," Google calendar will create a new event for you just as it does when you use the Quick Add feature.

    Currently the SMS features work only in the United States, and you can arrange to get data only 24 hours in advance. In my tests, it worked only for the main (first) calendar though I had more than one calendar set up. You can use GVENT with phones on most U.S. mobile carriers--namely, Alltel, AT&T, Cellular One, Cincinnati Bell, Dobson Communications, Nextel, Qwest, Sprint, T-Mobile, U.S. Cellular, Verizon, and Virgin.

    Automatic alerts; click for enlarged image.

    Automatic alerts: To receive notifications automatically via text messaging, click the arrow next to the calendar name, and choose Notifications. Next to 'Event reminders', click Add a reminder to set the default method (pop-up, e-mail, or SMS) and the time to receive reminders. If you want multiple reminders (for example, a day before, an hour before, and 10 minutes before an event) or reminders of multiple kinds, click Add another reminder as many times as necessary to specify all of them. Change your mind? Click Remove next to the reminder you don't want.

    All done? Click Save. Repeat for each calendar in your list on the left that you need reminders and notifications for.

    Naturally, you can return to this dialog box to cancel or alter your notifications if your current settings aren't working for you. Alternatively you can send the text message "STOP" to 48368 (GVENT) to stop all notifications for all calendars.

    Keep It All in Sync

    Google Calendar can import data from other calendars in the iCal or CSV (comma-separated values) formats. This comes in handy if you plan on migrating your schedule to Google once and forever. But for people who want to use both Google and Outlook, Google makes a utility that keeps data from both sources in sync with each other.

    Import from iCal or Yahoo: To import data from a calendar, you must first export it to a file. For example, in Apple iCal, select the calendar you want to export and choose File, Export. Then name and save the file. In Yahoo Calendar, click Options on the upper right and then click Import/Export under Management. Click the Export button under 'Export to Outlook'. Save the file to a desired location.

    Import from Outlook: Outlook users have more than one option. If you have a single calendar in Outlook, it's probably easier to import the data using Google's syncing utility (see "Google Calendar Sync," below). But if you have multiple calendars in Outlook, you're better off exporting them to a separate file one at a time. To do that in Outlook, choose File, Import and Export and select Export to a file. Click Next and select Comma Separated Values (Windows). Click Next, select a calendar, and click Next again. Continue to follow the steps in the wizard. When you're prompted for a date range, Google recommends that you specify no more than one year's worth of data. You may need to repeat the export process for each year that you want to export, importing them into Google Calendar one at a time.

    Once your data is saved as a file, go to Google Calendar, click Add below the minicalendar on the left, and choose Import Calendar. In the Import Calendar tab, click Browse to locate and select your calendar file. Then use the drop-down list to specify which calendar should receive the data. Then click Import.

    Google Calendar Sync; click for enlarged image.

    Google Calendar Sync: Outlook users who want to use Google's syncing utility can download it from this link. Once you have saved and finished downloading the file, run the installer. As part of the installation, the program will instruct you to identify your Google account and password, specify which direction (or both) you want to synchronize info in, and state how often the utility should perform that task. The utility runs in the background while you work; you can change the options at any time by right-clicking the Google Calendar Sync icon in the taskbar tray and choosing Options.

    Google Calendar Sync is an easy, painless way to make sure that your Outlook and Google calendars always have the same information. But the tool can synchronize only your default Outlook calendar and your main (first) Google calendar. For many people, that's enough.

    Reference :,145844-page,1-c,webservices/article.html

    نویسنده : Nasser Hajloo : ۱۱:٠٦ ‎ق.ظ ; ۱۳۸٧/۳/۱
    Comments پيام هاي ديگران ()      لینک دائم