The release of ASP.NET forces us to reconsider many preconceptions about the deployment of websites. For example, we need to get used to the possibility of running multiple copies of the same site on a single server, sharing different versions of identically named DLLs. Another thing that developers might find incredible is XCopy deployment, which allows a developer to deploy an application by simply copying files to the target location. There's no need to use the Registry or any complex COM registration.
ASP.Net's introduction of the web.config file went a long way to filling the configuration hole we had to deal with in classic ASP. We actually went from having very little (global.asa was the closest thing) to a well-structured, change on the fly XML file. For the most part, the web.config file does the trick fine. However there are some limitations and constraints with using it, which you are probably already aware of. What you might not know is how easy is it to surmount those issues by creating a far more flexible alternative.
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.
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.
This article discusses the importance of security considerations when designing a server application. Both Microsoft Internet Information Services (IIS) and ASP.NET provide security models that will allow you to authenticate your users appropriately and obtain the correct security context within your application.
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.
Out of the box, ASP.NET is a very powerful platform for writing XML Web Services. But what happens when you need to format the XML to match an existing XML grammar? Not surprisingly, this can be accomplished using the XML Serialization Engine. In the first part of this two-part article, Justin Rudd shows you the basics of the engine as well as how the engine works with ASP.NET.
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.
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.