So this makes Workflow available across all Visual Studio Editions.
#MICROSOFT VISUAL STUDIO 2017 ENTERPRISE EDITION RC INSTALL#
There is no need to install the ‘Office/Sharepoint development’ workload anymore. One nice thing which is not mentioned in the above blog, is that this update has Windows Workflow as an Individual Component.
NET Core Tools.įor details, you can refer the complete announcement from the VS Team – On 12th December, 2016 – Visual Studio team announced an update to the VS 2017 RC, which contains multiple enhancements and bug fixes to the. NET Community members – The ‘Office/Sharepoint development’ was not available in the VS Community Edition – which was again a kind of blocker for workflow users using that edition of VS. There was another issue which was brought up by the. Although it was not the convincing way of having Workflow enabled, it did work! Once you had that particular workload installed, you could successfully build your workflow projects. To have Workflow working, you had to install the ‘ Office/Sharepoint development‘ workload. It actually turned out not to be a bug, but the way Workflow had to be installed. Thanks to Blake Helms for his blog post which had a solution to the above problem –
I reported this problem to Visual Studio Team, who have been very active in evaluating and responding to the bugs reported by the community members – I use Windows Workflow Foundation heavily in my projects, and to my surprise when I tried to open one of my existing solution, the projects containing WCF Workflow Service failed to load – as if they were not supported in VS2017. With the initial release of Visual Studio 2017 RC, there were multiple issues reported related to Windows Workflow Foundation in the VS Developer Community site.