Signin
.NET Blues

Wildgrape NewsDesk is a .NET-based RSS viewer.  There is not much there that I haven't seen before in an RSS viewer, except clean (less feature means less clutter) and somewhat crispy (tender loving care of layout) GUI with no-nonsense functionality.  What caught my attention is its use of .NET 1.1 beta framework.  Geesh.  I thought I was taking a big risk by using .NET 1.0!

More I use .NET, more problems I find.  Interoperating with Win32 is a chore, having to manually import Win32 API one function at a time, an error prone process.  There are odd bugs too like RegistryKey.SetValue method's confusion over UInt32.  What bothers me the most is the lack of aggressive plan to increase .NET installbase.  20 megabytes is not something users will casually download unless its porn.  Only solution I see around this problem is to bundle .NET Framework 1.1 with IE 7.  Will Microsoft do this?  I doubt it.

I don't think .NET will be ubiquitous on desktops until .NET 3.0 is released two year from now.  Until then, .NET makes sense only for server-side software.  So the situation is a mixed revisit to Windows 3.1 and Java.

Comments
I agree with you on .NET 3.0. There are way too many bugs in .NET 1.0/1.1. Every day I discover some new bug. Every moment when I make a step into anything a bit trickier that "Hello World" stuff - Bang!

I agree that UI is king, but .NET 1.x has less than sufficient set of UI controls and they are childish at best. While I could use or build something like Magic UI Library and Docking controls, but I suspect Microsoft will start making their own UI improvements starting with .NET 2.0 and leave my custom improvements stranded.
PropertyGrid is really cool. I love it.
Wildgrape NewsDesk 0.6.1 now runs on .NET 1.0 thanks to a few bindingRedirects in an application configuration file. I was a little surprised that it worked with no other changes. Now you step back from the bleeding edge to the cutting edge.

Comment has been disabled for this post.