{"action":"opened","issue":{"url":"https://api.github.com/repos/OmniSharp/omnisharp-vscode/issues/2174","repository_url":"https://api.github.com/repos/OmniSharp/omnisharp-vscode","labels_url":"https://api.github.com/repos/OmniSharp/omnisharp-vscode/issues/2174/labels{/name}","comments_url":"https://api.github.com/repos/OmniSharp/omnisharp-vscode/issues/2174/comments","events_url":"https://api.github.com/repos/OmniSharp/omnisharp-vscode/issues/2174/events","html_url":"https://github.com/OmniSharp/omnisharp-vscode/issues/2174","id":313211338,"number":2174,"title":"Remote Debugging On Linux Arm instructions are incorrect for FDD","user":{"login":"pierslawson","id":792983,"avatar_url":"https://avatars2.githubusercontent.com/u/792983?v=4","gravatar_id":"","url":"https://api.github.com/users/pierslawson","html_url":"https://github.com/pierslawson","followers_url":"https://api.github.com/users/pierslawson/followers","following_url":"https://api.github.com/users/pierslawson/following{/other_user}","gists_url":"https://api.github.com/users/pierslawson/gists{/gist_id}","starred_url":"https://api.github.com/users/pierslawson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pierslawson/subscriptions","organizations_url":"https://api.github.com/users/pierslawson/orgs","repos_url":"https://api.github.com/users/pierslawson/repos","events_url":"https://api.github.com/users/pierslawson/events{/privacy}","received_events_url":"https://api.github.com/users/pierslawson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-11T07:53:52Z","updated_at":"2018-04-11T07:53:52Z","closed_at":null,"author_association":"NONE","body":"## Environment data\r\nNot Applicable\r\n\r\n## Steps to reproduce\r\n\r\nFollow the steps in he [Remote Debugging On Linux Arm](https://github.com/OmniSharp/omnisharp-vscode/wiki/Remote-Debugging-On-Linux-Arm#build-and-deploy) documentation page to do a Framework Dependent Deployment. Check that you can debug the sample console application.\r\n\r\nAdd a reference to a NuGet package and make use of that package in the sample code.\r\n\r\nTry to debug the new version of the sample console application.\r\n\r\n## Expected  behaviour\r\n\r\nAble to debug into your code both with the original sample console application and the extended console application.\r\n\r\n## Actual behavior\r\n\r\nAble to debug into the original sample application but not into the extended version. See errors regarding assemblies missing e.g.\r\n```\r\nAn assembly specified in the application dependencies manifest (MyConsoleApp.deps.json) was not found:\r\npackage: 'System.Text.Encoding.CodePages', version: '4.4.0'\r\npath: 'lib/netstandard2.0/System.Text.Encoding.CodePages.dll'\r\nThe target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.\r\n```\r\n\r\nThe documentation appears to be wrong for Framework Dependent Deployment. It should use `dotnet publish` rather than `dotnet build` and the contents of the `bin/Debug/netcoreapp2.1/publish` directory should be copied to the `Linux-arm` device. If you use only `dotnet build`, you don't get a `publish` directory, and if you only use the contents of the `bin/Debug/netcoreapp2.1` you only have your own assembly, not any referenced assemblies... hence the load error.\r\n\r\nI had at first thought this was a dotnet/cli#9039 problem!\r\n\r\nI'll look to create a pull request later."}}
{"actor":{"display_login":"pierslawson"}}