If your Source Control Software is Team Foundation Server then skip Visual Studio Code. If you're using GitHub and are creating small projects Visual Studio Code is the way to go. If you need to create a large, enterprise-level application, Visual Studio Code makes it easier to set up interactions between related projects (client & server). If you're interested in getting back to the old way of using the command line to create projects and you know what to enter in the console window then Visual Studio Code is great. Visual Studio Code is a better choice if you don't know the console commands and prefer to make selections from a menu.
Well Suited - WORKFLOWS! To a SharePoint Developer, workflows are like a hammer to a carpenter. If there is a business process that needs automation, the first thing I look to is what are we automating? What/where is the data? How can we minimize the number of keystrokes by end-users to get from the start to finish? The answer to all of these is "build a workflow". With the introduction of "Call HTTP Web Service" action, you can now access data anywhere in a site collection and consume it in any site, on any list, for any form. SharePoint Designer Workflows makes the SharePoint world go round. Less Appropriate - Building SharePoint Pages I have attempted to use SharePoint Designer to build custom pages, but it just is the worst tool to use. There are many other tools to use to develop customized pages. The techniques of designing custom page layouts, CSS files to populate in pages, JavaScript Snippets for pages have changed so much over the years, and SharePoint Designer did not change with them. In fact, it is my opinion the 2013 version made it 100 times more difficult than the 2010 Version.
SharePoint Designer offers more granularity of customizing a workflow that is more sophisticated solution that can effectively delegate tasks to responsible parties and reflects status updates of task status.
SharePoint Designer allows SharePoint professionals the ability to customize a SharePoint site with HTML5, CSS3, and JavaScript that can be integrated in .ASPX pages.
SharePoint Designer offers form customization where Office products such as Word, Excel or PowerPoint cannot meet specific government requirements and or expectations.
Unlike for most languages I have used, Ruby and Rails support available for Code users isn't great. The most popular Ruby extension is unofficial, and leaves much to desire. As an example, code navigation even with language server Solargraph installed isn't as good as IntelliJ's RubyMine.
Even there is quite good support for a language or a framework, it is almost never as good as a dedicated IDE for it. In terms of the sheer number of features available, IntelliJ IDEs handily beat Code.
Microsoft has close-sourced some of the extensions it develops for Code itself, e.g. Pylance for Python, and that has not been perceived as a good move for open-source.
Navigation between sub-sites and beyond the entry point is not seamless. I find it difficult to get to the root of a directory structure if I have not started there.
Would love to be able to do WYSIWYG in some form. I have only used it for a year but I have not found anything fancy to do.
I would like to be able to work in a development site and easily move to the production site.
Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.
Looking at our current implementation, Microsoft Visual Studio Code is perfect for writing code and performing debug operations. Integration with SVN repository is easy and changes can be tracked effectively. Microsoft Visual Studio Code supports developers to write code productively using syntax check and easy customization. Microsoft Visual Studio Code also provides support for IntelliSense which prompts suggestions for code completion. It is easy to step through code using interactive debugger to inspect the root cause of error quickly.
Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.
Support is good from Microsoft. They are quite responsive when we raise a ticket but SP Designer support will be ended by Microsoft in the near future as they have got new techs like PowerApps and Flow to achieve the same functionality SP Designer does and even more than that.
All the previously listed are incredible development environments that perfectly fulfill this function, but [Microsoft] Visual Studio Code goes one step ahead by providing flexibility, customization and adaptability to development environments with its own methodology, for all this productivity. of the work team is greatly increased helping to achieve the objectives set in the organization.
In order to simplify our internal workflows, we have installed additionnal tool for our SharePoint platforms : Nintex Workflow and forms. Compared to Nintex, SharePoint Designer is very far away. I am only talking here for 2 main features of SharePoint Designer : - Workflows - Forms But for these 2 features, Nintex is way above SharePoint Designer
With workflows alone we have had a positive ROI because it gives us increased functionality and value with a smaller amount of development time needed.
The testing of workflows or pages is more structured and we have less base cases than a ground-up customized development solution.
Occasionally, we will have a negative impact on our ROI based on the work-arounds needed to make SharePoint Designer work for a specific project, but overall there has been more positive impacts than negative.
