Last November at PDC 09 we announced the Open Data Protocol (OData), providing a way to unlock your data and free it from silos that exist in applications today. OData makes it easy for data to be shared in a manner that follows the philosophy of Open Data and enables the creation of REST-based data services. These services allow resources identified using Uniform Resource Identifiers (URIs) and defined in an abstract data model, to be published and edited by Web clients using simple HTTP messages. OData enables a new level of data integration across a broad range of clients, servers, services, and tools.
This morning during the Keynote at Mix 2010, Doug Purdy announced the re-launch of OData.org and the release of the OData SDK.
The OData SDK brings together a wealth of resources to help developers participate in the OData Eco-system including:
Also announced today at Mix, there are some new OData services available publicly:
How can you get involved in the OData ecosystem? Check out OData.org – Expose OData – and the next time you’re developing an app ask yourself, is there a feed for that?
- The OData Team
How about a single PDF printable version of all the OData specs? Or at least the individual specs as PDF files? (Some of us prefer dead trees. :-) )
+1 to pdf version of the specs.
Hard to take this too seriously. Where is the VB6/VBA client library? What about service libraries?
VB6 is probably unsupported, so they probably won't release a library themselves. But I think one could be made from the specs or other libraries.
Seriously, VB6/VBA? Why not go all the way back to Basic? I think it may be time to migrate that code to .NET. VB6 is a dead language and has since been 4 times surpassed. Asking people to waste their valuable time on supporting VB6 is like asking web designers to make their site compatible with Internet Explorer 4. I for one am sick of all the VB6 compatibility crap. Why is Microsoft so bloated now? Oh yea, they have to support Stone Age programmers and a dead language that people can’t just let go. VB 1-6 have been retired and Windows 7 will be the last OS to even include the VB6 core runtime environment. Thankfully, most of the components (everything except for core) are already not installed on or supported by Windows Vista and Windows 7. Finally, after 10 years of dragging a corps behind them, Windows 8 will not support ANY functionality of VB6. Migrate or be replaced.
I see both sides of the VB6 compatibility issue. The problem boils down to thousands of small businessmen who bought or commissioned software years ago that works just fine running on old hardware. Those guys are the least able to financially support our audacious technology advances. They don't see or understand the advantage to buying hardware and software that's obviously several orders of magnitude beyond what they really need to do their business. They see it as technological blackmail, and frankly, I feel bad for them. Sorry to participate in the hijacking of this discussion. I just couldn't resist.
Thats the kind of people that should consider moving to Azure or a similar cloud offer. They don't need to buy new hardware and what not and would pay only for what they actually use.
What about the Compact Framework? Is it planned any support?
oh nice .. :) all i understand that we will be able to select, add, delete and update data with a simple HTTP Request. .. i hope microsoft will not be disabling the previous tools...
hope this will help my library 2 work.....
"I see both sides of the VB6 compatibility issue. The problem boils down to thousands of small businessmen who bought or commissioned software years ago that works just fine running on old hardware. Those guys are the least able to financially support our audacious technology advances. They don't see or understand the advantage to buying hardware and software that's obviously several orders of magnitude beyond what they really need to do their business. They see it as technological blackmail, and frankly, I feel bad for them. Sorry to participate in the hijacking of this discussion. I just couldn't resist." -if those people can't afford to upgrade, their businesses suck and they should go out of business
# Maximus said on March 24, 2010 4:20 AM:
"if those people can't afford to upgrade, their businesses suck and they should go out of business"
hmm, modern consumerism, it ain't broke but I'll fix it anyway. VB6 is old and is supposed to be dying but why would you replace a core business product that does what you need and is proven through time served? That said while the hardware keeps going and the OS is alive it's not a worry.
The dilemma of wether to continue VB6 support is a difficult one for both sides. A company who has legacy VB6 applications shouldn't be forced to replace them just because they are old, if they do the job they were intended for and do it well then there is unlikely to be a business case for upgrading.
(and to say "if those people can't afford to upgrade, their businesses suck and they should go out of business" is a rediculous statement - you are obviously not business minded Maximus and should stick to the coding ;-) )
On the other side it doesn't make good business sense for Microsoft to continue support for VB6, resources would be much better spent furthering more modern languages and developments.
I think the key is a comprmise between Microsoft and the consumer, the fact that Microsoft have supported VB6 for such a long time, in my opinion, is enough of a comprimise from Microsofts side.
I suppose some comfort can be taken in the fact that any companies which still have core systems written in VB6 probably have had them for quiet some time and need little support any more.
There is nothing stopping the business owners from using the VB6 apps. However, the decision to use the VB6 apps (and not be forced to upgrade the code) comes with the limitation that they use it under an older OS. So if they want to stick with their VB6 apps, then they are also stuck with NT4 and Win98.