<p>The rich presentational capabilities of WPF and Silverlight mean developers like me will be working closely with graphic designers more often these days, as is the case in my next project.  </p>

<p>Does anyone out there have any tips and experience (from both points of view) on making this go more smoothly?  </p>

<p>For example, when I mentioned source control to a designer recently, I was quickly told you can't source control graphics, images etc, so it is a waste of time.  So I responded: ok but, what about XAML files in WPF/Silverlight?   </p>

<p>Scott Hanselman spoke about this topic in a <a href="http://www.hanselminutes.com/default.aspx?showID=138" rel="noreferrer">podcast</a>, but he focused more on the tools, while I'm more interested in the communication issues/aspects.</p>

This may be a bit off topic (I'm replying specifically to your question about source control and graphics), but you
can
put binary data (images etc.) into source control (and in my opinion in a lot of cases should) -- they just take up more disk space and you can't use a diff view to analyze what has changed in any meaningful way, but what you do gain is a history of commit messages documenting each revision, rollback ability and the ability to easily archive (
tagging a revision
in SVN terms) all files (be they visual assets, documentation, source code, whatever) belonging to a specific release/version together. It's also easier for your build system to just fetch everything required for building a specific version of your software from the source control.