I’ve updated my windows service helper so that it also can install your service for you (through the command line).
Throwing exceptions is in itself trivial. Just invoke
throw with an exception object. But when should you throw? Should you create a new exception or rethrow an old one? What should you include in the exception info?
This blog has been quiet for a while. I am currently writing a book about localization. Me and my partner is also getting close to release of our new startup. One of it’s features is to automatically catch unhandled exceptions and send them to a webservice for analytics. But to take full advantage of that you’ll have to use a set of exception handling best practices. I’m therefore going to write a set of exception articles. The series will end with the release of our service.
I just read that Mozilla are going to block third party cookies in the next version of Firefox (optional, but blocking is on per default). That’s great. Let’s get rid of the web site/usage tracking that all advertising services has.
Yet again I got shut down by Azure. This time the CPU quote was exceeded just a couple of hours into the new quota period.
I’ve switched to “Reserved” mode which doesn’t have the same limits (which is not said anywhere in the management interface).
I’ve just updated the API for my ADO.NET Fakes library. The library is a complete ADO.NET driver which is designed to aid you in unit testing.
(this entry was previously published as a PDF on twitter since I couldn’t access my blog)
I really liked my first experience with Azure. I’m also going to certify myself (I still am). But that’s before things stopped working and I got some not very good support. This blog entry
is awas a PDF because I currently can’tcan use my blog. This entry is all about why.
Sorry for being down again. My website mysteriously at all of my CPU quota at Azure = being suspended without notification.
More about that later (or check my PDF blog post in my twitter account)