Download: Microsoft® Visual Studio® LightSwitch™ 2011 Trial

Microsoft® Visual Studio® LightSwitch™ 2011 gives you a simpler and faster way to create professional-quality business applications for the desktop, the web, and the cloud. Using application templates, Visual Studio LightSwitch 2011 saves the time and effort of building from scratch, without sacrificing the flexibility needed to create custom applications.

Microsoft Visual Studio LightSwitch 2011 is a flexible, business application development tool that aides developers of all skill levels to quickly create and deploy desktop and web business applications. With timesaving tools and templates, and an intuitive development environment, Visual Studio LightSwitch helps speed the development and reduces the complexity of everything from UI design to Windows Azure Cloud Deployment. Now with Visual Studio LightSwitch it is finally practical to build affordable, scalable custom software solutions that bridge the gaps between existing systems and provide comprehensive, user-friendly views of your business data. For more information on Visual Studio LightSwitch 2011 visit http://www.microsoft.com/lightswitch

Download Trail

How Application Pools Works ? (IIS 6.0)

What are Application pools? How it actually Works? The concept of Application Pools has from IIS 6.0. Application pools are used to separate sets of IIS worker processes that share the same configuration and application boundaries. Application pools used to isolate our web application for better security, reliability, and availability and performance and keep running with out impacting each other . The worker process serves as the process boundary that separates each application pool so that when one worker process or application is having an issue or recycles, other applications or worker processes are not affected. One Application Pool can have multiple worker process.

When you run IIS 6.0 in worker process isolation mode, you can separate different Web applications and Web sites into groups known as Application pools. An Application pool is a group of one or more URLs that are served by a worker process or set of worker processes. Any Web directory or virtual directory can be assigned to an application pool. Each application pool is given its own set of server resources. That way, if a Web site crashes, it won’t effect sites in other application pools.

A classic example of this is a Web site with a memory leak. If all of the Web sites hosted on a particular server were to share system resources, and one of the Web sites had a memory leak, it could potentially take memory away from the other hosted sites. If the leaky site were in its own application pool though, the memory leak would not effect any other site because each application pool has its own server resources (including memory).

Main idea behind application pools are
1. Isolation of Different Web Application
2. Individual worker process for different web application
3. More reliably web application
4. Better Performance

For more information check this URL from MSDN.

Hope this is useful

Authenticate a Windows account using Forms Authentication

I have found good article on authenticating a Windows account using Forms Authentication by Akhtar Shiekh. Go through this link for details.

10 Tips for Writing High-Performance Web Applications

10 Tips for Writing High-Performance Web Applications


Source: http://msdn.microsoft.com/msdnmag/issues/05/01/ASPNETPerformance/

10 Tips for Writing High-Performance Web Applications Rob Howard
--------------------------------------------------------------------------------
This article discusses: Common ASP.NET performance myths Useful performance tips and tricks for ASP.NET Suggestions for working with a database from ASP.NET Caching and background processing with ASP.NET This article uses the following technologies: ASP.NET, .NET Framework, IIS
--------------------------------------------------------------------------------
Contents Performance on the Data Tier
Tip 1—Return Multiple Resultsets
Tip 2—Paged Data Access
Tip 3—Connection Pooling
Tip 4—ASP.NET Cache API
Tip 5—Per-Request Caching
Tip 6—Background Processing
Tip 7—Page Output Caching and Proxy Servers
Tip 8—Run IIS 6.0 (If Only for Kernel Caching)
Tip 9—Use Gzip Compression
Tip 10—Server Control View State Conclusion Sidebars Common Performance Myths
--------------------------------------------------------------------------------