Using Silverlight with C#?

I would like to get into programming with C# and Silverlight. I have read up a lot on WPF and like it a lot (from my narrow viewpoint)

Here is the question I have: if I understand WPF principles correctly, then I can seperate UI from logic.

I also can seperate logic from animation in my app (using Silverlight for animation, C# for logic)

Am I correct in this understanding?

Right now I am looking through some tutorials on Silverlight but I am asking for some pointers on how to make these all talk to one another. In my WPF app, ho开发者_如何学JAVAw can I use Silverlight to do animations?

If anyone has a good book or resource, I would really like to read it. Thanks for any help :)

Tools I have are: Visual Studio 2010 and Expression Studio 3 (I can get 4 and install the trial if I am supposed to use it instead of version 3)

---

There is a slight misconception here.

You wouldn't use Silverlight within a WPF application. It's really one or the other - Silverlight is an alternative platform to WPF.

If you're using WPF, you can use WPF for all of the animation. If you want to run within a browser, and/or have the deployment advantages of silverlight (cross-platform, simple deployment, etc), then target Silverlight. Silverlight development is similar to WPF development (many of the concepts are identical), but it's a lighter-weight platform which is sort of like WPF minus some features (with some extras thrown in, too).

---

Check www.silverlight.net there are lot of nice video tutorial.

---

Silverlight is the browser-based implementation of XAML and WPF technology. It represents a subset of the capabilities of WPF. So you can accomplish everything you need for a desktop app just using WPF. The experience you gain will translate to Silverlight development when you need to create browser-based applications.

---

Yeah you need to decide between Silverlight or WPF. For heavy Windows graphics or a GUI Client, I'd pick WPF. If you're looking for more of a web application. I'd go with Silverlight because of the difficulty of configuring WPF XBAP applications. I'd probably try to writing it in silverlight and then if I ran into something I couldn't do in silverlight, convert it over to wpf to go from there due to silverlight being lighter weight and cross platform.