You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
Create a folder
create a project.json file that doesn't match the json spec (say just put hello world)
kpm build
Result - Error (expected) see below, but no physical path to where it happens, so when kpm build runs inside a script you don't get enough input to where things happened.
Would like to get the full physical path to the project.json file (if available)
Error example
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while pars
ing value: E. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonTextReader.ReadInternal()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader)
at Newtonsoft.Json.Linq.JObject.Parse(String json)
at Microsoft.Framework.Runtime.Project.GetProject(String json, String project
Name, String projectPath)
at Microsoft.Framework.Runtime.Project.TryGetProject(String path, Project& pr
oject)
at Microsoft.Framework.PackageManager.BuildManager.Build()
at Microsoft.Framework.PackageManager.Program.<>c__DisplayClass3.<Main>b__12(
)
at Microsoft.Framework.Runtime.Common.CommandLine.CommandLineApplication.Exec
ute(String[] args)
at Microsoft.Framework.PackageManager.Program.Main(String[] args)
The text was updated successfully, but these errors were encountered:
Microsoft uses Newtonsoft.Json in ASP.NET project systems as well as bringing the JSON support in VS (for JSON AST and indentation too I believe).
As you can see here: Microsoft.Framework.Runtime/project.json#L8, KRuntime is using 6.0.4 version (which, btw, is penultimate version and needs to be updated to 6.0.5?), while VS 2013 uses old 4.x version.
Therefore, reporting this issue to Json.NET's issue tracker (w.r.t this issue) might yield better results; as this kind of context would only be available to Newtonsoft.Json's parser.
Repro steps
Create a folder
create a
project.json
file that doesn't match the json spec (say just put hello world)kpm build
Result - Error (expected) see below, but no physical path to where it happens, so when kpm build runs inside a script you don't get enough input to where things happened.
Would like to get the full physical path to the project.json file (if available)
Error example
The text was updated successfully, but these errors were encountered: