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

Drop MSBuild, use dotnet build instead #1441

Merged
merged 2 commits into from
Sep 10, 2018

Conversation

thomaslevesque
Copy link
Member

As discussed with @adamralph, not sure where/when it was.
We no longer need to call MSBuild explicitly, so we don't need VSWhere anymore.

@blairconrad
Copy link
Member

blairconrad commented Sep 9, 2018

It's beautiful, @thomaslevesque. Thanks.

Confession time: I didn't completely follow when last we talked about the build prerequisites. It seems that we now don't need VS or MSBuild, but you were concerned about some other extensions or plugins or something that I don't know what they are. Are you happy with how_to_build.md as it is?

@thomaslevesque
Copy link
Member Author

It seems that we now don't need VS or MSBuild

I think we don't. But I'd like to check, first. I'll create a clean VM in Azure to make sure.

but you were concerned about some other extensions or plugins or something that I don't know what they are.

I don't remember what it might be.

Are you happy with how_to_build.md as it is?

No, I should update it. We might want to state clearly that it only works on Windows (because of ILMerge). It was implied by the VS requirement, but if that requirement is gone we should be more explicit. Currently it's a little understated:

At the time of writing the build is only confirmed to work on Windows using the Microsoft .NET framework.

Copy link
Contributor

@adamralph adamralph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@thomaslevesque
Copy link
Member Author

I think we don't. But I'd like to check, first. I'll create a clean VM in Azure to make sure.

OK, so Visual Studio itself isn't required, but we still need

  • .NET 4.6.1 Developer Pack (available from this page)
  • .NET 4.5 Developer Pack (NOT available as a standalone download, can be installed as part of the Visual Studio Build Tools, available from this page, in the "Tools for Visual Studio 2017 section)

So I think the easiest way to describe the requirements is to say that we need VS2017 or at least the VS Build Tools.

@@ -16,9 +16,7 @@ Ensure that the following are installed:

1. .NET 3.5, required by ILMerge

1. .NET framework 4.6.1 or later
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is implied by VS2017 (you can't have VS2017 without having net461 or later)

@blairconrad blairconrad merged commit 5dd048a into FakeItEasy:develop Sep 10, 2018
@blairconrad
Copy link
Member

I do love me some deleted lines. Thanks, @thomaslevesque!

@blairconrad blairconrad added this to the vNext milestone Sep 10, 2018
@thomaslevesque thomaslevesque deleted the use-dotnet-build branch September 10, 2018 08:01
@thomaslevesque
Copy link
Member Author

Thanks for the merge!

@blairconrad
Copy link
Member

This change has been released as part of FakeItEasy 4.9.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants