Attention: We are retiring the ASP.NET Community Blogs. Learn more >

A Blog for Graymad

Musings about ASP.NET and more...by G. Andrew Duthie

  • More on w.bloggar...

    Sure, both of those solutions would probably work...but only if you know enough to know why the software's failing in the first place. If you don't know that going in, how are you going to know to install to a different directory? And like the suggestions made by Drew, these are workarounds, not true solutions. As such, they really don't address the larger issue of getting developers to test their software and make it run without elevated privileges, and without having to resort to workarounds or hacks.

  • Testing the WMP blog plug-in...

    Seems to work pretty well, with one caveat. Since I'm running w.bloggar using Run As... and an admin account, I have to run WMP with the same credentials in order to get the plug-in to work.

  • More on w.bloggar and admin permissions...

    Now, Drew is correct about the fix. But this only highlights my point. Applications aren't supposed to write user data to the Program Files tree in the first place. That's what the user's folder under the Documents and Settings folder is for. If w.bloggar wrote to the user's MyDocuments folder instead (or to the Application Data or Local Settings folders under the user's root folder), there would be no need for loosening the permissions on the w.bloggar install directory or running as admin to get it to work right.

  • Been out for a while...

    As I'm guessing some of you might have noticed, I've been absent from the blog world for a while. As Julia pointed out, this is because a couple of weeks ago, my son was born. His name is Joseph Andrew, and as one would expect, he's been taking up quite a lot of his daddy's time and attention of late. So if my blog entries are a little few and far between for a while, now you know why. :-) Cheeks!

  • First post from w.bloggar...

    Writing this post from w.bloggar. Nice UI, and good features (I especially like being able to easily post links to a new window, which has been a pain until now), but it breaks one of my primary pet peeves these days...it must be run using an administrator account in order for it to function properly.

  • Follow-up: BlogThis and SharpReader 0.9.0.1

    OK. I think I solved the problem I was seeing with BlogThis and SharpReader, thanks to some advice from Scott. The value for the "Key" key must be the value that you get from the URL for your own key. That is, you must:

  • BlogThis and SharpReader 0.9.0.1

    Scott wrote, of Luke writing:

    SharpReader 0.9.0.1 has been released. This version has the following changes:

    • Added a "File | Open" menu-item.
    • Added a "File | Subscribe" menu-item.
    • Mark updated items in italics.
    • Added a label before the address text box; ALT-D selects address text box.
    • Fixed KeepAlive bug that sometimes kept connections open too long.
    • Fixed bug in proxy authentication.
    • Better retry-mechanism for failed webrequests.
    • Fixed infinite post-threading.
    • Fixed unnecessary ListView refresh issue.
    • Added debug-statements at app-startup to find Win98/WinME problems. If you're running Win98 or WinME, please try to run SharpReader and send me the sharpreader.log file after it fails. Hopefully this will give me some more information that may help resolve this bug.
    • Open links in external browser now always goes to the system default browser.
    • implement Simon Fell's BlogThis plugin interface. If you save your plugin into a "plugins" subdirectory, SharpReader will find the plugin and make it available in the listview popup menu (shortcut ^B). Simon's last drop of Relaxer uses this plugin mechanism to post to RESTLog. Make sure you do NOT put IBlogThis itself in the plugins directory as this causes .NET to load this interface twice. Since SharpReader will use one copy of IBlogThis and your plugin another, SharpReader will not be able to find the plugin (because it will implement the wrong copy of IBlogThis)