Does anyone here use VSTO in real work ? I don't have a query, it's just that I don't know anyone personally who uses VSTO in a bank.

Is that a "no", then.

They are pushing it quite hard - free downloads as opposed to the previous (paid for) version. I've never heard of anywhere using it yet though.I'm not sure it's the best tool for the financial market. One one side .net will be rather over the top for your average VBA spreadsheet type; on the other it's not as powerful as a custom application - you get more flexibility from developing your own application than integrating with office.

On the occasions that I've seen people look at it, they instead took the route of writing .net assemblies enabled for automation, and had excel use those through vba wrappers. I guess because it's the more understood way of doing things.

Yes, I've used vsto.1) Ok if you want to use Excel 2007's new GUI.2) Most developers want an add-in in an xll flavour. So they usually go with using an XLL to .net wrapper technology. I've not seen a native C++ XLL for some time with most of my companies clients. The current SDK for producing .net UDF (In VSTO) within Excel takes to much code compared (it's a real bag of spanners) with the XLL/.net approach, so why bother and VSTO has less functionality. 3) I find the templates for producing installers a bit to prescriptive in VSTO, but that can be worked around.I suspect when Excel 2007 makes more in roads VSTO use will pick up for producing GUI front ends to Excel add-ins.M

I used it at work.C# with vsto for Excel 2007 in VS 2008.Yeah, they push the new ribbon GUI really hard. I find more use for my time working in stand alone application than to try to learn how to create fancy ribbon, writing menu xml in vsto.Give it a few more years and maybe they can convince me to revisit it.

how do u incorporate a customised function in C++.. into MS excel through dll/xll??? i have tried everthng... doesnot work though... please help me out....tried using sample codes on net... still does not work...

try using a VBA wrapper function. So Excel calls -> VBA wrapper function, which calls a customized function in a compiled dll file.