For starters, I'd suggest creating a test WinForms project, and a test WPF project. Then add a button and a textbox onto each of the forms and compare the "Designer Generated Code" in the WinForms app to the XAML in the WPF app.
Then you can double-click on the button in the designer window in both projects, and VS will create an OnClick handler for your button in WinForms and in WPF. This will allow you can compare the event handling features of both platforms.
Another common problem we run into when we first delve into WPF is this one:
XAML - get user control position relative to whole window as binding property
You'll learn really fast that there are a lot of simple things, like location, that we are used to doing in WinForms, but that are no longer available to us in WPF.
Apart from this, I'll just add that the biggest learning curve with WPF is the fact that the design sequence is completely reversed from what we are used to. In WPF you are expected to created all of the inner workings of your application first, and then bind that code to the user interface second. This will help keep you from coding yourself into a corner like you mentioned, more than almost anything else.