This weekend I began working on my first project. I'm taking my DTBanking/MiniMint app that I use in my Intro to jQuery talk and converting it to a Silverlight4 app. Eventually I'm going to be taking the data and taking it offline; not sure which Silverlight Offline DB I'll use (probably either HSQL or SQLite --If I do this I won't be storing in Isolated storage but will use a fully offline app with the improved permissions which means I'll be doing some clean up on the aforementioned samples and will publish if I come up with something decent).
Some things I've learned
I know more than I thought. Seriously. I do a lot of research keeping myself up to date, and I think many of my lack of confidence in myself was really lack of experience. I jumped right in.
I think the other thing is that the mentality that I have when building an Ajax/Web 2.0 app carries over. When creating solutions for either, I find myself mapping out the service model first then moving toward coding up the UI to take advantage of my service model. I think oftentimes in terms of the amount of data being pushed down or rather I think about how I can avoid sending gobs of data all at onces.
Linq To SQL + the Repository pattern is a timesaver!
Linq To SQL + a Repository pattern (as taught by the ASP.NET MVC Team) really can help get you cut over quickly... I was able to build an ADO.NET Data Service (aka WCF Data Service... still pronounced "Astoria service") from my Linq to SQL model and then change the DBContext in the repository to using a Astoria Service context (will post code soon on this in a separate post)