Vista - File.xaml and File.xaml.cs are atomically checked out/in from sourcesafe

Hi,

When I create a WinFX project in Visual Studio, it automatically
combines any XAML file with its corresponding .xaml.cs code-behind file,
like so:

<Compile Include="Window1.xaml.cs">
<DependentUpon>Window1.xaml</DependentUpon>
<SubType>Code</SubType>
</Compile>

And in the IDE, the code-behind file shows up as a "child" of the xaml
file in the Solution Explorer.

This is generally a good thing, but not quite so when it comes down to
checking in/out to SourceSafe only one file of this pair.

First, there is no way to check out the .xaml.cs file via the context
menu (nor the top-level source control menu). I need to start editing
the file for VS to prompt me to check it out.

Then, it doesn't check out only the .xaml.cs file, but the .xaml file as
well!

Also, if I modify both the .xaml and .xaml.cs files and want to undo
check-out only one of these files, it undoes BOTH files!

This behavior goes against the advertised development process that a
designer can work in the XAML file while a developer writes the code in
the .cs file...

Should this be considered a bug or simply an undesirable side effect of
the way VS/SourceSafe handle <DependentUpon> files?

As a workaround, can I safely break the <DependentUpon> relationship
manually in the csproj file?

Thanks!

Pascal

I've forwarded your feedback. Also, yes, you can safely break the
<DependentUpon> association without sacrificing application functionality.

--
Ashish Shetty [MSFT]
Program Manager, Windows Presentation Foundation (Avalon)
Blog: http://nerddawg.blogspot.com



"Pascal Bourque" <bourquep@xceedsoft.com> wrote in message
news:O0MLOg7YGHA.3400@TK2MSFTNGP02.phx.gbl...
> Hi,
>
> When I create a WinFX project in Visual Studio, it automatically combines
> any XAML file with its corresponding .xaml.cs code-behind file, like so:
>
> <Compile Include="Window1.xaml.cs">
> <DependentUpon>Window1.xaml</DependentUpon>
> <SubType>Code</SubType>
> </Compile>
>
> And in the IDE, the code-behind file shows up as a "child" of the xaml
> file in the Solution Explorer.
>
> This is generally a good thing, but not quite so when it comes down to
> checking in/out to SourceSafe only one file of this pair.
>
> First, there is no way to check out the .xaml.cs file via the context menu
> (nor the top-level source control menu). I need to start editing the file
> for VS to prompt me to check it out.
>
> Then, it doesn't check out only the .xaml.cs file, but the .xaml file as
> well!
>
> Also, if I modify both the .xaml and .xaml.cs files and want to undo
> check-out only one of these files, it undoes BOTH files!
>
> This behavior goes against the advertised development process that a
> designer can work in the XAML file while a developer writes the code in
> the .cs file...
>
> Should this be considered a bug or simply an undesirable side effect of
> the way VS/SourceSafe handle <DependentUpon> files?
>
> As a workaround, can I safely break the <DependentUpon> relationship
> manually in the csproj file?
>
> Thanks!
>
> Pascal