Profiling VSTO code
amaclean
Posts: 3
Trying to profile .net code that is built into Excel through the VSTO interops.
I am trying to do it by making Excel the executable,
Giving the Path as the path to where the Spreadsheet is
And giving the parameter as the fully qualified spreadsheet name (path and file name)
When the Excel starts, it finds the spreadsheet, but then there is an error that the code behind in the .\projectname_bin\ dir which is where the VSTO code is kept, can't be found.
Is the Path parameter working correctly when the profiler is launched?
I am trying to do it by making Excel the executable,
Giving the Path as the path to where the Spreadsheet is
And giving the parameter as the fully qualified spreadsheet name (path and file name)
When the Excel starts, it finds the spreadsheet, but then there is an error that the code behind in the .\projectname_bin\ dir which is where the VSTO code is kept, can't be found.
Is the Path parameter working correctly when the profiler is launched?
Comments
are you using VS.NET 2005 or 2003? We have tested that this should work with 2005, but I recall that there were problems with 2003.
Thanks,
Tom Harris
Red Gate Software