What you say is correct - the QlikView WorkBench contains a number of 'drag and drop' controls for Visual Studio.NET which allow you to add QlikView objects into your website.
As well as supporting the 'native' QlikView controls such as listboxes, charts etc. there are also some additional controls not found in standard QlikView - for example a map control and a 'flexigrid' which can be used for rendering lists of products or other items in a more configurable manner.
End users will need a CAL just as if they were using the standard Zero-Footprint client and I believe now that a licence is also needed on the QlikView Server for the QlikView WorkBench itself although I am not too sure of the details on that.
My company, Industrial CodeBox, actually developed the QlikView WorkBench before it was on by QlikTech so we naturally have a lot of experience in using it and I should be able to answer further questions if you have any. From your post I don't think it will give you any benefit in terms of getting your reports out to more users unless you need more flexibility in how the reports look or operate or if you need to create some custom visualisations of you QlikView data.
The workbench product is an add-in to Visual Studio and allows you to embed individual QlikView objects in a web page. It is an add on to a QlikView Enterprise server license and end users require a license in the same way they do for standard server access.
To see some examples of end results please visit demo.qlik.com and checkout
I understand this is old thread. But I thought one of you might help me with Workbench configuration issue. I have installed successfully but I am when I open the Visual Studio, I don't see the QV tools on my VS IDE. Please can you help me with this?
What version of workbench? I'm using Workbench for V10 SR2. In this instance, you need to add the reference after creating the project...
or if you go to new website, there should be an icon for QlikView WorkBench under My Templates.
After that, if you have QV Server installed on the same machine as visual studio, your connectivity to QVW files will work pretty easily.
For us, we have VS on one machine, and QV server on another. The included Proxy.ASPX does not work because it just does a redirect and we use header injection for authentication. We have to start a session to the qlikview server and authenticate with injected header to the accesspoint before we are able to see qvw files. When the connection breaks, you get a nasty exception message from VS.
Hopefully your set up is more the former than latter.