Microsoft offers Visual Studio Code, an open source text editor that supports code editing, debugging, IntelliSense syntax highlighting, and other features.
N/A
SharePoint Designer (discontinued)
Score 3.0 out of 10
N/A
Microsoft's SharePoint Designer was a tool for developing SharePoint applications that has been discontinued.
N/A
Pricing
Microsoft Visual Studio Code
SharePoint Designer (discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Microsoft Visual Studio Code
SharePoint Designer (discontinued)
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft Visual Studio Code
SharePoint Designer (discontinued)
Considered Both Products
Microsoft Visual Studio Code
Verified User
Anonymous
Chose Microsoft Visual Studio Code
I also used sublime and notepad++. compared to them, Microsoft Visual Studio Code provide better balance between performance, features, and flexibility. Its lightweight like sublime text but offer more features and many extension support. Microsoft Visual Studio Code is free, …
Those are agentic IDEs, a fork of VSCode, but Visual Studio Code is used for inferior hardware and has fewer features, whereas others have more features but can't be used on those devices. So, it's the POV of the machine's config: which IDE should be used? If it has a good …
As described earlier, for low overhead projects, Microsoft Visual Studio Code does a great job of getting you in and out, all the way down as far as launch time for the app and compile time. Xcode is really feature heavy, but that makes learning how to use it a task of its …
Microsoft Visual Studio Code is a great competitor to all the IDEs listed above. The vast range of extensions is a strength of the Microsoft Visual Studio Code ecosystem. Integration of Copilot is another add-on, which makes development and debugging very easy and …
It is easy to use, has strong community support and add-ons, and lets you organize files in different languages in an easy-to-use, collaborative environment. The main reason I use it is its easy integration with Git and Jupyter notebooks.
As mentioned before, IDE's can be excellent with one thing, and the company we do a lot of things, so it's kind of annoying to have multiple programs, heavy ones to open your work, so just use one, Microsoft Visual Studio Code, personalize thanks to extensions, and you are …
Microsoft Visual Studio Code offers a wide variety of addons for supporting most scripting and programming languages. In contrast, Power Automate differs from the tools we need for our business task automation. We were told to use Power Automate, but it couldn't meet our …
Notepad++ is a great tool, but has most of the power tips and tools of notepad++ are available into Microsoft Visual Studio Code I use less and less notepad++. It's more easier to "stay" into Microsoft Visual Studio Code, open a new window do my stuff and go for the next task.
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.
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 was very good for what we needed and had a lot more storage than Dropbox. This was a big factor in determining cost and analyzing what platform we were going to go with. SharePoint met the criteria we needed for our company and allows us to stay in communication with …
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 …
For low-end devices, it is a very good tool, but for devices that have decent RAM and decent CPU, I would recommend Android Studio for Android dev as it has more features, and for others, I will recommend agile IDEs like Cursor and Anti-Gravity, as they offer higher limits on AI models, and autocomplete is unlimited as well.
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.
The customization of key combinations should be more accessible and easier to change
The auxiliary panels could be minimized or as floating tabs which are displayed when you click on them
A monitoring panel of resources used by Microsoft Visual Studio Code or plugins and extensions would help a lot to be able to detect any malfunction of these
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.
I rate Microsoft Visual Studio Code 9 out of 10 because it is best editor tool for development work. It has clean and simple interface. We can easily access the file navigation, search, git integration and extensions. It support multiple languages. overall it is very user friendly and works well for both new and experienced developers.
Overall, Microsoft Visual Studio Code is pretty reliable. Every so often, though, the app will experience an unexplained crash. Since it is a stand-alone app, connectivity or service issues don't occur in my experience. Restarting the app seems to always get around the problem, but I do make sure to save and backup current work.
Microsoft Visual Studio Code is pretty snappy in performance terms. It launches quickly, and tasks are performed quickly. I don't have a lot of integrations other than CoPilot, but I suspect that if the integration partner is provisioned appropriately that any performance impact would be pretty minimal. It doesn't have a lot of bells and whistles (unless you start adding plugins left and right).
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.
The licensing of the IntelliJ IDEs is prohibitive, I cannot be sure that I can continue to leverage them as I move between clients.
Zed while interesting doesn't have the market or mindshare to be a daily driver working as part of a team. I wouldn't be able to benefit from many of the day to day automations and findings that the team invents during the course of delivery.
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
It is easily deployed with our Jamf Pro instance. There is actually very little setup involved in getting the app deployed, and it is fairly well self-contained and does not deploy a large amount of associated files. However, it is not particularly conducive to large project, multi-developer/department projects that involve some form of central integration.
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.
