Moving from VBA to VSTO

[chatterbox]

Hello Everyone.

Not strictly a VBA question, but can you offer me your thoughts on the
following ?

I have created a prototype VBA application which contains some
proprietary algorithms. The next step will be to convert this xla add-
in into a modest commercial application. The application in VBA is
pretty instantaneous to execute. I would say there is moderate
interaction with the worksheet, but certainly not intense. The VBA
application extracts data from a worksheet, does some number
crunching, creates graphic and tabular data outputs, then deposits a
copy of the model data to MS Access which acts as a repository for
historic values. Ultimately I wish to create a commercial application
with auto-installation, a front loader that opens Excel, adds a custom
toolbar or ribbon, links to Access, and links to a client intranet so
that external stakeholders may view the model data. In so doing I
wish to make secure the algorithms which underpin the application.

Q1. My temptation is to jump in and embrace .NET and VSTO. Can you
please advise me on the road you would choose, and why ? Possible
scenarios are outlined below but not limited to these:

1. VB6 COM application utilising Ruby Forms

2. C++ COM application utilising Windows Forms via VSTO

3. C++ automation add-in with front loader to mimic a COM application
(I have heard it can be done), utilising Windows Forms via VSTO.

4. C# application utilising Windows Forms via VSTO

5. VB6 / C# hybrid application (I have heard this too can be done)

Q2. If I embrace VSTO, is there a standalone version I can utilise,
free or otherwise, or must I purchase Visual Studio Professional and
then download VSTO ?

Thanks in advance

chetterbox

 

[Bob Phillips]

Personally, if I were in your position and I believed there was a market for
this tool, I would go for the C# or VB.Net option using VSTO and Windows
forms, building a COM addin. This does limit your market somewhat, Excel
2003 or 2007 I think, but that may be acceptable.

If you are worried about the learning curve at this point, although Chip
Pearson has a good tutorial at
http://www.cpearson.com/Excel/CreatingNETFunctionLib.aspx, you could build a
VB6 COM addin, and migrate to VB.Net later. Chip also has a good tutorial on
classic COM addins at http://www.cpearson.com/Excel/CreatingCOMAddIn.aspx
and automation addins http://www.cpearson.com/Excel/AutomationAddIns.aspx.

--
HTH

Bob

(there's no email, no snail mail, but somewhere should be gmail in my addy)