Hi, Viv.

>>>Looking at ExpressionBlend AFAICS there's currently no intrinsic support for source control.
>>>
>>>Am I correct?
>>>
>>>If so - any suggestions on how best to integrate ExpressionBlend with an existing VS2008 solution under source control ?
>>
>>By now, you should either use a standalone client for you source control program (like VSS, or Tortoise), or you have to use Visual Studio to check-out and check-in.
>>
>>Source control integration is one of the most requested features for Blend and we hope there would be at least basic support in the RTM (it is in Beta 2 now).
>
>Are you referring to Expression Blend 2? I looking at EB SP1 (1.0.2017.0) which I believe is the current release. I see a 'EB2 December Preview' available for download but no indication that it supports (or intends to support) source control integration.

Yes. I really recommend you this preview as it is much better and stable than the official current release.

>We're currently using a remote web connection between Visual Studio and VSS but AFAICS the web option would not be available using the VSS client and loading Visual Studio onto machines that only need EB is not exactly cost friendly....

If you don't have Visual Studio you can use the VSS client on a remote connection. Are you using VSS 2005?

>It does seem daft that source control is not integrated into a product whose sole raison d'etre is to work seamlessly with WPF...

It is, really, and that's why many of us keep claiming for it. We hope the next preview of version available will fix this hole. Even more now that they are talking so much about developers and designer integration...


Regards,