I have the following installed on my Windows XP(sp2) machine;

Office 2003 Pro (sp2)

Visual Studio 2005 Pro (sp1)


VSTO SE Runtime

My objective was to create custom Excel applications, but none of the Office templates are available when start a new project. If I understand correctly, this would be a 'Document Level' application. What is the difference between that and an 'Application Level' application

I found this in the forum;

"VSTO 2005 SE is a free add-in for Visual Studio Professional and higher that only provides application-level add-in project templates. To use the document-level project templates (Excel workbooks, Word documents), you must purchase Visual Studio 2005 (this is a separate product from Visual Studio 2005 SE)."

It seems like I meet this requrement. However, the information at this URL seems to indicate that I can't create these applications if I'm running VS 2005 Pro;

Do I need to have Team System installed in order to create Document level applications, or am I missing something in my setup

Thank you for your help!


Re: Visual Studio Tools for Office VSTO SE Installed on VS 2005 Pro


Hello cdun,

(as I know)

yes you are correct,

VS 2005 Professional with VSTO SE installed doesn't support document level addins.

What is the difference.

Application level Addins are loaded into an application and available through the whole application runtime and for each document.

They have to be installed on the client machine.

Document level Addins are attached to 1 document and available only for this document.

They don't have to be deployed on the target machine.

Note that Document level Addins are not supported by Office 2003 Standard editions too.

(because Document level AddIns sit on top of Sharepoint technology)

But what is the goal you want to archive with your AddIn

Greets, Helmut

Re: Visual Studio Tools for Office VSTO SE Installed on VS 2005 Pro


Thank you for your response. I do reporting through Crystal Reports for a number of our users. Those users typically export data from their Crystal Report into Excel. We also have a number of users who receive data at the end of each month in spreadsheet from (the data is static). This requires someone to process the data, get it into a Workbook, and either email the workbook or put it into a share on the network.

I've started using ADO in Excel to call SQL Server stored procedures to return data into the Workbooks in order to eliminate the Crystal step, static data in worksheets, and the manual processing (with the help of DTS). This approach has become popular, and I can see that I will have the need for more functionality, and the use of application roles in SQL Server. I would also like an easier way to work with controls like combo boxes (I use the one on the forms toolbar, and it takes some tricks to populate those with data from SQL Server).

Our group is also moving towards financial analysis with cubes (and Reporting Services). I can see Excel having a role in that.