Lead Product Evangelist @Kentico, Founding partner @craftbrewingbiz. love to learn / teach web dev & software engineering, collecting vinyl records, mowing my lawn, craft 🍺
Something I only realized after years of doing C#/.NET development was that C#/.NET 'projects' are mono-repo oriented. Multiple Projects, with a dependency hierarchy all contained within a single Solution.
MSBuild understands the dependencies and will only re-build the Projects that have changed files or updated dependencies.
A single Solution can create multiple artifacts (NuGet packages, deployable web applications, console applications).
This is something the JavaScript world has only recently been adopting with tools like Lerna and NX and C#/.NET has had it for decades! We get all this goodness for free!
Something I only realized after years of doing C#/.NET development was that C#/.NET 'projects' are mono-repo oriented. Multiple Projects, with a dependency hierarchy all contained within a single Solution.
MSBuild understands the dependencies and will only re-build the Projects that have changed files or updated dependencies.
A single Solution can create multiple artifacts (NuGet packages, deployable web applications, console applications).
This is something the JavaScript world has only recently been adopting with tools like Lerna and NX and C#/.NET has had it for decades! We get all this goodness for free!
FritzsCoolApplication.Test -> FritzsCoolApplication.Test*s*