Eye Glazer

After wasting a few hours, I've decided it's not worth it to proceed any further. If you want to know the schedule (or just the next-run-time) of a subscription, just go to the SSRS web site (the web UI). It's too much of a pain to use the ReportingService2005 interface. The simple back-story to this is that I've made an app that handles uploading (create/update) all of our reports (.RDL files) from the local computer to an SSRS instance. Doing this through the web UI is incredibly tedious, error-prone, and my Carpal Tunnel flares up after a few reports. So now that I'm done, I decided that it would be nice to see information about all of the various subscriptions that people have defined for the various reports. It's not hard to add this in. You just call ListSubscriptions(null, null) after logging in with an admin account. But the Subscription object has no information about the schedule it runs against! Well, actually it can tell you a few things via the...

Hopefully, this will help me the next time I bang my head against the wall trying to figure out why an application of mine is going crazy, but none of my error-handling code seems to be working. The core threads that explain this are here: Visual Studio doesn't break on unhandled exception with windows 64-bit The case of the disappearing OnLoad exception   Silent exceptions on x64 development machines (Microsoft Connect) The summary is this: If an exception is thrown on Windows x64 (Vista, Win2k3, Win2k8, Win7, etc.) and it hits a kernal-mode boundary, it will be dropped. Execution will continue at that point as if no exception had been thrown. The simplest example is to create a new WinForm application and simply throw an exception from the OnLoad event. Not only will VS2008 not stop execution on that exception during debugging, but if you run it in "Release" mode, there will also be no trace of the exception. In this case, your code (OnLoad) was ultimately ca...