|
.NET Challenges on the Client Side |
|
|
|
Monday, 09 February 2004 |
Here's a challenge to every developer who would like to take advantage of .NET. You may lose ten times the time you save in development on supporting end users without .NET or without the exact right version of .NET. Joel summarizes the problem quite well.
This makes deploying .NET apps in a controled environment (such as internal company apps on company owned computer) tricky and supporting a consumer product written in .NET almost impossible.
Assuring the correct .NET runtime is installed seems less of a problem for server side applications (ASP.NET). At least you have control over the server(s). Then again, it might make .NET hosting on a shared server difficult (your app works on 1.0, mine works on 1.1). I recently completed a minor project using ASP.NET and I noticed another challenge that's a carry over from the Visual InterDev Design time control days: WebForms are brittle. Just as Joel noticed on the client side, when ASP.NET WebForms just don't run the error messages are not particularly helpful. The forms have all sorts of dependencies you aren't aware of. Edit the wrong line by hand, or delete that file that appears to be a useless temp file and your forms are hosed.
In theory, I thought .NET was probably Microsoft's most potent weapon to fend of Linux, but in practice I'm not so sure.
Powered by AkoComment 2.0! and SecurityImage 3.0.4 |
