Databases
StackOverflow2013
Postsdbo
POMS-Build BeforeBuild not firing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMS-Build BeforeBuild not firing
    primarykey
    data
    text
    <p>I'm customising a <code>.csproj</code> project to run some custom tasks before the main build. However, I can't get the tasks to execute at all. </p> <p>I uncommented the <code>&lt;Target Name="BeforeBuild" /&gt;</code> element in the <code>.csproj</code> file and added a simple Message task, but when I build, the message doesn't appear in my output, so it seems the task isn't running. So this fragment does not output the message;</p> <p><strong>Listing 1: No Message Appears</strong></p> <pre><code>&lt;Target Name="BeforeBuild"&gt; &lt;Message Text="About to build ORM layer" Importance="normal" /&gt; &lt;/Target&gt; </code></pre> <p>However, if I screw with some of the attributes, I can get the <code>.csproj</code> to fail to execute at all;</p> <p><strong>Listing 2: An MSBuild configuration error</strong></p> <pre><code>&lt;Target Name="BeforeBuild"&gt; &lt;Message Text="About to build ORM layer" XXImportance="normal" /&gt; &lt;/Target&gt; </code></pre> <p>Note the <code>XXImportance</code> attribute. The build error I get is</p> <pre><code>My.csproj(83,46): error MSB4064: The "XXImportance" parameter is not supported by the "Message" task. Verify the parameter exists on the task, and it is a settable public instance property. </code></pre> <p>This suggests that the XML is being parsed, that the <code>Message</code> class has been found, and that the class is being reflected over for the available properties. </p> <p>Why would the task not execute?</p> <p>I'm using the 3.5 framework.</p> <p><strong>UPDATE 1:</strong> On @Martin's advice, I tried to run MSBuild on the console, and got this error;</p> <pre><code>c:\path\to\my.csproj(74,11): error MSB4019: The imported project "C:\Microsoft.CSharp.targets" was not found. Confirm that the path in the &lt;Import&gt; declaration is correct, and that the file exists on disk. </code></pre> <p>Line 74 reads;</p> <pre><code>&lt;Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /&gt; </code></pre> <p><strong>UPDATE 2:</strong> I'm compiling in VS2008, which uses the C#3 compiler, but the project I'm compiling is a framework 2.0 project. When run from the command line (see UPDATE 1) the build seems to fail because there is a confusion as to where the <code>Microsoft.CSharp.targets</code> file is specified.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSteve Cooper
    1. USSteve Cooper
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMS-Build BeforeBuild not firing
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMS-Build BeforeBuild not firing
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMS-Build BeforeBuild not firing
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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