The author writes "One of the things that keeps coming up as a benefit of switching to ASP.NET is the ability to use code-behind to separate display code from application logic. In Visual Studio.NET, this is 'automagically' done for you. So what if you don't have VS.NET? Here's how you can implement code-behind using just a plain old text editor and the tools included in the .NET Framework... no VS.NET required!" Source codes available for download.
This article explains what are "Delegates"? And what is their role in .NET framework. The author uses VB.NET code to provide working examples of "Delegates".
What exactly is XSLT useful for and why would you, as an ASP.NET developer, want to learn about it? The answer boils down to the capability of XSLT to transform XML documents into different formats that can be consumed by a variety of devices, including browsers, Personal Digital Assistants (PDAs), Web-enabled phones, and other devices that will appear in the near future.
This article examines how to can create a Web service in .NET and then utilize it from a classic ASP page on your Web server, thereby providing an API that can be utilized by both your ASP.NET Web pages and classic ASP pages.
The ASP.NET 2.0 Wizard control simplifies many of the tasks associated with building a web application. In this tutorial we will look at the basics of the Wizard Control by creating a simple data collection form and then advance to simulate an online test wizard that will be generated dynamically.
The term "web service" has been used quite frequently lately: you hear people saying how good web services are and how they will dominate the future of software development, but what exactly are web services and how can we create them? This article shows us how to build two web services and also unravels all of the lingo surrounding web services.
Ideally, every application built would be designed with correct date handling techniques. In practice, applications are often built using ad hoc date formatting to match a corporate culture, the default format on a company’s server, or the favorite format of the lead developer. Also, many applications are not locale aware or were not designed to be deployed in an environment where locale issues were not considered important. Because of this it is extremely important to know the date formats in use for input and output when building applications that will integrate with other systems or databases and to handle these formats explicitly.
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.