Skip to main content

Windows (.NET) applications

The Qlik Sense .NET SDK is a development toolbox, for use with applications such as Microsoft® Visual Studio®. It contains components for embedding Qlik Sense into host application programs developed by software manufacturers on an OEM basis. The Qlik Sense .NET SDK does not automatically provide any of the GUI. You can use a browser control to reuse the web-based Qlik Sense GUI in a .NET app or you can build a new Windows GUI using Windows chart controls or frameworks like Windows Presentation Foundation (WPF).

The Qlik Sense .NET SDK can be used for building a Qlik Sense app from scratch or for visualizing an existing app in a custom client by embedding Qlik Sense objects. It can also be used for administering or modifying Qlik Sense apps or for using Qlik Sense as a computing device. The host application, in which the Qlik Sense .NET SDK library is embedded, can be written in, for example, Visual Basic or Visual C#. This guide is not a guide for Visual Basic or Visual C#. You should have a basic knowledge of Visual Basic or Visual C# programming.

Information note

The Qlik Sense .NET SDK is available as a NuGet package.

There are several ways to connect to the Qlik Sense .NET SDK, depending on how you want to interact with your applications and expand your Qlik Sense solution. To get started and connect to the Qlik Sense installation using the .NET SDK, see Getting started with the Qlik Sense .NET SDK. The best way to connect depends on your environment. To demonstrate how to connect to the Qlik Sense .NET SDK sample code is provided, see Sample code for how to connect to Qlik Sense.

To demonstrates capabilities and use cases of the Qlik Sense .NET SDK, see Code samples of capabilities and use cases of Qlik Sense .NET SDK. They are provided on an as-is basis, without any guarantees that they will work in all system configurations and future software releases.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!