Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a perfect scenario to use <a href="http://msdn.microsoft.com/en-us/library/ms171473%28v=VS.100%29.aspx" rel="nofollow">Batching</a>. </p> <p>You'll need to create custom <a href="http://msdn.microsoft.com/en-us/library/ms171453%28v=VS.100%29.aspx" rel="nofollow">Items</a> with the appropriate metadata and then create a single Target to reference the new Items.</p> <p>You can wrap each Item in it's own target like so:</p> <pre><code>&lt;Target Name="Tgt1"&gt; &lt;ItemGroup&gt; &lt;BuildConfig Include="Tgt1"&gt; &lt;Conf1&gt;Twiddle&lt;/Conf1&gt; &lt;Conf2&gt;Thing&lt;/Conf2&gt; &lt;/BuildConfig&gt; &lt;/ItemGroup&gt; &lt;/Target&gt; &lt;Target Name="Tgt2"&gt; &lt;ItemGroup&gt; &lt;BuildConfig Include="Tgt2"&gt; &lt;Conf1&gt;Twaddle&lt;/Conf1&gt; &lt;Conf2&gt;Thing 1&lt;/Conf2&gt; &lt;/BuildConfig&gt; &lt;/ItemGroup&gt; &lt;/Target&gt; &lt;Target Name="Tgt3"&gt; &lt;ItemGroup&gt; &lt;BuildConfig Include="Tgt3"&gt; &lt;Conf1&gt;Tulip&lt;/Conf1&gt; &lt;Conf2&gt;Thing 2&lt;/Conf2&gt; &lt;/BuildConfig&gt; &lt;/ItemGroup&gt; &lt;/Target&gt; </code></pre> <p>You'll then need a core target to call that will perform all of the work like so:</p> <pre><code>&lt;Target Name="CoreBuild" Outputs="%(BuildConfig.Identity)"&gt; &lt;Message Text="Name : %(BuildConfig.Identity)" /&gt; &lt;Message Text="Conf1 : %(BuildConfig.Conf1)" /&gt; &lt;Message Text="Conf2 : %(BuildConfig.Conf2)" /&gt; &lt;/Target&gt; </code></pre> <p>Adding <code>Outputs="%(BuildConfig.Identity)"</code> to the target will make sure you batch at the target level instead of at the task level.</p> <p>You can execute this from msbuild with passing arbitrary combinations of the targets as long as the last target is your core target. For example executing this command <code>MSBuild.exe test.msbulid /t:Tgt1,Tgt3,CoreBuild</code> will give you the following output:</p> <pre><code>Name : Tgt1 Conf1 : Twiddle Conf2 : Thing Name : Tgt3 Conf1 : Tulip Conf2 : Thing 2 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to avoid repetition in MSBuild?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAaron Carlson
    1. USAaron Carlson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to avoid repetition in MSBuild?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBut this means I can no longer build just one or just two of them, correct? Any way to preserve that ability?
      singulars
      1. PO
      1. USRoman Starkov
    2. COYou can put conditions on the Items. I'll update the answer with an example.
      singulars
      1. PO
      1. USAaron Carlson
    3. COThank you, though I can see the conditions becoming quite tricky if I want to include any _two_ builds. I am currently leaning towards keeping the repetition because I'd like to keep the ability to specify `/t:Tgt1,Tgt2` - the real script actually has a few more targets, and we're relying on the ability to pick arbitrary subsets like this.
      singulars
      1. PO
      1. USRoman Starkov
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload