Home/ Questions/Q 5838123
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T11:26:04+00:00

I have one build project with target build <Target Name=Build> <Message Text=Version : $(FullVersionNr)

  • 0

I have one build project with target build 

<Target Name="Build">
    <Message Text="Version : $(FullVersionNr)"  />
    <MSBuild Projects="@(WebProj)"  Properties="WebProjectOutputDir=$(SitePublishPath);OutDir=$(SitePublishPath1);Configuration=$(Configuration)" />      
<Message Text="Version  : $(FullVersionNr)"  />

and during build I set $(FullVersionNr) to accurate assembly number and it’s not this nr at the end

I even declared $(FullVersionNr) prop in another file

<Import Project="Common.proj"/>

and it’s not getting out.

It’s only one way communication from parent to child project, and I want it to be bi-directional

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This MSDN article should give you a few ideas on how to achieve this: MSBuild Properties. More specifically, this blog post should answer your scope questions: Scope of properties and item in an MSBuild script. Be sure to read the summary at the end.

    So if you are batching over multiple projects, it is possible that the local contexts have not been merged back into the global context when you access the $(FullVersionNr) for the second time, or that one local context has overwritten another (i.e. two child projects, the first updates the build, but the second doesn’t).

    One possible solution for you is to use registry properties as described in the MSDN article, and only write the property when its value is updated.

    • 0