{"action":"created","issue":{"url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service/issues/602","repository_url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service","labels_url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service/issues/602/labels{/name}","comments_url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service/issues/602/comments","events_url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service/issues/602/events","html_url":"https://github.com/fsharp/FSharp.Compiler.Service/issues/602","id":163831968,"number":602,"title":"Move to MSBuild 14.0","user":{"login":"dsyme","id":7204669,"avatar_url":"https://avatars.githubusercontent.com/u/7204669?v=3","gravatar_id":"","url":"https://api.github.com/users/dsyme","html_url":"https://github.com/dsyme","followers_url":"https://api.github.com/users/dsyme/followers","following_url":"https://api.github.com/users/dsyme/following{/other_user}","gists_url":"https://api.github.com/users/dsyme/gists{/gist_id}","starred_url":"https://api.github.com/users/dsyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsyme/subscriptions","organizations_url":"https://api.github.com/users/dsyme/orgs","repos_url":"https://api.github.com/users/dsyme/repos","events_url":"https://api.github.com/users/dsyme/events{/privacy}","received_events_url":"https://api.github.com/users/dsyme/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-07-05T11:45:57Z","updated_at":"2016-07-05T21:57:37Z","closed_at":null,"body":"As reported elsewhere [MSBuild 12.0 in Visual Studio Update 3 is now giving strange errors for some F# project files](https://github.com/fsharp/FSharp.Compiler.Service/pull/601#issuecomment-230454923)/  This is causing our AppVeyor builds to fail.\r\n\r\nMy suggestion is that we move FSharp.Compiler.Service.ProjectCrackerTool.exe to use MSBuild 14.0\r\n\r\n@rneatherway Do you expect any problems with doing this?  It looks from your previous analysis that MSBuild 14.0 is reliably installed on all Mono systems.  But can we expect it to be installed on Windows systems, if Visual Studio is not installed?  Will this lead to renewed requests to package the MSBuild 14.0 binaries with FSharp.Compiler.Service project cracker, e.g. in a \"tools\" directory?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service/issues/comments/230615230","html_url":"https://github.com/fsharp/FSharp.Compiler.Service/issues/602#issuecomment-230615230","issue_url":"https://api.github.com/repos/fsharp/FSharp.Compiler.Service/issues/602","id":230615230,"user":{"login":"rneatherway","id":243995,"avatar_url":"https://avatars.githubusercontent.com/u/243995?v=3","gravatar_id":"","url":"https://api.github.com/users/rneatherway","html_url":"https://github.com/rneatherway","followers_url":"https://api.github.com/users/rneatherway/followers","following_url":"https://api.github.com/users/rneatherway/following{/other_user}","gists_url":"https://api.github.com/users/rneatherway/gists{/gist_id}","starred_url":"https://api.github.com/users/rneatherway/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rneatherway/subscriptions","organizations_url":"https://api.github.com/users/rneatherway/orgs","repos_url":"https://api.github.com/users/rneatherway/repos","events_url":"https://api.github.com/users/rneatherway/events{/privacy}","received_events_url":"https://api.github.com/users/rneatherway/received_events","type":"User","site_admin":false},"created_at":"2016-07-05T21:57:37Z","updated_at":"2016-07-05T21:57:37Z","body":"> Perhaps we could just override it to be back at \\Program Files or \\Program Files (x86) regardless of where the MSBuild binaries are.\r\n\r\nI was thinking more of overriding it to be wherever the bundled MSBuild assemblies and target/props files are.\r\n\r\nAnyway, I'm afraid that I do not think your approach (14 by default, 12 as a backup) will work in the MSBuild v12 case. I definitely considered it back when we first created ProjectCrackerTool. If I remember correctly, the problem is that the binding redirects you have in place will even affect the backup resolution, so if 14 fails and you try 12, that just gets redirected back to 14 again.\r\n\r\nI hope that one day there might be a viable alternative to MSBuild for F#."}}
{"actor":{"display_login":"rneatherway"}}