{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/msbuild/issues/185","labels_url":"https://api.github.com/repos/Microsoft/msbuild/issues/185/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/msbuild/issues/185/comments","events_url":"https://api.github.com/repos/Microsoft/msbuild/issues/185/events","html_url":"https://github.com/Microsoft/msbuild/issues/185","id":104787003,"number":185,"title":"32-bit MSBuild.exe running as LOCAL SYSTEM calls 64-bit VBCSCompiler.exe causing CSC : error CS2001: Source file 'file' could not be found","user":{"login":"reidca","id":7325010,"avatar_url":"https://avatars.githubusercontent.com/u/7325010?v=3","gravatar_id":"","url":"https://api.github.com/users/reidca","html_url":"https://github.com/reidca","followers_url":"https://api.github.com/users/reidca/followers","following_url":"https://api.github.com/users/reidca/following{/other_user}","gists_url":"https://api.github.com/users/reidca/gists{/gist_id}","starred_url":"https://api.github.com/users/reidca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/reidca/subscriptions","organizations_url":"https://api.github.com/users/reidca/orgs","repos_url":"https://api.github.com/users/reidca/repos","events_url":"https://api.github.com/users/reidca/events{/privacy}","received_events_url":"https://api.github.com/users/reidca/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-09-03T21:39:41Z","updated_at":"2015-09-11T05:44:28Z","closed_at":null,"body":"I posted this issue on connect almost as soon as MS Build 14.0 was available and it has gone nowhere therefore I thought I would post it here as well to see whether anyone can help with this.\r\n\r\nOne could argue that running MSBuild as SYSTEM is perhaps a corner-case however most continuous delivery toolsets run as Windows Services, running as SYSTEM which is where we experienced (and continue to experience) the issue. Surely we are not the only people to have seen this?\r\n\r\nhttps://connect.microsoft.com/VisualStudio/feedback/details/1580569/32-bit-msbuild-exe-running-as-local-system-calls-64-bit-vbcscompiler-exe-causing-csc-error-cs2001-source-file-file-could-not-be-found"},"comment":{"url":"https://api.github.com/repos/Microsoft/msbuild/issues/comments/139459305","html_url":"https://github.com/Microsoft/msbuild/issues/185#issuecomment-139459305","issue_url":"https://api.github.com/repos/Microsoft/msbuild/issues/185","id":139459305,"user":{"login":"jasonwilliams200OK","id":2031765,"avatar_url":"https://avatars.githubusercontent.com/u/2031765?v=3","gravatar_id":"","url":"https://api.github.com/users/jasonwilliams200OK","html_url":"https://github.com/jasonwilliams200OK","followers_url":"https://api.github.com/users/jasonwilliams200OK/followers","following_url":"https://api.github.com/users/jasonwilliams200OK/following{/other_user}","gists_url":"https://api.github.com/users/jasonwilliams200OK/gists{/gist_id}","starred_url":"https://api.github.com/users/jasonwilliams200OK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasonwilliams200OK/subscriptions","organizations_url":"https://api.github.com/users/jasonwilliams200OK/orgs","repos_url":"https://api.github.com/users/jasonwilliams200OK/repos","events_url":"https://api.github.com/users/jasonwilliams200OK/events{/privacy}","received_events_url":"https://api.github.com/users/jasonwilliams200OK/received_events","type":"User","site_admin":false},"created_at":"2015-09-11T05:44:28Z","updated_at":"2015-09-11T05:44:28Z","body":"@reidca, Limitation is anti-freedom. FreeBSD, Ubuntu, Mac, Solaris etc. possess no limit on path, which means their MAX_PATH limit == the limitation of underlying filesystem, which in many cases is virtually infinity. For example, NTFS limit is 32000 characters, while Windows caps it down to 256 in the name of backward compatibility with FAT! I don't think anybody in the world who encountered MAX_PATH limit is happy about it except for some former boss of Windows team who made this decision in last century and the entire world is reaping the consequences till date. It is a shame that nobody at Microsoft dares to enlighten Windows team that they have at least made one blunder which is imposing MAX_PATH! One of the reasons the most popular node.js package management system \"npm\" wasn't considered first-class supporter of Windows due to this limit since npm tends to nest the sub-dependencies. However, they had to reboot their whole packaging infrastructure due to MAX_PATH with npm3 (still in beta): https://github.com/npm/npm/issues/3697"}}