Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Git command formatting characters in msbuild are interpreted incorrectly

Post

Git command formatting characters in msbuild are interpreted incorrectly

+2
−0

I wish to add a property with the date of the current Git commit to the assembly info.

From my .csproj:

<Exec Command="git -C &quot;$(ProjectDir).&quot; log -1 --pretty=format:%ad"
	  ConsoleToMSBuild="true"
	  Condition="'$(GitCommitDate)' == ''">
	<Output TaskParameter="ConsoleOutput" PropertyName="GitCommitDate" />
</Exec>

Build output interpretation: git -C "<project directory>\." log -1 --pretty=format:-­

Output: -

Using raw format:

<Exec Command="git -C &quot;$(ProjectDir).&quot; log -1 --pretty=format:%aD"
	  ConsoleToMSBuild="true"
	  Condition="'$(GitCommitDate)' == ''">
	<Output TaskParameter="ConsoleOutput" PropertyName="GitCommitDate" />
</Exec>

Build output interpretation: git -C "<project directory>\." log -1 --pretty=format:­-

Output: -

Doubling % characters to escape them:

<Exec Command="git -C &quot;$(ProjectDir).&quot; log -1 --pretty=format:%%aD"
	  ConsoleToMSBuild="true"
	  Condition="'$(GitCommitDate)' == ''">
	<Output TaskParameter="ConsoleOutput" PropertyName="GitCommitDate" />
</Exec>

Build output interpretation: git -C "<project directory>\." log -1 --pretty=format:%-­

Output: -

This attempt worked, but it gets different details from those I want:

<Exec Command="git -C &quot;$(ProjectDir).&quot; log -1 --pretty=format:&quot;%%H %%cI&quot;"
	  ConsoleToMSBuild="true"
	  Condition="'$(GitCommitDate)' == ''">
	<Output TaskParameter="ConsoleOutput" PropertyName="GitCommitDate" />
</Exec>

Build output interpretation: git -C "<project directory>\." log -1 --pretty=format:"%%H %%cI"

Output: 2594b984b59b061dd714ed6a88fbee2907b30a05 2024-02-14T12:33:49-06:00

So I tried adding quotes to my original attempt:

<Exec Command="git -C &quot;$(ProjectDir).&quot; log -1 --pretty=format:&quot;%%aD&quot;"
	  ConsoleToMSBuild="true"
	  Condition="'$(GitCommitDate)' == ''">
	<Output TaskParameter="ConsoleOutput" PropertyName="GitCommitDate" />
</Exec>

Build output interpretation: git -C "<project directory>\ManagementConsole\." log -1 --pretty=format:"%­"

Output: -

What am I doing wrong?

What details am I missing that would help solve the question?

(I know that git show would be easier, but it failed the build with an exit code 128, which I figured would be more difficult to solve without further details.)

The - characters in the output and at the end of "build output interpretation" is added manually because I could not copy and paste it from my build output. I do not know why, but I thought that might be a clue.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

IMO this is a specific, concrete problem suitable for a Q&A on the main site. Discussions is for opin... (2 comments)
IMO this is a specific, concrete problem suitable for a Q&A on the main site. Discussions is for opin...
Kevin Krumwiede‭ wrote 4 months ago

IMO this is a specific, concrete problem suitable for a Q&A on the main site. Discussions is for opinion-based wisdom.

LyndonGingerich‭ wrote 4 months ago

Pardon, but I don't understand. Isn't this Q&A? It's under the Q&A tab.