An open source re-implementation of RollerCoaster Tycoon 2
-
Updated
Oct 16, 2020 - C++
{{ message }}
An open source re-implementation of RollerCoaster Tycoon 2
A utility to perform design-time builds of .NET projects without having to think too hard about it.
Converts C# classes to TypeScript interfaces (and many more) within project build. 0-dependency, minimal, gluten-free
Find all of the resources you might need to try out code presented in the Student Zone at Build 2020 for yourself!
Invoke-MsBuild PowerShell module to make building projects and solutions with MsBuild.exe easy.
Gradle plugin for msbuild execution, supports C# project files for now
NsDepCop is a static code analysis tool that helps to enforce namespace dependency rules in C# projects. No more unplanned or unnoticed dependencies in your system.
A Roslyn based C# source generation framework
MSBuild 15.0 Toolset integration for multiple LLVM (From v5 to v8)
Builds observables from events.
TeamCity plugin for .NET Core projects
An API to locate MSBuild assemblies from an installed Visual Studio location. Use this to ensure that calling the MSBuild API will use the same toolset that a build from Visual Studio or msbuild.exe would.
A GitHub Action to facilitate configuring MSBuild in the workflow PATH for building .NET Framework applications.
gulp-msbuild has moved to https://github.com/fluffynuts/gulp-msbuild.
MSBuild integration for the Yarn package manager.
MSBuild task for compiling Visual Studio C/C++ projects (.vcxproj) with your choice of compiler on Linux or Windows or Mac!
A collection of scripts and utilities to support integrated development with external compiler and linker toolchains under Microsoft Visual Studio 2013+.
Add a description, image, and links to the msbuild topic page so that developers can more easily learn about it.
To associate your repository with the msbuild topic, visit your repo's landing page and select "manage topics."
We have several errors/warnings that have a URL in the text of the message. After #5488 (thanks, @jmezac!) we'll have a structured way to represent this that will eventually (dotnet/project-system#6335) be used in the Visual Studio UI.
We should use that!
Likely candidates: