-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSBuild All The Things #117
Comments
Should we do this in stages? First would be build with assembly versions. |
Extracting the steps out one-by-one seems like a reasonable approach. Getting my dev environment up to date now so I can ensure things aren't breaking along the way... |
On hold, waiting for @shiftkey to confirm if this is required. |
As the maintainer of a suite of custom rake tasks for .NET projects, I have to speak out against this request! I'd say it's a lot harder to maintain and contribute to msbuild scripts than ruby scripts. With the chocolatey package manager, you can have Ruby in one step
and you can be ready to run rake in a few more
And now you're all setup for any project that has rake builds |
I can propose an even better option than pure MSBuild - https://github.com/fsharp/FAKE We're using it in Octokit.net and it lets you write really simple scripts https://github.com/octokit/octokit.net/blob/master/build.fsx Let me put together a start on this and see how everyone feels |
Obsoleted by #138 |
As a contributor
I want to be able to build NSubstitute without needing ruby + gems
So that I can have a simpler dev environment
While it would be nice to drop the whole ruby dependency from the build, it's going to be easier to do this gradually by switching functions across from ruby into MSBuild scripts.
Tasks:
version_assemblies
in MSBuild and replace ruby implementationget_build_version
in MSBuild and replace ruby implementationtest
,specs
,pending
andtest_examples
in MSBuild and replace ruby implementationpackage
as MSBuild script and replace ruby implementationnuget
as MSBuild script and replace ruby implementationTODO: can we can drop the Jekyll dependency?
The text was updated successfully, but these errors were encountered: