ria

Silverlight can use WCF, Web Services, REST based services, .NET RIA Services, but it seems like Silverlight and .NET RIA Services are preferred most. I want to know if there are any common issues [which can be a show stopper if one goes ahead with this combo] that you have seen in practical implementation of SL with .NET RIA Services. Thanks, Rahul Working with metadata (and writing it by yourself) is really pain in the ass. Especially when you need to update your model. RIA tutorial applications look quite well on a small database but working with a model consisting of dozens of entites, you

When using .NET RIA Services and MVVM in Silverlight 3.0 is there a difference between the Metadata type from RIA Services and the ViewModel from the MVVM pattern? Are these the same thing or should they be keep separate? The metadata type is a sealed internal class to the partial Entity class. There doesn't seem to be a proper separation there but the metadata type can also be decorated with attributes for Validation which makes it look like a ViewModel. I've searched around but I didn't see anything that talks about this in any detail. Agree with ChuckJ - generally the DomainContext forms

I am torn between Wicket and Vaadin. I am starting a micro-isv and need to make a choice of web framework. I have narrowed down my choices to Wicket and Vaadin. I have used both frameworks and I love them both. however I need to make a choice. If If I choose Vaadin: I wont have to worry much about the look and feel. It comes with nice themes. I will do all my programming in Java which am very good at and wont have to spend time hacking CSS which am not very good at. And most of the components that I will need for a business applications are there OUT OF THE BOX including, desktop like layout,

I have a need to pass an HTTP header for each an every RIA Service request being made from a Silverlight app. The value of the header needs to come from the app instance, and not from a cookie. I know this can be accomplished by putting it in the DTOs, but it's not an option because a lot of our service calls use Entities and change sets, so there's no base class to tie into for all requests. So I'm looking for a centralized and safe means to pass something back with each request so the developers do not have to worry with it. A custom HTTP header would work fine, but I don't know how to

I wonder if someone have tried using WCF RIA Services in XAML based metro application. If you have any blog or sample please share. As a matter of fact I did and here's the trick :) I added a " Service Reference " to my WCF service exposing an ADO.NET Entity Framework model. The problem is that in a XAML/C# Metro app, executing the following code fails: SampleEntities ctx = ((App)Application.Current).Context; var query = from p in ctx.Products where p.Name == name select p; foreach (Product p in query) /** this line fails **/ { // do stuff } Here's the exception you'll get at runtime:

I need some help in choosing the right way for my RIA. I do want to use a javascript widget library - possibly ExtJS. I'm not sure however if I should try to get around programming in Javascript through ExtGWT or other solutions like Rialto Python . What are your experiences with web application frameworks that do not require you to program in Javascript? For instance, is it a big disadvantage to abandon technologies like jQuery if heading for GWT? You don't lose a ton of functionality in ext-gwt, but it's not a flawless import of ext either. The things that most influence deciding about

I've recently heard about Apache Pivot being moved to the Top Level Projects category and I was wondering who has tried the most recent version and compared it to other RIA tools. What are the proper categories for comparison? It seems to be easier to pick up for Java developers since JavaFX has a different scripting language. The Pivot developers say that Pivot is what Sun should have made instead of JavaFX. Good to hear from you. :-) I agree that we tend to focus more on applet deployment in Pivot's design. However, there is nothing inherent in the platform that prevents an application from

As a Silverlight newbie, I am finding it really hard to set up an RIA Web service. The examples available on the web almost always refer to Entity framework as the ORM but we are using NHibernate as our ORM. I am aware of the tutorial by Brad Abrams where he uses NHibernate as the ORM but most of it goes above my head because I am also a newbie at NHibernate and some of the concepts of RIA are not clear to me e.g. DomainService. I'd like to first keep it simple and ignore the ORM at the moment. So, can anyone point me in the right direction as to how to get a "vanilla" web service going with