This question is locked. New answers and comments are not allowed.
Hi,
I have an application im working on. it consist of:
- Entity Model + Data Access powered by Open Access
- Web Application
- Silverlight Application
Usually, I build a mid tier for the Business Logic, and reference it in the web app. but this is not possible with silverlight so i use Astoria.
I have two questions:
1)
When using Astoria - for example with the sample code for use with open access from the forum - I have an Order class, in that class there is a field of type Shipper. The context has a property of Orders (that extends all the orders into IQueriable) but doesnt have a Shippers property. When i run it this way - i get a shipper object inside the order object i get. If i declare a Shippers property in the context, the shipper field in order object - is always null. Its this way for every similar scenario. why is that?
2)
What is the best design method? Usually i have all of my business logic in the mid tier - in this case im forced to have all the logic done in the silverlight app. what about if i have some logic that i want to use in the web app and in the silverlight app - and its not just
loading of data, but something ,more complex that requires parameters and logic?
The currently available methods are declaring static WebGet operation (in the service file in the web app) or declaring interceptors (BTW - really studpid name for it) which are not good business tier solutions.
I would really appreciate your thoughts...
I have an application im working on. it consist of:
- Entity Model + Data Access powered by Open Access
- Web Application
- Silverlight Application
Usually, I build a mid tier for the Business Logic, and reference it in the web app. but this is not possible with silverlight so i use Astoria.
I have two questions:
1)
When using Astoria - for example with the sample code for use with open access from the forum - I have an Order class, in that class there is a field of type Shipper. The context has a property of Orders (that extends all the orders into IQueriable) but doesnt have a Shippers property. When i run it this way - i get a shipper object inside the order object i get. If i declare a Shippers property in the context, the shipper field in order object - is always null. Its this way for every similar scenario. why is that?
2)
What is the best design method? Usually i have all of my business logic in the mid tier - in this case im forced to have all the logic done in the silverlight app. what about if i have some logic that i want to use in the web app and in the silverlight app - and its not just
loading of data, but something ,more complex that requires parameters and logic?
The currently available methods are declaring static WebGet operation (in the service file in the web app) or declaring interceptors (BTW - really studpid name for it) which are not good business tier solutions.
I would really appreciate your thoughts...