Community Server Issues - Part I

re: Community Server Woes - Part 1

Don Demsak — Fri, 13 May 2005 13:35:07 GMT

Can anyone say Code First Versus Contract First?

This example is a great example of one of the major issues with the Code First approach that VS embraces, it hides the fact that a change to the underlying class will cause a break in the generated contract. See Aaron Skonnard's Contract First Service Development articles in May and June 2005 MSDN Mag: http://msdn.microsoft.com/msdnmag/issues/05/05/ServiceStation/default.aspx and http://msdn.microsoft.com/msdnmag/issues/05/06/ServiceStation/default.aspx

re: Community Server Woes - Part 1

Scott — Fri, 13 May 2005 13:56:51 GMT

You are correct. You are not using the same version available for public download yet.

The web service API is something we did not have enough time to investigate properly in 1.0.

So in 1.1 we made a couple of changes and improvements. The goal is to lock the CS public API (web service included) by version 1.2 (late summer/early fall).

The reason for the above change was to make sure Blogs, Gallery and Forums (and others soon) can have a more "common" API. So if/when a gallery web service is published, ServiceCredentials will be re-used.

HTH,
Scott

re: Community Server Woes - Part 1

Heath Stewart — Fri, 13 May 2005 20:42:59 GMT

You should be able to modify the client proxy and add fields for each element. With the right XmlElementAttribute, the field would not be null while the other one would.

re: Community Server Woes - Part 1

guowu — Fri, 13 May 2005 22:45:29 GMT

Don: Great articles.

Scott: thanks for taking time explaining this. It makes sense in your roadmap. I just hope changes in 1.2 will not be as dramatic as this time. I will have more to say in the coming posts.

Heaths: I thought about that. It may not be hard. But it definitely will get messy. You can try to unify the client proxy for the following to web referecne:
1) http://blogs.msdn.com/blogservice.asmx
2) http://www.trefry.net/blogs/blogservice.asmx
Please share with me if you do come up with something neat, :-)

Community Server Issues - Part II

Guoqiang Wu's Blog — Wed, 20 Jul 2005 06:24:25 GMT

A while back, I complained about the big pain caused by the SOAP header change between Community Server...

re: Community Server Issues - Part I

Kevin Daly — Fri, 05 Aug 2005 19:55:54 GMT

I've just hit this one, and frankly whatever the reason, it stinks.
I believe there is a responsibility to provide a degree of consistency for published APIs...but apparently the message should be "don't use the web service because we haven't finished playing with it"...but then MetaWeblog on the other hand has been provided as an add-on, so we can't count on it *being* added on...

My patience is sorely tried.