The Qlik Analytics Platform (QAP) is a developer platform for building custom analytic applications based on rich frontend and backend APIs. It gives full API access to the Qlik associative engine to build rich data-driven analytic applications, for example when building web applications for extranet and Internet deployment.
N/A
Visual Studio
Score 9.1 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.
If you want to setup analytics dashboards for reporting or simple data analysis then Qlik is your tool of choice.
Complex data structures are handled well, but you’ll need to keep de amount of data on the low side. Integration with other software is possible and easy.
It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.
It's flexible in allowing the development of fully-fledged analysis tools and dashboards, but also smaller "widgets" to embed in our websites to bring stories to life, and enables us to develop things once and then re-use them in different contexts.
The development platform and management console are both easy to use, and, with proper data development by our expert developers, can be used by relatively junior colleagues to produce great-looking and very useful products.
The way the platform handles a mix of data sources from different APIs and internal data stores is good.
We like the visualizations and from a corporate perspective find it easy to develop one-size-fits-all visualizations that present a wide range of data items well in a responsive way.
Rock solid intellisense. For C# and VB.Net code, the intellisense provided by Visual Studio is hands down the best. If you find that you have a hard time remembering parameters of functions, or what object names were, the intellisense will rescue you and help me be an efficient developer.
Super fast and simple to use debugger for C# and VB. Everything in the debugger is handed to you on a silver platter. When you stop on a break point, it immediately shows you the local variables, the call stack, and even your current memory usage. Setting up watch variables is super simple and you can even make breakpoints conditional so it will only stop on certain conditions.
Hides the tedious tasks. There are quite a few things like publishing, creating click once deployments, and adding/removing settings in the project files that can be really time consuming when trying to do it by hand (such as if you don't have access to Visual Studio and you need to make changes). Visual Studio hides all the tedium from you by making nice point and click interfaces to get things done quickly.
Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.
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.
The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.
Qlik is great for companies with lots of business domains and departments because it scales well, especially if data that is reported is saved in SQL and similar structures. Its ease of use and good UI enables business units to create and manage their own reports. That removes a great burden of creating and managing/modifying these pages from the IT team. Overall, it's a win-win for both IT and business units.
Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.
They are all good tools, each having their own pros and cons. Qlik Analytics Platform was easy to set up, more than affordable, and has a good user base. Though not as large as some of the other tools, it is growing every day and for the price, it is very hard to beat. I would recommend it. Microsoft Power BI is a little more intuitive to some users, many of them engineers, because of its similarities to Excel. I do like that it follows a similar structure to Excel but I think that it also has the same old-school GUI, which could be improved on. I prefer the way Qlik Analytics Platform's visualizations look because they appear more modern and smooth rather than rigid.
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.
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.