This document discusses project files and MSBuild. It explains that project files are MSBuild files that define properties, items, imports and targets. It compares legacy project files to SDK-style project files. It also discusses how MSBuild works by parsing the project file and evaluating properties, items, imports and targets. Finally, it recommends using build logging to see how MSBuild evaluates the project file.
Everything You Should Know About Project Files and MSBuild
1. Things (I think) you
should know
about project files and MSBuildDavid Wengier
Developer - .NET Project System
Microsoft
@davidwengier twitch.tv/davidwengier
21. @davidwengier twitch.tv/davidwengier
In summary:
• Project files are MSBuild files
• Project files are code
• Code reuse (Import)
• Separation of concerns (Import, Include vs Update)
• Order is important
• Use /pp or /bl to see what is going on
• Stuff we didn’t cover:
• Function calls (Tasks)
• Variables (properties)
• Conditionals (condition)