I am an asp.net, MS Access LOB application developer for a medium sized company and I have made the desicion to start developing with Silverlight. There is a lot of information out there and I am a bit daunted by it all.
I currently use SqlDataSources for most everything I do in my asp.net apps, just directly access the SQL Server so I guess I'm not really using n-tier arcitecture, and for what I am doing, I don't see a real need to although I could be wrong. I have only one service that I created for use in a cascading combo box but thats about the extent of my knowlege of services and I basically copied and pasted from an online example.
I want to keep things as simple as possible, from the complexity of the code to learning curve, but I don't want to fall into a trap of starting in one direction just to find that I should have gone in another. As an example when I started with asp.net I got caught up in creating a business layer between my web app and the sql server that made things way more complicated for me than I needed but I didn't know any better at the time, I just followed some tutorials on the asp.net site. I am at the same crossroads here I think with deciding how to develop my data model. Here is the biggest question I have:
I am told that I should use the MVVC pattern. Is ther a compelling reason to include RIA Services with MVVC?
It just seems like I don't need to but I'm not sure. Any thoughts on the matter would be appreciated. Thanks.