The other IDE that I use is Eclipse. Comparing both, Microsoft Visual Studio Code it clearly wins in resource consuming. I can have open many instances of Microsoft Visual Studio Code and the memory ram usage it doesn't go very high. Another point where I prefer Microsoft …
Microsoft Visual Studio Code provides more flexibility and supports easy integration to different platforms (including cloud). It is more modular and lighter application as compared to other integrated development environments. Microsoft Visual Studio Code is easy to learn and …
prior to Visual Studio Code, I was using sublime text, which was not the most effective in terms of third-party libraries and complex debugging, so I switched to Visual Studio Code where I got a positive as a developer. it is having all the features and third-party libraries to …
Far better than eclipse IDE. Eclipse takes so much space, and it is slow. Whereas Vs Code IDE is so fast and having good UI as compared to Eclipse. I help to work efficiently and is also highlight the syntax in good way by recommending in editor. Microsoft Visual Studio Code …
1. More features compared to Notepad++ 2. fast performance compare to Android Studio 3.More and usefull extensions then other two 4. Easy to use and everyone can start using it instantly 5. Version Control system is top notch 6.If you start using it , you will forget other ides …
Microsoft Visual Studio Code is a combined form of the above-mentioned products i.e. one product, many applications. Eclipse is suitable for java development, PyCharm is mainly for Python development whereas Android Studio is for Android applications development but in …
Microsoft VS Code is extremely customizable with needs. So, features like syntax highlighting, bracket-matching, auto-indentation, well-integrated terminal, and side-by-side editing are powerful. Even these features are given free with Microsoft VS code. Pycharm and Webstorm …
It has [the] right balance of solutions for [a] wide range of problems. Atom or Notepad++ are lighter but [have fewer] features, [Microsoft] Visual Studio [Code] is full of features but [a] tad heavier.
I think VS Code is much better as compared to all the tools mentioned above. Just waiting for its support for iOS and Android development. currently, it misses support for them. That's where you will require Xcode and Android Studio.
Microsoft Visual Studio Code has turned out to be far more powerful than the original promises of the Atom editor. Microsoft Visual Studio Code supports large files much better than Atom, and more extensions are available for language support. NetBeans has been a slower …
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 …
Visual Studio Code stacks up nicely against Visual Studio because of the price and because it can be installed without admin rights. We don't exclusively use Visual Studio Code, but rather use Visual Studio and Visual Studio code depending on the project and which version of …
When you start using [Microsoft Visual Studio Code], it lands more on the "text editor" side of the spectrum, akin to Vim/Emacs/Sublime. Aligned with this, it's fast and easy to install and setup, and competes with the best of them as a great general purpose tool. But then it …
Visual Studio Code is one of the peak engineering tools you can use today on the market. It's one of the most advanced IDE, and, currently, a de-facto top-used IDE. This alone should be proof to use it.
[Microsoft] Visual Studio Code beats the competition due to its extensibility. Their robust extensions architecture combined with the plethora of mostly free extensions written by the community can't be beaten. The fact that this tool itself is provided by a world-recognized …
There are many IDEs available but I don't think anyone is better than Visual Studio Code. Most others are language dependent softwares while VS Code supports all the languages. There are others popular available like Atom, Eclipse, IntelliJ IDEA, and WebStorm but none of them …
I have been using vim as both editor and IDE for development projects for a long time until I met Visual Studio Code. VS Code can provide the editing power of vim through a plugin, plus many other benefits, thus it can easily replace vim in most development use.
When it comes to UI and light weightiness, Visual Code is the winner. But when it comes to Intelli-Sense and autosuggestion IntelliJ works better in my view.
Microsoft Visual Studio Code wins hands down when it comes to light, easy, free yet super powerful. This is the perfect balance for that. If you need to manage a complete end to end project with team collaboration I would recommend Visual studio IDE or Eclipse if you need to …
User interface and integration to other tools is very straightforward and easy to use. You can find [third] party [development components] very easy for Microsoft. You can code a variety of applications using the same framework without installing any plugins or extensions (Web …
Every IDE has almost the same features but being lightweight is a plus point for the IDE so that you can run on any hardware with good speed. VS Code has ultimate features.
Microsoft Visual Studio Code is more lightweight than most other options, such as Spyder and MATLAB. These other applications provide strong benefits such as a useful user interface that displays information about variables in in your workspace, as well as a window for built-in …
I haven't used anything else like this. I use different products for workflows and forms, but they aren't listed in the listings for this page. Instead of using it for workflows or forms (deprecated 2 years ago), I use Nintex. For everything else, I have what I need in the …
These products are very good alternatives to SharePoint Designer but SharePoint Designer stacks up when you are using it for on-premise SharePoint environment.
I prefer InfoPath for designing forms for use in SharePoint over SharePoint Designer. I have not used SharePoint Designer for designing pages in SharePoint. I have found it easier to work directly in SharePoint. Granted I have only had the product for a little over a year.
I'd say that Nintex is a lot easier to configure and identifying errors is less complex than SharePoint Designer. In addition, an alternative that developers may prefer using is Adobe Dreamweaver which is also a web development tool. A third option is Coda, a text editor that …
SharePoint Designer is somewhat inferior when compared to a purpose-built third-party tool like Nintex. Even though Nintex leverages built-in workflow engines (SP2010 and SP2013 depending on platform), it builds on top of that and adds many useful features.
Nintex Forms and Workflow are both very robust tools, but cost for some clients can be prohibitive. Nintex does not provide tools to manage SharePoint sites, lists and libraries.
Both K2 and Nintex provide a powerful platform to build and run business applications that integrate seamlessly with SharePoint; business apps typically consist of workflow, forms, data and reports. The type of business apps range from simple document approval workflows to …
Both Nintex and K2 Blackpearl are great products in their own way, but they are expensive. The pricing models for the SharePoint Online environment is very expensive for how Holiday uses workflows. Nintex's pricing model is by the number of workflows in your tenant, and I …
There really isn't a holistic, complete SharePoint Designer replacement currently. You can utilize several different tools and piece together the functionality of Designer. No one really "selects" SharePoint Designer, it is just a necessary evil. For O365 subscribers, Flow …
SharePoint Designer is the only tool of its kind that I feel 100% comfortable using. Compared to the Nintex workflows/forms, SharePoint Designer has much more increased functionality and ease for an IT-type user like myself. I think it has a much better and easier to navigate …
As I said before, I didn't select SharePoint Designer per se, but I did (and will continue to) elect to sometimes use Designer rather than create deployable solutions in Visual Studio.
Designer could be called the lazy person's tool for modifying SharePoint. Solutions created in …
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.