7

I'm looking for some high-level help with determining the best type of Visual Studio 2010 project to use for an Excel custom application.

I will be developing a program that requires the user to enter a dataset in a particular way. Not using a form per se, but rather in columns and the program will need to do some custom validation on the items in order to prep the data. From there, the user will be able to conduct various operations on the data via a custom Ribbon and associated options. The program will also transmit the data via web service.

I've fooled around with the Add-In project and that gives me a lot of what I need but I'm wondering if a Template or Workbook project is better for this in terms of data entry and being able to "guide" the user a little more.

How do you go about choosing between which project type to use? Do all the project types support a custom Ribbon?

Community
  • 1
  • 1
Unknown Coder
  • 6,625
  • 20
  • 79
  • 129
  • 2
    If you plan to use VSTO then go in for an Add-In. But if you want to go In for a Template and Workbook then you can create customized ribbons using the Custom UI Editor. In such a case you will not require VSTO. I would recommend seeing this link http://stackoverflow.com/questions/8850836/how-to-add-a-custom-ribbon-tab-using-vba on how to work with the Custom UI Editor – Siddharth Rout Jul 16 '12 at 16:02

1 Answers1

4

Sorry if this is too far off topic. I'm referring to VBA, not Visual Studio, but it might still be relevant.

With an AddIn, compared to a Workbook, you can separate your code from the user's data. So, if the code is complex, and you'll need to update it separately from user's workbooks with data, this is not a bad idea.

With an AddIn, you can add buttons that do things like check to make sure the user data workbook is ok, or process it in someway. However, the AddIn custom buttons will load ever time a user opens any Excel worksheet. This doesn't sound good, but in practice, isn't so bad. You can code your AddIn so it does nothing as long as no one uses a button, so it almost doesn't hurt load times, etc...

A Workbook might be useful if you need to really guide the user - that is, you cannot rely on the user to hit a button to verify something, and instead you need to verify on every change, for example. However, the workbook solution incorporates the user data and your code in the same workbook, so if you need to update the code for existing users' data, that's harder.

I use a combination of AddIn (.xlam) with buttons, and a template (with minimal self-describing data only).

I'm not sure about the template-only option, so won't comment on that.

Erik Eidt
  • 23,049
  • 2
  • 29
  • 53