We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now


Silverlight Newby with some questions

AkAlan asked
Medium Priority
Last Modified: 2013-11-12
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.
Watch Question

Sathish DVSenior Software Engineer

Hi AkAlan,
If u have started with ASP.NET, better continue with the same and try to get some good hold on ASP.NET. You said writing n-tier app is little bit tedious, but that's not true. Try to change your perception. Writing n-tier application will make ur app more flexibile, rigid, reusable, robust and scalable and also maintainable. So try to get through some good ASP.NET design patterns. Refer http://wiki.asp.net/page.aspx/276/design-patterns/ . And ASP.NET itself created on MVC Pattern. Model - ur data model class, View - ur User Interface, Controller - Code behind or Class library which controls the user events and data events. So getting through MVC is really good. So after all ASP.NET, MVC bla bla bla...... RIA services is another set of components were WCF services is tailored to use with RIA apps i.e., Silverlight or Flex apps. If u want to get started with Silverlight, just go through basics. Tim Heuer is maintaining very good site on Silverlight - http://timheuer.com/blog/articles/getting-started-with-silverlight-development.aspx . So get started with basics first and then good design patterns and then building cool apps. Enjoy coding dude!!!!!!!


Thanks sathishinfotech,
Staying with asp.net is not an option for reasons that would take too long to explain for my purposes.
 I do fully expect to create an n-tiered approach from here on out, I guess my big question here is should I concentrate on using RIA Services from the get go or should I just use WCF Services until I get some development time under my belt? I don't have any real experience with either, just want to keep things a  simple as I can to begin with.
Senior Software Engineer
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview


Thanks, I will start with wcf and go from there, that is what  I was leanining towards to begin with.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.