Linked by Will Senn on Thu 22nd Apr 2004 06:30 UTC
This article is intended to give you a practical recipe for creating a simple Web Control and extending Visual Studio with support for the control. The control itself is a basic Country Code drop down list such as you would find on many profile entry pages.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
I get what you're saying in principle, but in practice - where are you calculating the 'cost'?
Developing in ASP.NET/C# actually don't have to cost a red cent (other than effort) - the SDK is free. Studio is expensive, yes, but it's not required to develop apps. Postgres works well enough with .NET, although MySQL offers a driver that will (in theory) outperform it using ADO.NET.
The Server is where I calculate most of the 'cost' and it's not radically expensive to host a website with IIS, these days.
On the twice as fast using other tools comment, that's been your experience I take it? VS.NET most definitely supports RAD and applications from simple mom and pop ecommerce sites to complex search, catalog and financial websites can be rapidly constructed using it. Experience is the best teacher... For example, Multi-tiered architectures are cool to read about and can entertain a group of Comp-Sci students, but are rarely required in the majority of 'real world' situations - at least to the degree that they are hyped. The concept is sound and should be strived for at times, but generally an interface, database, and logic are what's required to service a small-medium size website. How much separation there is, is a matter of no small consideration. However, unless you are developing an enterprise solution - less is more. The default codebehind separation of interface from logic is sufficient. The logic and data objects can be hand written by a proficient developer without introducing an additional hierarchy of classes, separated by more file boundaries. I guess what I'm saying is that I can write a Web Application in .NET that reads some data from a DB, joining a couple of tables, convert that to XML and send it to another process, tell the user what's going on and whatnot in a single pair of .aspx and .aspx.cs files, using a text editor and the command line compiler - not radically different from any web development platform...
I would agree that there's a lot more room for abuse on the cost front in .NET, but it doesn't have to be that way.
Later,
Will