[dscottj]

Our organization has unique business rules and workflow processes for managing our members. However, we wish to store our data in RE. We have determined NetCommunity will not be suitable for our needs. What are your general impressions of the RE API? I am a certified professional .net web application developer (2.0 & 3.5, C#). I'm familiar with OO design patterns, TDD, and enterprise development best practices. I have worked with various Microsoft Office and third-party APIs in previous projects.

From my perusal of the FAQs, it would seem there are a few hoops to jump through to get the API COM object working in .net 2.0+, but they appeared straightforward enough. I'm especially interested in opinions about the APIs design, it's completeness, comparative ease-of-use, and if anyone has had experience incorporating it into independently developed web applications.

I have a suspicion I'm not the first person to ask this question, but couldn't find a post directly addressing it when I searched. URLs to previous discussions are welcome!

[kstrange]

We've been using RE API with VB6 windows apps, then used upgrade wizard to VB.Net 2005 - .Net handles the COM objects with no problem, so probably C# web will work OK.
I would rate the APIs design, completeness, comparative ease-of-use as very good -once one has a basic understanding of the data structure.