{"action":"created","issue":{"url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1304","repository_url":"https://api.github.com/repos/techtalk/SpecFlow","labels_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1304/labels{/name}","comments_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1304/comments","events_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1304/events","html_url":"https://github.com/techtalk/SpecFlow/issues/1304","id":371533942,"node_id":"MDU6SXNzdWUzNzE1MzM5NDI=","number":1304,"title":"Still not NetCore and stuck because of new feature ? why not ship a minimal working set","user":{"login":"tebeco","id":2266487,"node_id":"MDQ6VXNlcjIyNjY0ODc=","avatar_url":"https://avatars0.githubusercontent.com/u/2266487?v=4","gravatar_id":"","url":"https://api.github.com/users/tebeco","html_url":"https://github.com/tebeco","followers_url":"https://api.github.com/users/tebeco/followers","following_url":"https://api.github.com/users/tebeco/following{/other_user}","gists_url":"https://api.github.com/users/tebeco/gists{/gist_id}","starred_url":"https://api.github.com/users/tebeco/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tebeco/subscriptions","organizations_url":"https://api.github.com/users/tebeco/orgs","repos_url":"https://api.github.com/users/tebeco/repos","events_url":"https://api.github.com/users/tebeco/events{/privacy}","received_events_url":"https://api.github.com/users/tebeco/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-18T13:35:46Z","updated_at":"2018-10-18T13:49:19Z","closed_at":"2018-10-18T13:49:19Z","author_association":"NONE","body":"Hi @SabotageAndi ,\r\n> Please contact @SabotageAndi before you are starting on an issue.\r\n\r\nI'm here a bit angry, as i see there is a Github project in order to act as a roadmap and i wonder about the delivery.\r\nIt is already time for netcoreapp 2.2-preview 3 and 3.0  but still no way to use spec flow\r\n\r\nWhat worked before :\r\n* Windows ? Ok\r\n* Running on the CI ? Ok\r\n* Running from a console ? Ok\r\n* Visual Studio Integration ? Ok but not a blocker \r\n* Mac ? Never existed on netfx => new feature => Why would it block a working release ?\r\n* Linux ? Never existed on netfx => new feature => Why would it block a working release ?\r\n* Visual Studio integration ? just confort => let's target the blocker => Console + CI\r\n\r\nToday companies see this as a STRONG blocker to move to .NetCore\r\nThe csproj for specflow\r\n* has to target fullfx\r\n  * Cannot reference project in `netcoreapp` project\r\n  * Need to split apps between host / controller in order to test\r\n* still uses app.config and config section (custom runner)\r\n\r\nI'm wondering if there's a way to make people ALREADY using SpecFlow happy but delivering a mininal working set like  `dotnet test` or `dotnet specflow` in a console for local dev / ci\r\n\r\nAlso the 2 or 3 issue does not seems to be detailed or block anything. Is there any missing issue in this board ?\r\n\r\nI'd love to have info like a date or more detailed info in order to know if we move out of specflow while you work on it\r\nor if we wait for a release ?"},"comment":{"url":"https://api.github.com/repos/techtalk/SpecFlow/issues/comments/431015762","html_url":"https://github.com/techtalk/SpecFlow/issues/1304#issuecomment-431015762","issue_url":"https://api.github.com/repos/techtalk/SpecFlow/issues/1304","id":431015762,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMTAxNTc2Mg==","user":{"login":"SabotageAndi","id":859801,"node_id":"MDQ6VXNlcjg1OTgwMQ==","avatar_url":"https://avatars0.githubusercontent.com/u/859801?v=4","gravatar_id":"","url":"https://api.github.com/users/SabotageAndi","html_url":"https://github.com/SabotageAndi","followers_url":"https://api.github.com/users/SabotageAndi/followers","following_url":"https://api.github.com/users/SabotageAndi/following{/other_user}","gists_url":"https://api.github.com/users/SabotageAndi/gists{/gist_id}","starred_url":"https://api.github.com/users/SabotageAndi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SabotageAndi/subscriptions","organizations_url":"https://api.github.com/users/SabotageAndi/orgs","repos_url":"https://api.github.com/users/SabotageAndi/repos","events_url":"https://api.github.com/users/SabotageAndi/events{/privacy}","received_events_url":"https://api.github.com/users/SabotageAndi/received_events","type":"User","site_admin":false},"created_at":"2018-10-18T13:49:19Z","updated_at":"2018-10-18T13:49:19Z","author_association":"COLLABORATOR","body":"I know a lot of people are waiting on .NET Core support for SpecFlow and my team and I are working hard on it.\r\n\r\nWe are nearly finished with it. I merged yesterday the PR into the master branch.\r\nAfter that some new problems with our tests appeared, which we haven't yet solved.\r\n\r\nSo a preview release is not far away. I am talking here about days and not weeks. So a little bit more patient here please.\r\nNo need to get angry. \r\nAfter all, this is an open source project that lives from it's contributors. "}}
{"actor":{"display_login":"SabotageAndi"}}