While ASP.NET 2.0 is completely backwards compatible with ASP.NET 1.1, its new features may require you to revise parts of your Web applications. This article provides a detailed analysis of how changes in ASP.NET 2.0 will influence your porting decisions.

This discussion will focus around "How to write secure code?" using .NET Technologies. It will also discuss secure coding practices for enterprises and organizations. The discussion will include following topics: .NET Security Fundamentals; Code Access Security; Impersonation, Authentication and Authorization; Security in COM+ and ASP.NET. Source code included.

The new security components in .NET 2.0 can help you greatly reduce the amount of code you need to write in order to make your applications secure. Security is difficult to get right, and it is a good strategy to leverage the code provided by Microsoft and other security vendors. To that end, .NET 2.0 provides numerous additional types that encapsulate functionality already provided in the base Windows OS., as well a new functionality only available in .NET 2.0. The improvements affect public key cryptography, Windows security, remoting, ASP.NET and Code Access Security. Even if you plan to stick with .NET 1.1 for a while and implement your own security classes, you might want to take inspiration from.NET 2.0 beta.

Microsoft provides an easy way to dynamically register client side code at runtime. Unfortunately, it can only place the code within the body of a web page. I have two suggestions on how to work around this issue and register code in the header.

Watch Thomas Lewis, Technical Evangelist for ASP.NET 2.0, give you his top-of-mind perspective on salient features of ASP.NET 2.0 in this 10 minute video.

As more and more companies reach out to other countries for business, creating global Web applications with Microsoft ASP.NET is becoming more and more important. ASP.NET 1.1 supported creating localized Web sites by means of the ResourceManager class. ASP.NET 2.0 makes it even easier to provide support for multiple cultures and locales through improved runtime and tool support.

E-Commerce applications require mechanisms for payment. Although more commonly than not e-Commerce sites will use full credit card processing gateways, giving PayPal as an additional option of payment provides additional payment options for your customers, especially those that don't want to pay by credit card over the Internet. If you run a Web shop that uses direct credit card processing and want to integrate PayPal seamlessly, you'll find that using PayPal as a processing service is not as straight forward as using a payment gateway. In this article I describe how you can minimize the external PayPal interaction and work the PayPal payment into the order processing workflow to provide a seamless interface using ASP.NET and C#. However, the principles used here should be applicable to any Web programming environment.

Create stored procedures with Output parameters and return values and use them in .NET

Learn how to create and execute stored procedures using .NET.

Thom Robbins, from Microsoft New England, provides a quick overview of all the data source controls: SqlDataSource, AccessDataSource, XmlDataSource, ObjectDataSource, and SiteMapDataSource as well as the declarative caching properties you can use with the controls.