what's Difference b/w creating a RIA Services Solution (i.e. Enabling RIA Services checkbox) and RIA Services class library (i.e. using a project template)
What are the functional differences amongst the two?
相关问题
- how to Enumerate local fonts in silverlight 4
- Free Silverlight mapping with Bing maps and OpenSt
- Custom number picker?
- How to upgrade/install Upstart deamon version 1.5
- Error using ResourceDictionary in Silverlight
相关文章
- Service层和Dao层一定要对应吗?
- k8s 访问Pod 时好时坏
- Async task does not work properly (doInBackground
- New Windows Application - What language?
- relative url in wcf service binding
- Embedded images not showing when in a UserControl
- Keeping alive Intent Service after application is
- A proper way to Debug a Service in Android Studio?
The library option means you can share it between projects more easily. The solution option is just simpler to get working (not much though).
There is no real functional difference between them. They are just different project structures.
Each RIA services library turns into a web WCF web service library, that you can simply link with your web application and a client side library that you link with your Silverlight client app.
These are not simple class libraries: They are "RIA-linked" together in pairs and generated/shared code from the service library propagates to the matching client library.
Nowadays we always create RIA services libraries in our projects.