Microsoft's SharePoint Designer was a tool for developing SharePoint applications that has been discontinued.
N/A
Visual Studio
Score 8.7 out of 10
N/A
Visual Studio (now in the 2022 edition) is a 64-bit IDE that makes it easier to work with bigger projects and complex workloads, boasting a fluid and responsive experience for users. The IDE features IntelliCode, its automatic code completion tools that understand code context and that can complete up to a whole line at once to drive accurate and confident coding.
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 …
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 …
SharePoint does not provide, out of the box, a tool to create / update workflows from web. You have to use SharePoint Designer in order to create them. If you need to implement custom workflows for specific business processes, then SharePoint Designer is well suited. SharePoint Designer allows you to create workflows with task approval, email notifications, assign variables and update SharePoint Lists / Documents properties. In our company, we have created specific workflows for : - Purchase order - RH forms validation like annual employee review - Dematerialized existing forms and validation
When working with base C# code for desktop and web projects, then Microsoft Visual Studio is ideal as it provides the libraries and interfaces needed to quickly create, test and deploy solutions. It is when slightly more complex scenarios are required that issues can arise. The built-in integration for things like PowerBI Paginated Reports and dashboards is far from ideal.
2013 Workflows - Loops: You can build loops to work while a value (not) equals something, or N number of times. You can insert Parallel Blocks to do multiple things at once, or to watch for multiple things, and when 1 thing finishes, cancels the others and moves to the next step or stage.
2013 Workflows - Stages: Previously all we had were steps, which worked sequentially. With the Concept of Stages, we can create blocks of steps and based on the data collected during those functions, we can tell the workflow to go to a different Stage in the workflow based on a set of 1, or multiple, Conditionals in a transition area after each Stage. Giving you the power to develop multiple entire processes and skipping to the correct part of the workflow, rather than going through 20 conditionals to find out you needed to do action 31.
2013 Workflows - REST API: the "Call HTTP Web Service" is a very powerful tool, but hard to understand if you have never seen it done, or have a guideline. It works very similar to the requirements in PowerShell to connect and get and post data to SharePoint using the Rest API. You can also use this to manage permissions on List Items, Lists, Sites, and Site Collections. Best part is when developed correctly, it is SUPER FAST!
Intentionally Building Infinite Loops: I have built multiple review process from Managing Certifications to Updating Published Documentation, that monitors when an Item, based on provided approved metadata, when the "Author" needs to review the document within the given amount of time. They will get e-mails with links asking if changes are needed. If not, it is routed to the Approving Executive, and the Workflow Automatically updates the Metadata to push out the review dates to the next date, based on metadata provided on how how often the document should be reviews. By using conditionals in the transition of stages, it basically starts over, and goes into a parallel block to allow the monitoring of multiple values of metadata to move to the next stage. Very Powerful when you want to automate these types of process. It truly is a "Set It and Forget It" process.
In the newest version of SharePoint Designer, they have gotten rid of the Design view which makes what used to be quick and easy changes much more code-intensive. This makes it harder for non-IT users and is more risker for all SharePoint Designer users.
SharePoint Designer workflows have a lot of functionality, but there are also some crucial limitations, such as not being able to put lookup fields in email subjects or using parenthesis to separate/group logical conditions.
Although this goes along with the Design view, there really isn't a good user interface anymore for adding conditional formatting and styles in views/pages.
VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.
I love the overall usability of Microsoft Visual Studio. I’ve been using this IDE for more than 20 years, and I’ve seen it evolve by leaps and bounds. Today, with AI and code-suggestion/completion features, developers no longer need to remember countless libraries, methods, or language syntax, or invest a huge amount of programming effort to complete a project. It truly offers everything a developer needs to program, debug, test, and deploy in a single IDE.
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.
There are many resources available supporting Visual Studio IDE. Microsoft whitepapers, forum posts, and online Visual Studio documentation. There are countless demonstration videos available, as well. If users are having issues, they can call Microsoft Support, but depending on the company's agreement with Microsoft, the number of included support calls will vary from organization to organization. I've found that Microsoft support calls can be hit or miss depending on who you get, but they can usually get you with the right support person for your issue.
IT is very complicated to understand all the functions that the environment has if you are not familiar with this type of development environments. It is important to select a good in-person training to achieve to understand all the possibilities and the capacity of the application. In this case, you will be able to develop a lot type of different applications.
If you are not accustomed to develop in this type of development environments it would be complicated to follow all the parts of the course because if the course does not include a great tour with all the concepts to develop you will not have the option to understand all the functions.
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 Modern version of SharePoint online
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.
For my needs, I have not found SharePoint Designer useful for my day to day maintenance of SharePoint. It is useful for viewing all the objects that make up the SharePoint site.
It is not as intuitive in regard to setting up Workflows. I have yet to use it to set up workflows in SharePoint. Maybe if I needed more complex workflows, it would be beneficial.
I like to use SharePoint Designer for moving around files within SharePoint sites.
Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.
