Skip to content
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

Closed
9 tasks
shiftkey opened this issue Jul 17, 2013 · 6 comments
Closed
9 tasks

MSBuild All The Things #117

shiftkey opened this issue Jul 17, 2013 · 6 comments
Labels
on hold Not actively being worked on, pending some additional information or dependency.

Comments

@shiftkey
Copy link
Contributor

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:

  • implement version_assemblies in MSBuild and replace ruby implementation
  • implement get_build_version in MSBuild and replace ruby implementation
  • implement test, specs, pending and test_examples in MSBuild and replace ruby implementation
  • implement package as MSBuild script and replace ruby implementation
  • implement nuget as MSBuild script and replace ruby implementation
  • implement 'zip` as MSbuild script and replace ruby implementation
  • test that build scripts can be run using Mono
  • .net exe for extracting tests from code samples (currently in ruby) (DT)
  • ???

TODO: can we can drop the Jekyll dependency?

@dtchepak
Copy link
Member

Should we do this in stages? First would be build with assembly versions.
We can incorporate test runs later, and optionally doc generation after that. Doc generation is pretty heavily reliant on ruby and jekyll, so that may not be worth the effort in converting.

@shiftkey
Copy link
Contributor Author

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...

@dtchepak
Copy link
Member

On hold, waiting for @shiftkey to confirm if this is required.

@AnthonyMastrean
Copy link

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

> cinst ruby

and you can be ready to run rake in a few more

> gem install bundler
> bundle 

And now you're all setup for any project that has rake builds

@shiftkey
Copy link
Contributor Author

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

@dtchepak
Copy link
Member

dtchepak commented Nov 5, 2014

Obsoleted by #138

@dtchepak dtchepak closed this as completed Nov 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on hold Not actively being worked on, pending some additional information or dependency.
Projects
None yet
Development

No branches or pull requests

3 participants