I might be missing something really obvious, but in BlogItem is seems I am getting a string that is not in any XML format.  For example, I get channelTitlelinkchanneldescriptionIndustry unites against drunk dogs... as one big ugly string.

Here is the code I am using to see this string

XPathNavigator xnav = rssFragment.CreateNavigator ();

MessageBox.Show(xnav.XmlLang );

MessageBox.Show(xnav.ToString() );

Ideas???

You're seeing expected behavior for what you're doing...but what you WANT to be doing  is something like the following:

XPathNavigator nav = rssFragment.CreateNavigator();

XPathNodeIterator iterator = nav.Select("/rss/channel/item/description");
while (iterator.MoveNext())
{
   description = iterator.Current.Value;
}

iterator = nav.Select("/rss/channel/item/title");
while (iterator.MoveNext())
{
   title = iterator.Current.Value;
}

That should get you started...

Yep starting from the root did the trick.  Thanks.

NewsGator Rocks!  I simply love it. 

I assume most of the Outlook related code you have is COM, right?

One more question and it is probably as obvious as the first...

Why do these simple return "channelTitle" and "channelLink"?

iterator = xnav.Select("/rss/channel/title");

while (iterator.MoveNext())

{

string link = iterator.Current.Value;

MessageBox.Show(link);

}

iterator = xnav.Select("/rss/channel/link");

while (iterator.MoveNext())

{

string link = iterator.Current.Value;

MessageBox.Show(link);

}

Cool, glad it's working better now.  And I'm glad you like NewsGator!

On the channel title and link, NewsGator doesn't actually store channel information for the items, so it doesn't have anything useful to put in those items.

They are, however, required by the RSS 2.0 spec. In this case, you should just ignore them.

If you have a scenario where you think you need this information, let me know so we can see if there's some way to handle it, or if there's a good use case to start providing this information.

Gotcha.  The only way to do this right now would be to parse the link out of the description - we will always put it in there, in the same format, so you should be able to parse it out.

In the next release, this information will be provided directly.