Both "customizing QV" and "Dotnet" are too broad topics to give you a precise answer, I can think of several meanings:
Extending functionalities of QlikView desktop -> embed the QlikOCX component in a .Net application (or any Windows application) to interact with QlikView objects and add custom behavior on top of it. An example of such an application is GeoQlik.
Importing QlikView objects in a web site -> use the QlikView workbench to interact with a QlikView server document in an ASP.Net application, allowing to do mashups and cleanly integrate QlikView to your website. An example was desirabelles website but it does not seem to be still online.
Designing new chart objects -> implement a QlikView extension that will render data in its own way. Though it does not have to be anything .Net you can use any technology embeddable in a web browser, so Silverlight, XBAP or even a .Net ActiveX control could be used.
I know this is quite an old thread, but I haven't found something more up-to-date, so I hope you can help me out:
A customer wants to integrate QV in one of his server applications (which is a WPF Browser Application using XBAP on .NET 4.5), so as far as I understand, it's a rich client internet application (communicating to its server using several web services).
The integrated QV component should talk to the QV server, essentially silently opening an application, displaying some QV list boxes in the application and allowing to trigger a data export (to a file (on server or remote) ).
The customer had the idea to use QV OCX component to integrate into his WPF application.
Honestly, I've never done that before and never heard of this before (I think today's usual way to integrate QV would be accessing the QV JS API). Well, I know the IE plugin and I can imagine how to create an 'old-style' windows desktop application using the OCX component and access the QV server in principle, but I am unsure about the XBAP part.
So, here are my questions:
1) Is this scenario feasible at all?
3) Using the OCX component, what about licensing and authentication?
Hope you can answer at least parts of my questions or send me a link to other areas of interest.
1) WPF applications can embed OCX components so i guess XBAP should too.
3) Licensing and authentication is completely transparent: the OCX will use whatever qlikview license is installed on your computer (it can be a qv desktop license, a license leased from a server or even no license at all, in which case you will have the same limitations as in the personal edition). Opening a document on a server from the OCX will prompt the same authentication dialog as the desktop client.
One last thing: the OCX cannot use webview, and extensions only work in webview.