Design issue
-
hi guys i have to start a new project (silverlight based), but i am unable to find a standard and latest design structure, should i use L2s or EF, i want to follow to n-tier architecture ,there are many sample applications i have seen but there WCF services are included in the web application why ?but i want my WCF services in the separate project , am i thinking in a right way ? please any help , thanks , regards.
Tauseef A Khan MCP Dotnet framework 2.0.
-
hi guys i have to start a new project (silverlight based), but i am unable to find a standard and latest design structure, should i use L2s or EF, i want to follow to n-tier architecture ,there are many sample applications i have seen but there WCF services are included in the web application why ?but i want my WCF services in the separate project , am i thinking in a right way ? please any help , thanks , regards.
Tauseef A Khan MCP Dotnet framework 2.0.
Silverlight is strictly client-side technology. WCF and other web services are server side. You don't have to host your web services in the same web application that hosts the Silverlight application. In fact, Silverlight apps don't need to be hosted in web applications at all. For n-tier, how you connect your client and server tiers is up to you. You have some options built-in: Accessing Web Services in Silverlight[^] For EF you get even more help built-in: WCF RIA Services[^] Even though WCF RIA Services is still beta, the Visual Studio 2008/Silverlight 3 version has a go-live license. I use it in production applications and it works great - saves a ton of plumbing code usually needed for typical n-tier/CRUD type stuff.
Mark Salsbery Microsoft MVP - Visual C++ :java: