Welcome to NED.net User Group

When Microsoft released the .NET Framework 1.0 Technology in July 2000, it was immediately clear that Web development was going to change. The company’s prior technology, Active Server Pages (ASP) launched hundreds of books, articles, Web sites and components, all aiming to make the development process easier than before. However, what ASP did not have, was an application framework - it was never an enterprise development tool. Everything in ASP was code oriented - but it simply wasn't possible to avoid doing work without writing codes.
ASP.NET was designed to counter this problem. Right from its initial release as a preview technology, Microsoft ASP.NET has been a huge success. For those people developing web sites using Microsoft technologies, ASP.NET provides a rich programming model, allowing sites to be easily constructed. There has been a lot of talk since its release, but ignoring all the hype and press, .NET really is a product for developers, providing a great foundation for building all types of web applications. One of the key design goals of ASP.NET was to make programming easier and quicker by reducing the amount of code that needed to be created. This phenomenon operates when one enters the era of declarative programming model, rich server controls, large class libraries, and support for development tools from the humble Notepad to the high-end Visual Studio .NET.

Yup thats an excerpt from my latest contribution for Spider Magazine. See their September 2005 issue, page 47 if you want to read more. Visual Studio Team System, SQL Server 2005 and Smart Clients are on the list for future publications for both Spider and Dawn Sci-Tech. Feel free to share your comments and suggestions.

Today there is a greater focus than ever on reusing existing components and wiring together disparate components to form a cohesive architecture. But this wiring can quickly become a daunting task because as application size and complexity increase, so do dependencies. One way to mitigate the proliferation of dependencies is by using Dependency Injection (DI), which allows you to inject objects into a class, rather than relying on the class to create the object itself.

Read the rest of this article and download the source code from here.