R
Roy
I use ADO.NET Entity Data Model to generate code. I have two stored
procedures with complex logic. They return tabular records that are logically
related.
If I add function importer for the stored procedures, the utility does not
generate the class for the returned value for me. Instead it asks for the
object model classes.
If I converted the stored procedures as views and generate code for them, I
cannot specify the relationship between the views so the relationship between
the classes are lost.
Is there a way to generate classes that keeps the relationships when using
ADO.NET Entity Data Model utility for stored procedures or views? I use the
generated class for readonly purposes.
procedures with complex logic. They return tabular records that are logically
related.
If I add function importer for the stored procedures, the utility does not
generate the class for the returned value for me. Instead it asks for the
object model classes.
If I converted the stored procedures as views and generate code for them, I
cannot specify the relationship between the views so the relationship between
the classes are lost.
Is there a way to generate classes that keeps the relationships when using
ADO.NET Entity Data Model utility for stored procedures or views? I use the
generated class for readonly purposes.