More on that RSS editor…

In the end, MSDN didn’t end up needing the RSS editor I wrote, so I’ve stripped out the features and content specific to their needs and started turning it into a more generic RSS creation tool. If you’d like to see it, as it is, you can run it from a ClickOnce install point here on my site. There are more features coming, and I’m revamping the style and behavior of the category system…. but you can try it out against copies of your own feeds or click File | New Feed to make new ones. Check out the Validate option on the menu, it will send whatever feed you have open to a web service enabled version of the system (coded up by Kent Sharkey), allowing you to check the validatity of your RSS without having to publish the file anywhere.

Note: If you have Beta 2 of the .NET Framework installed, the Click Once application will not install or run correctly. In this case, you need to run the VS remove tool (available from here)

Author: Duncan Mackenzie

I'm the Developer Lead for the Channel 9 team, formerly worked on MSDN as a developer, content strategist and author.

10 thoughts on “More on that RSS editor…”

  1. Not working from FireFox. Or Opera. From what I can tell that’s a ClickOnce issue, which only seems to work from IE. Nice one MS! So I’m sorry, can’t even look at it. Perhaps you could put up a download link?

    (Incidentally, Java Web Start DOES work from any browser.)

  2. It works for me in Mozilla and IE 6 (don’t have Opera). I think its something else that isn’t getting along with all browsers. I have a project that uses click once and works without a problem IE or Mozilla on my test server.

  3. Just found out that Install works (it just downloads the installer, which you have to start manually); it’s just the Launch link that refuses to work. ClickOnce complains about a missing .manifest (duh, that’s not downloaded when you click on the .application link).

    Never understood why MS decided to use both an .application and a .manifest; probably to be obnoxious and force people to use IE. Again.

    Anyway, not even close to ClickOnce. It was a click Install, click OK (save), open the download manager, right click to open folder, double click to start setup (or just double click on the download bar). Which saves you how many clicks? Not one I tell ya. And after the setup the launch link still won’t work (because it’s broken to start with: a href points to a single resource, not two).

  4. Ruben, almost every single one of those clicks occurs for you because you were downloading the files not just running them directly. I believe that this is the default and only choice in Firefox, and I understand the reason for that, but in the situation where you can click on the link and it can be run directly at that point it truly does occur all in one click.

    What happens from Firefox is that the .application file is saved locally and then run from there, which changes the path…. which means that instead of looking for the .manifest and other files back on the web, it looks for them in the same directory as the .application file (which is now local to your machine).

    It isn’t an ideal situation when you are going through a download manager, that is certainly true…

  5. Well I *know* what’s going wrong. It’s just that I’m very surprised that nobody cared enough to solve this before the product got released. Well, unfortunately that would be lying; it’s pretty much what I expected. (Ooh, big bad MS, naught boy you!)

    But at least you can say that this is clearly a case where MS didn’t copy Java. Unfortunately that is.

    Java Web Start simply works with a single click, in both IE and Firefox because you’ve only got a single .jnlp file, not an .application and .manifest file. .jnlp files are also self-describing, so you can send a .jnlp file and have the user run it. ClickOnce prohibits this kind of usage.

    PS. having a download manager by default is actually a good thing. But that’s probably something to tell the IE7 team 😉

Leave a Reply