El Bruno

Hello!

Visual Studio does an excellent job gathering files from most common projects. A WFP C project # groups XAML files and way XAML.CS for Panel Solution Explorer only see a grouped item.

What you see in this way, in the File system actually in Solution Explorer are several files.

This grouping of files (file nesting) is defined in the project file, and so far all happy. The following text is part of the project file and the MainWindow.xaml.cs element (line 14) has a dependency relationship with MainWindow.xaml (line 15)

   1: <ItemGroup>

   2:   <ApplicationDefinition Include="App.xaml">

   3:     <Generator>MSBuild:Compile</Generator>

   4:     <SubType>Designer</SubType>

   5:   </ApplicationDefinition>

   6:   <Compile Include="App.xaml.cs">

   7:     <DependentUpon>App.xaml</DependentUpon>

   8:     <SubType>Code</SubType>

   9:   </Compile>

  10:   <Page Include="MainWindow.xaml">

  11:     <Generator>MSBuild:Compile</Generator>

  12:     <SubType>Designer</SubType>

  13:   </Page>

  14:   <Compile Include="MainWindow.xaml.cs">

  15:     <DependentUpon>MainWindow.xaml</DependentUpon>

  16:     <SubType>Code</SubType>

  17:   </Compile>

  18: </ItemGroup>

If you ever “lose this partnership” the following extension is quite useful. This is common in the not so common, as LS project types, or if you do testing with IronPython. The following picture is worth a thousand words, no?

Returning to the previous example, the same now I can do things as useful as putting MainWindow.xaml as a dependency of App.Config

Download: http://visualstudiogallery.msdn.microsoft.com/3ebde8fb-26d8-4374-a0eb-1e4e2665070c

Saludos @ Home

El Bruno

Google