Hello.
As many of you know, REST services have now been integrated in the current Visual Studio 2008 SP1.
You developed the wrapper classes for .NET Framework, not the compact edition... so if somebody is wanting to release an application to run over Windows Mobile, for example, they have to develop their own wrappers, that is an awful task.
My suggestion is: why don't you make the REST services to be Visual Studio 2008 SP1 compliant???
If you don't want to do so, you could at least publish the source code to port it easily. Since you obfuscated the key assemblies, you're blocking some developments...
José Manuel NietoTranslator of the Spanish Language Pack for Community Server 2008Developer of CS Writer
Pardon me for not knowing, but what in them is not compatible with Visual Studio 2008 SP1?
The next release of CS will have the webservices unobfuscated, however I do not know about releasing the source code.
Hello Ken :)
I don't say it's not compatible, but it doesn't use the new "Data Services" approach that brings SP1. I'm talking about Astoria. It could be really good to adapt CS 2008 to it. It's my suggestion.
If you don't have plans to do it (it would be a brand new feature to attract new developers for every kind of applications for CS), it's not bad that in the next version, you won't be obfuscating the code.
Oh dear, I love open source in so many situations :P How could you be alive without that?
Alright, I'm ready to start to code a new project for Windows Mobile if you choose the right direction. If not, I will be very sorry. Really.
Regards.
I share your frustration and I know that I'm not the only one. I invested a huge amont of money to purchase a Community Server license naively thinking that since I'd get all the source code, I'd be pretty much free to do anything I wanted with it, only to realize that large chunks of the source code are not actually provided, even to paying customers.
A few week ago, I had to implement a few APIs to allow an external application to access data from a custom application I create and that was hosted on my Community Server site. Knowning that Community Server already had an extensive REST API, I thought that this would be a 1-hour job and that I would just have to add a few more functions to the existing API, withough having to re-invent the wheel and re-implement the authentication, access control, logging and serialization mechanisms. That's what I paid for after all. Boy, I couldn't be more wrong. The hour I thought it would take to implement the entire thing was spend looking through the whole SDK trying to find where the code for the API was, only to eventually realize that not only the code wasn't there at all but the REST API assembly had been obfuscated preventing me from even being able to reuse a single helper function. I ended up having to re-implement everything from scratch. What a waste of time.
It should be really frustrating... I hope they realize that CS could be more successful and popular if they stop blocking road for us developers. We only want to make the product more flexible.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com