This is currently a big limitation, however Microsoft is working on a flow-down business entity framework (code name Alexandria) that will allows the business objects defined against the .NET runtime to be referenced from Silverlight.
This was presented at the PDC & various MDCs across the country last fall, but unfortunately there is no timeline announced for when it will be released.
The way I have handled this limitation is, I perform the majority of my business logic on the server (using the .NET objects) based on WCF service calls. The data resulting from this logic is returned using DataContract classes which I can then use to populate
local Silverlight business objects, which duplicate only that business logic that the UI itself needs to know about but have the same "shape" as the DataContract class.
It's not ideal, certainly, but it is working. I look forward to the flowdown business objects though too because duplicated code is never ideal.
--
Anye Mercy
AnyeDotNet.blogspot.com
Please "Mark as Answer" the posts that help you - this lets others know the problem has been solved and helps others having the same problem know which solution works. Thanks!
anyeone
Participant
826 Points
199 Posts
Re: Silverlight project "add reference"
Feb 06, 2009 03:17 PM | LINK
This is currently a big limitation, however Microsoft is working on a flow-down business entity framework (code name Alexandria) that will allows the business objects defined against the .NET runtime to be referenced from Silverlight.
This was presented at the PDC & various MDCs across the country last fall, but unfortunately there is no timeline announced for when it will be released.
The way I have handled this limitation is, I perform the majority of my business logic on the server (using the .NET objects) based on WCF service calls. The data resulting from this logic is returned using DataContract classes which I can then use to populate local Silverlight business objects, which duplicate only that business logic that the UI itself needs to know about but have the same "shape" as the DataContract class.
It's not ideal, certainly, but it is working. I look forward to the flowdown business objects though too because duplicated code is never ideal.
Anye Mercy
AnyeDotNet.blogspot.com
Please "Mark as Answer" the posts that help you - this lets others know the problem has been solved and helps others having the same problem know which solution works. Thanks!