VS2013 MSBuild error that does not occur with .Net V4.0 Framework.

Question

4.00/5 (1 vote)

See more:

I have VS2013 installed on a "clean" Windows 7 VM. Also installed in the system is the V4.0 .Net Framework. The following is a sample build script that demonstrates a problem I am having with a much larger script

XML

<!-- *****************************-->
     <!DOCTYPE Project [
       <!ENTITY e_DefaultValue "Hello World">
     ]>

  <Project DefaultTargets="Display" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
      <MsgStr>&e_DefaultValue;</MsgStr>
    </PropertyGroup>

    <Target Name="Display">
      <Message Text='$(MsgStr)' />
    </Target>

 </Project>

If I attempt to run the snippet using the VS2013 MSBuild executable, I get the following error:

The project file could not be loaded. Reference to undeclared entity 'e_DefaultValue'.

If I run it with the .Net v4.0 Framework version, it displays the message correctly.

Is this an issue where the VS2013 MSBuild needs something else defined?

Posted 26-Aug-14 2:54am

MSBuildMan

Updated 26-Aug-14 4:09am

Richard MacCutchan

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

MSBuildMan · Answer 1 · 2014-10-16T03:12:00

Microsoft has changed the way MSBuild handles DTD processing. Will have to rewrite scripts. Here's their response:

https://connect.microsoft.com/VisualStudio/feedback/details/981375/wc-10-17-vs2013-msbuild-error-that-does-not-occur-with-net-v4-0-framework

Bottom line: Remove DOCTYPE section, create a PropertyGroup section and populate it with the values you had in the DOCTYPE section.