Skip to content

Conversation

@cdmihai
Copy link
Contributor

@cdmihai cdmihai commented May 19, 2018

Useful if you know exactly where MSBuild is, for example if you want to point it to the msbuild repo bootstrap directory.

/// path.
/// </summary>
/// <param name="msbuildPath"></param>
public static void RegisterMSbuildPath(string msbuildPath)
Copy link
Member

Choose a reason for hiding this comment

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

Should the casing be RegisterMSBuildPath with a capital B? That matches other APIs here.

Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

Nice.

Can you:

  • "Fixes #21"
  • Add a sample showing how to use this, ideally as a fallback

?

/// Add assembly resolution for Microsoft.Build core dlls in the current AppDomain from the specified
/// path.
/// </summary>
/// <param name="msbuildPath"></param>
Copy link
Member

Choose a reason for hiding this comment

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

Doc what this is: (absolute?) path to the folder that contains Microsoft.Build.dll?

MSBuildLocator.RegisterInstance(instanceToUse);
if (msbuildDeploymentToUse.VSInstance != null)
{
Console.WriteLine($"Using MSBuild deployment from VS Instance: {msbuildDeploymentToUse.VSInstance.Name} - {msbuildDeploymentToUse.VSInstance.Version}");
Copy link
Member

Choose a reason for hiding this comment

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

I would not use the word "deployment" here. Just say Using MSBuild from...

@cdmihai cdmihai merged commit a860e02 into microsoft:master May 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants