navigation properties on derived types

Question

 

Now that "Astoria" has hit RTM, I decided to give it another go. I set up a scenario that I had tried months prior (without success). I didn't get very far this time, either. The error I am confronting is (paraphrasing) "Navigation properties on derived types are not supported...". There was a post on this subject way back in Nov '06 discussing the possibility that this might be supported one day. I guess it didn't make the cut for RTM

 

I suppose most folks wouldn't care too much, but I find this very disappointing. It means that if I'm going to use "Astoria", I have to greatly compromise the design of my entity model.

 

Are there any clever hacks around this limitation? Is there any hope that this limitation will be lifted in some future drop?

 

Thanks,

Daniel

 

 

Answer 1

You are right - this didn't make it for the V1 timeframe. We really wanted to support this so that users can use inheritance in the entity model. This is one of the most important features we are targetting for V2. V1 just went out, so it will be some time before we do a beta/ctp for the next release.

 

Pratik

Answer 2

I appreciate the realistic answer, even if that's not what I wanted to hear. Speaking of "realistic", how about if you folks just hand over the source code, and I'll fix it myself

 

Regards,

Daniel

Answer 3

Hi,  i would like to have a refresh of this answer...  To date, is there a workaround or a CTP that could let us do navigating properties with derived types within astoria?

In clear, is there a CTP for the V2 out yet, if not when will it be?

Thanks!

Answer 4

No no we dont tell you the answer, you have to pay for this kind of support

--------------joking aside

@ Everyone

No CTP as of yet boys and girls. And you know the answer for the question that has the word "when" on it. To spell it out: When it is ready.

You understand the implications of giving the community a time frame.

Nice if they deliver early but a storm of hate if it delivered late.

Daniel Portella Blogger from hell http://undocnet.blogspot.com

Iif this reply has answer your question please mark as the answer.

---

Daniel Portella - http://undocnet.blogspot.com - This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 5

Hi Daniel,

With CTP1 not supporting navigation properties on derived types is there any further information you can give us (especially timelines!) regarding this important feature?

Thanks,

Drew Loika

Answer 6

I just ran into this bug myself. I really wish the model would complain about navigation properties on derived types at startup though, as it does for other unsupported stuff like enums etc. I only discovered this discrepancy at run time when an entity set with derived types containing navigation properties was accessed.

This is really a deal-breaker as we're pretty far gone on this project and can't really change the model at this stage (not easily anyway). Is there any workaround?

As for v2, can you at least give us some kinda ball park figure on when we can expect some kinda release containing a fix for this issue?

Thanks,

---

Jimit Ndiaye

Answer 7

Does v1.5 CTP2 address this issue?

---

Jimit Ndiaye