> Are you certain you want hard references to Excel's primary interop > assemblies (PIA)? > Generally, you only reference the PIA during development. > Once development is complete you should remove the PIA reference and > change > the type of the Excel application class to 'object'.
Yeah I know what you mean if all we do is export static data to excel, but we do more than that. In our case we build an excel workbook with text references that excel resolves by creating a data subscription to our application that is updated in real time. This is done by having excel host some of our .NET FW interop code through a shim dll, which when activated creates a remoting cross process channel to our real time data subscription layer in our application process. For this to work in retail mode, the dll that hosts our code in the Excel process space needs to be installed into the GAC and be binary compatible with the current Excel version, since it is Excel that calls into our app through that assembly as the cell reference is resolved. This allows us to setup cells that update in real time push style from the server using native excel mechanisms with all the bells and whistles that comes w that (live updating spread sheet objects, and whatnot). But thanks for the heads up! /Mathias ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
