Open Data Protocol Visualizer Extension for VS2010 – Screencast

by mosessaur| 03 May 2010| 3 Comments

Last week I introduced a screencast talking about OData Visualizer Extension for VS2010 on http://odataprimer.com community.

It’s a How-To video on how to download, install and start working with OData Visualizer Extension for Visual Studio.Net 2010. OData Visualizer is an extension for VS2010 made by Microsoft Data Modeling team

I case you missed it, you can watch it on ODataPrimer website. You can also download an HD video (~35Mbs).

You can also subscribe to ODataPrimer channel on yourtube for future updates and videos.

Hope you’ll enjoy it.

Comments (3) -

Yasser Makram
Yasser Makram Egypt on 5/3/2010 7:21 PM Awesome video, thank you for the excellent demonstration. It will surely make my life easier dealing with OData.
|
Ahmed Adly
Ahmed Adly Egypt on 5/26/2010 3:17 PM [Modified]
Salamo Alikom Moses

I want just to comment about the previous post related to the CodeCamp in ASU, Thanks for the nice presentation, but I have a simple comment on Slide 6, I think the relation between the Decorator Class and the IComponent is not "is-a", also between the Decorator & Component, because "is-a" as you know better than me is Generalization, and Generalization should be between 2 Similar Types ( 2 Classes , or 2 Interfaces), but if we have 2 different types (Class & Interface, Class & Component), I think the exact relation should be Realization, which is represented by dotted line and a white triangle as in the ppt presentation, so on my opinion the relation is true but we just need to change the label on the arrow from "is-a" to be "implements" or "uses" according to IBM notifiers, Thanks again for the nice article Smile
|
Muhammad Mosa
Muhammad Mosa Egypt on 5/29/2010 2:11 AM Thanks for the comment brother.
Assume you have this interface ICategoryRepository, and a class that implements this interface CategoryRepositoryDecorator.
In natural language does it feel wrong to say that an instance of CategoryRepositoryDecorator is a actually instance of ICategoryRepository?
No it doesn't! In fact it is an ICategoryRepository. However it is totally right to say that it implements an ICategoryRepository. But that doesn't mean it's wrong to use is a to describe the relation.
The decorator uses the interface and implements it at the same time. Note that implementing an interface means you inherits it somehow. But it makes sense for use to say implements more than inherits. At the end this is a generalization as well on a way or another.
Returning to any book you'll find that the relation is described as "is a". And at the same time "has a".
I hope you got my point. But I can assure you that this is not wrong annotation. And you can return any reference and point me to any if you find that it's wrong.
|

Pingbacks and trackbacks (1)+

Comments are closed