Home/ Questions/Q 671823
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T00:24:58+00:00

I use VSTO Excel template based solutions frequently. One of the things I like

  • 0

I use VSTO Excel template based solutions frequently. One of the things I like about this project type is that I can use cached data sets in the Excel template or worksheet to handle application state that persists after the user saves the file. However, cached data sets create a problem: the schema of the document is bound to the application version.

This hasn’t been a big problem, but I’ve realized it would be a good idea to create a mechanism that will read the version of the Excel document when it opens in order to detect and handle version incompatibilities. For example, if my 2.1 plugin opens a 1.5 document, the schema of the cached data will not match what is expected.

Is there a standard or recommended way to version stamp the Excel template or worksheet? If not, does anyone have suggestions on how to do this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I usually use the Worksheet.CustomProperties to persist information like this into my worksheet. Any information you put into the CustomProperties collection gets saved along with the worksheet and is loaded back along with the worksheet information when you reload the worksheet.

    Workbooks also support custom properties, but I think in your case Worksheet.CustomProperties is the way to go.

    • 0