Building in Visual Studio

[maryamariyan]

From @terrajobst on Mar 26

On a clean machine, opening the solution file and building in VS fails as the Tools folder doesn't exist. Just running init-tools.cmd doesn't fix it either as it now fails with malformed AssemblyInfo.cs files.
I'm still trying to get build working from the command line (where I get mostly actionable error messages, like Install CMake) this feels like the sort of thing that discourages contributors quickly. Ideally, you should be able to clone the repo, open the solution in VS, and building immediately.
Thoughts?

[maryamariyan]

From @eerhardt on Mar 26

The error message you got told you to run build from the root of the repo first, right?
This is the same experience as dotnet/corefx

[maryamariyan]

From @terrajobst on Mar 26

The error message you got told you to run build from the root of the repo first, right?

Ah yes. Here is the error:

The tools directory [P:\machinelearning\Tools/] does not exist. Please run build in the root of the repo to ensure the tools are installed before attempting to build an individual project.	

I missed the "please run build in the root". So I take it back -- the error we provide is actually actionable, provided the person can read properly :-)

This is the same experience as dotnet/corefx

Yes, but in corefx it's mostly because for us there isn't necessarily a good way to build from the IDE. Other projects (like Roslyn and ASP.NET) allow for developing/building inside the IDE. I don't see why ML.NET has to be a CLI only build experience -- they sit on top of the platform.

[maryamariyan]

From @eerhardt

Other projects (like Roslyn and ASP.NET) allow for developing/building inside the IDE.

These projects don't contain native code. And even harder, building native code cross platform.

I don't see why ML.NET has to be a CLI only build experience

It isn't a CLI only build experience. It is a "build from the CLI first" experience. After you build once from the command-line, you can then use the IDE until your heart is content.

[maryamariyan]

From @terrajobst

These projects don't contain native code. And even harder, building native code cross platform.

That's fair.

It isn't a CLI only build experience. It is a "build from the CLI first" experience.

I see. I got the impression that you always have to run the build.cmd from the command line. For the initial prep, do I have to run build.cmd or should it be sufficient to just run init-tools.cmd? If not, maybe we should move init-tools.cmd out of the root.

[maryamariyan]

@eerhardt can this issue be closed?

[danmoseley]

@maryamariyan once build.cmd has run from the root, is the VS experience on csproj and .vcxproj satisfactory? If so, yes. If not, please update the issue with the problem.

[eerhardt]

When you just open the .sln in Visual Studio and try to build with a clean repo, you get the error:

Severity	Code	Description	Project	File	Line	Suppression State
Error		The tools directory [F:\git\machinelearning\Tools/] does not exist. Please run build in the root of the repo to ensure the tools are installed before attempting to build an individual project.	Microsoft.ML.Core	F:\git\machinelearning\Directory.Build.targets	4	

Once you run build.cmd in the root of the repo, you are able to build and test in VS as expected.

Closing.

[jstallm]

In order to build in the Visual Studio IDE, need to call “build.cmd” from the command line first.

[DevLob-zz]

In order to build in the Visual Studio IDE, need to call “build.cmd” from the command line first.

i do that but still can't build the solution

[eerhardt]

i do that but still can't build the solution

What error are you getting?

[DevLob-zz]

i do that but still can't build the solution

What error are you getting?

[DevLob-zz]

[image: image.png]

…

On Thu, 22 Nov 2018 at 19:00, Eric Erhardt ***@***.***> wrote: i do that but still can't build the solution What error are you getting? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEzeLCdC-OtImugDrZye5CRRom2aZ8q7ks5uxtglgaJpZM4TzZ37> .

-- *Phone Number : 01110024783* *Skype : SkipCoder* *FB : http://www.facebook.com <http://www.facebook.com/NOBDEV>*

[DevLob-zz]

[eerhardt]

The last 2 errors about not supporting .NET Core 3.0 shouldn't block you from building. They can be ignored.

The first screen shot you posted with 1000 errors - are you still getting those?

What does the "Output" window say when you build?