Things have been really hectic over the past few weeks but at least I've got time to breathe again. We presented our beta version of the Radio Station System project on Friday which went fairly well. Apart from one problem with reporting all went smoothly and everybody seemed impressed. It never ends though - so now I'm trying to implement dynamically changeable look and feels for the portal component of the system.

That brings me to my biggest problem with C# - Exception handling. Coming from a Java background, I've got so used to the compiler reminding me when I've forgotten to handle an exception somewhere. Now, don't get me wrong - I don't rely solely on the compiler to tell me when I've made a mistake, but it helps in some cases. Being fairly new to C#, there is no way that I know all the exceptions and where they could arise. So, inevitably I miss quite a few and the application (usually at the most inopportune time) bombs out as you're trying to show off some functionality that's taken months to build. Instead of getting some oohs, and aahs, you've got a red face and try to mumble something about the Memory....

From what I've seen, the developers at Microsoft seemed to try to make things as easy as possible with the good tools provided, frameworks, API's etc, whereas Java seems a little "lower-level". I'm sure that the guys had some reason not to build C# with forced exception handling but I can't seem to find it. It just seems contradictory to the assistance everywhere else?

|

0 comments


Twitter Delicious Facebook Digg Stumbleupon Favorites More

    Subscribe