build command results in 404 from server

[aggieben]

I'm new to OmniSharp, so I don't know much yet about how to do a lot of troubleshooting. After having failed to get a released version to work with DNX/project.json, I got the sources for the latest master (after the merge of the roslyn stuff) and tried that. It kinda-sorta works, and I don't have all the red squigglies like before, but building doesn't work. The following is produced in the OmniSharp output pane:

What did I do wrong?

Output of apm list:

C:\Users\Administrator\.atom\packages (7)
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[ctolkien]

@aggieben , bits from master will work with dnx/project.json based builds. However omnisharp-roslyn is still being fleshed out:

This issue tracks current support:
OmniSharp/omnisharp-roslyn#29

Note that /buildcommand is not supported yet!

[aggieben]

Perfect, thanks!

[nosami]

Also - You don't really need an explicit build command with Asp.Net 5 projects. Edit, then run.

[aggieben]

Not all DNX projects are ASP.NET 5 ;-) Also, explicit building has the benefit of explicit diagnostic spew and error messages.

[nosami]

Still.... the same applies for an Asp.Net 5 console app ;)

[davidfowl]

You can still build. We should wire up the DTH build here.

[RexMiller]

I am getting the same 404 response trying to build a .csproj project in a solution with a .sln file. I'm using version 3.0, on Windows. Is it supposed to be able to build sln/csproj projects?

The server seems to recognize the project in the last two lines below:

But it seems suspect that on the second line it seems to be picking the dnx runtime that I also have installed on the machine. Should that be? Not sure how to specify the runtime. Building results in the 404:

The packages I have installed are:

C:\Users\currentuser\.atom\packages (6)
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

I'm sorry if I'm totally missing the point here. Very much liking Omnisharp though.