search

OmniSharp / Kulture

Sublime extension for ASP.NET vNext
Other
79 stars 12 forks source link

"Run K Commands" does nothing #8

Open afortaleza opened 10 years ago

afortaleza commented 10 years ago

This is a clone from https://github.com/ligershark/Kulture/issues/22

I am having the same issue, I'm following the tutorial at http://www.asp.net/vnext/overview/aspnet-vnext/create-a-web-api-with-mvc-6 using Sublime. The tutorial puts the project.json file into the src/ subfolder and when I hit F5 (Run K Commands) it does nothing with the message: "project,json not found with sublime project. looking based on file being edited".

The symptons follow the source thread referenced above.

spboyer commented 10 years ago

@afortaleza open any file within the project inside Sublime and attempt again. Kulture uses the the open file to determine the directory to locate the project.json file in.

cmatskas commented 9 years ago

Yes, still an issue with the latest install. Please advise if there is a work around as it is quite a pain :(

sayedihashimi commented 9 years ago

@cmatskas @afortaleza did you try what @spboyer suggested above?

cmatskas commented 9 years ago

Should we make it clear for other people's sanity that creating an ASP.NET 5 in Visual Studio and then copying it to OSx or Linux doesn't work in the expected way? There are some hoops to jump, for now, to allow Omnisharp to work with the VS solution file structure.

juzzbott commented 9 years ago

I too am seeing this issue, except the status bar shows: found project.json in project directory: [/path/to/project.json]

After this message appears in status bar, nothing happens, and after a few seconds the message disappears again.

I've installed Kulture both using Package Control and manually. I'm currently using beta3, which has updated the .kre directory in my home directory to .k, so I've updated the Kulture/build.sh file accordingly (and I'll send through a PR soon).

Currently using Linux Mint 17 with Sublime Text 3.

juzzbott commented 9 years ago

Actually, disregard this issue.

It turns out my project.json file had a sneaky trailing , after one of the dependencies. Frustrating.