Out of the box, CS has virtually no implementation for CommentRSS (which is strange as .Text supports it 100%…curious as to why Telligent didn’t include it with CS).  We followed the same pattern that .Text uses by implementing a custom httpHandler to intercept requests for a specific Url that comments are sent to from feed readers.  The first thing you’ll need to do is add a new class in the CommunityServerBlogs project (in the Components/Syndication folder); name it RssCommentHandler.cs, and make sure to change the namespace to CommunityServer.Blogs.Components (as C# projects will include the full directory structure in the namespace by default…interestingly enough VB.Net doesn’t do this, defaults to the root namespace).  Here’s the code you’ll need to add to the new class:

using System;

 using System.Web;

 using System.Web.Caching;

 using System.IO;

 using System.Xml;

 
 // CS

 using CommunityServer.Components;

 using CommunityServer.Blogs.Components;

  
 
namespace CommunityServer.Blogs.Components

 {

     /// <summary>

     /// Summary description for CommentHandler.

     /// </summary>

     ///

     // jervis -- fix for posting comments from feed readers

     public class RssCommentHandler : IHttpHandler

     {

         private RssCommentHandler() { }
 

         #region IHttpHandler Members
 

         public void ProcessRequest(HttpContext context)

         {

             HttpRequest request = context.Request;

             if(request.RequestType == "POST" && request.ContentType == "text/xml")

             {

                 XmlDocument doc = new XmlDocument();

                 doc.Load(request.InputStream);
 

                 User user = Users.GetUser();

                 int postID = getPostIDFromUrl(request.RawUrl);
 

                 WeblogPost commentedEntry = WeblogPosts.GetPost(postID, false, true, false);

                 Weblog blog = commentedEntry.Section as Weblog;
 

                 // if comments aren't enabled, throw an http forbidden exception

                 if (!blog.EnableComments)

                 {

                     throw new HttpException(403, "Comments are not enabled");

                 }
 

                 Permissions.AccessCheck(blog, Permission.View, user);
 

                 string name = doc.SelectSingleNode("//item/author").InnerText;

                 if(name.IndexOf("<") != -1)

                 {

                     name = name.Substring(0,name.IndexOf("<"));

                 }
 

                 WeblogPost post = new WeblogPost();

                 post.SubmittedUserName = name.Trim();

                 post.BlogPostType = BlogPostType.Comment;

                 post.SectionID = blog.SectionID;

                 post.ParentID = postID;

                 post.Body = doc.SelectSingleNode("//item/description").InnerText;

                 post.Subject = doc.SelectSingleNode("//item/title").InnerText;

                 post.TitleUrl = checkForUrl(doc.SelectSingleNode("//item/link").InnerText);

                 post.IsApproved = true;

                 post.PostDate = DateTime.Now;

                 post.BloggerTime = DateTime.Now;

                 WeblogPosts.Add(post, user);

             }

             else

             {
 
                      

             }

         }
 

         private string checkForUrl(string text)

         {

             if(text == null || text.Trim().Length == 0 || text.Trim().ToLower().StartsWith("http://"))

             {

                 return text;

             }

             return "http://" + text;

         }
 

         private int getPostIDFromUrl(string uri)

         {

             try

             {

                 return Int32.Parse(getReqeustedFileName(uri));

             }

             catch (FormatException)

             {

                 throw new ArgumentException("Invalid Post ID.");

             }

         }
 

         private string getReqeustedFileName(string uri)

         {

             return Path.GetFileNameWithoutExtension(uri);

         }
 

         public bool IsReusable

         {

             get

             {

                 return true;

             }

         }
 

         #endregion

     }

 }

The next change is in CommunityServer.Blogs.Components.WeblogRssWriter.PostComments method.  Add the following code:

// Jervis -- fix for posting comments from feed readers

// only write the wfw:comment tag if comments are enabled for this weblog

if (CurrentWeblog.EnableComments)

{

    this.WriteElementString("wfw:comment", FormatUrl(BlogUrls.Instance().RssComments(CurrentWeblog.ApplicationKey,p.PostID)));

}

As we’re looking for a new RssComments Url, we need to modify the CommunityServer.Blogs.Components.BlogUrls class with a new method to find the rewritten Url; add this method to this class:

// jervis -- fix for posting comments from feed readers

public virtual string RssComments(string applicationKey, int PostID)

{

    return FormatUrl("weblogRssComments", applicationKey, PostID);

}

We then need to tell CS how to rewrite this Url so that it formats correctly; thankfully the infrastructure for this is already in place via the SiteUrls.config file; add the following element in the HomePages section:

<!-- jervis fix for posting comments from feed readers -->

<url name = "weblogRssComments" location = "weblogs" path="rsscomments/{1}.aspx" pattern="rsscomment

And finally, we need to map an httpHandler to our newly created RssCommentHandler class to intercept requests for rsscomments/*.aspx; add the following element to the httpHandlers section of the root web.config file:

<!-- jervis fix for posting comments from feed readers -->

<add verb="POST" path = "rsscomments/*.aspx" type="CommunityServer.Blogs.Components.RssCommentHandler,

Done.

We will say this about CS; it’s Url rewriting infrastructure is powerful stuff; adding a new Url is a snap with it…this would have taken much longer without this in place.  Oh, and my new website is now officially done.

Reasons why you must trust ASPHostPortal.com

Every provider will tell you how they treat their support, uptime, expertise, guarantees, etc., are. Take a close look. What they're really offering you is nothing close to what ASPHostPortal does. You will be treated with respect and provided the courtesy and service you would expect from a world-class web hosting business.

You’ll have highly trained, skilled professional technical support people ready, willing, and wanting to help you 24 hours a day. Your web hosting account servers are monitored from three monitoring points, with two alert points, every minute, 24 hours a day, 7 days a week, 365 days a year. The followings are the list of other added- benefits you can find when hosting with us:

- DELL Hardware
Dell hardware is engineered to keep critical enterprise applications running around the clock with clustered solutions fully tested and certified by Dell and other leading operating system and application providers.
- Recovery Systems
Recovery becomes easy and seamless with our fully managed backup services. We monitor your server to ensure your data is properly backed up and recoverable so when the time comes, you can easily repair or recover your data.
- Control Panel
We provide one of the most comprehensive customer control panels available. Providing maximum control and ease of use, our Control Panel serves as the central management point for your ASPHostPortal account. You’ll use a flexible, powerful hosting control panel that will give you direct control over your web hosting account. Our control panel and systems configuration is fully automated and this means your settings are configured automatically and instantly.
- Excellent Expertise in Technology
The reason we can provide you with a great amount of power, flexibility, and simplicity at such a discounted price is due to incredible efficiencies within our business. We have not just been providing hosting for many clients for years, we have also been researching, developing, and innovating every aspect of our operations, systems, procedures, strategy, management, and teams. Our operations are based on a continual improvement program where we review thousands of systems, operational and management metrics in real-time, to fine-tune every aspect of our operation and activities. We continually train and retrain all people in our teams. We provide all people in our teams with the time, space, and inspiration to research, understand, and explore the Internet in search of greater knowledge. We do this while providing you with the best hosting services for the lowest possible price.
- Data Center
ASPHostPortal modular Tier-3 data center was specifically designed to be a world-class web hosting facility totally dedicated to uncompromised performance and security
- Monitoring Services
From the moment your server is connected to our network it is monitored for connectivity, disk, memory and CPU utilization - as well as hardware failures. Our engineers are alerted to potential issues before they become critical.
- Network
ASPHostPortal has architected its network like no other hosting company. Every facet of our network infrastructure scales to gigabit speeds with no single point of failure.
- Security
Network security and the security of your server are ASPHostPortal's top priorities. Our security team is constantly monitoring the entire network for unusual or suspicious behavior so that when it is detected we can address the issue before our network or your server is affected.
- Support Services
Engineers staff our data center 24 hours a day, 7 days a week, 365 days a year to manage the network infrastructure and oversee top-of-the-line servers that host our clients' critical sites and services.