Two issues I have with new Astoria

Issues with ADO.Net Data Services (Astoria) and VS sp1

1) After deleting a table from the Model, you can't add it back.  It does not show as a table to add.
2) Adding a table with the new DateTimeOffset type will fud the service with some unrelated error.  Took me a while to find this one.
3) I said before, sometimes you can't double click on the model object to object the designer.

Kinda big issues on the bug scale I would think.  Not sure how DateTimeOffset thing got passed testing.

littleguru said:

Have you tried to post these issues in the Astoria forums?

I posted on the ngs.  I posted here as well to maybe gain some eye share to the issues.

staceyw said:

littleguru said:

*snip*

I posted on the ngs.  I posted here as well to maybe gain some eye share to the issues.

If you can the team would like posts on the Connect site.

Hi staceyw,

Issue 1: if the table is already "known" to the designer, then you don't need to import it again. If you delete it from your conceptual model you can re-add it by creating a new entity and mapping it to the underlying table (in the mapping designer the table will still show up). The "update from database" thing is usually needed when you actually changed something in the database, or want to add something that you didn't add originally.

Issue 2: yeah, that's our bad. It's not that we didn't catch it, actually. Because of timing issues we couldn't get support for this data type in Astoria v1.

Issue 3: I've seen this too in my box, but couldn't reproduce it reliable. Do you happen to have the Silverlight tools installed? I have a "weaking founded" theory that these two are not interacting well...

btw - as littleguru mentioned, the best place for Astoria-related questions is the Astoria forums. The Astoria team and MVPs hang out there regularly.

-pablo