Re: VSTO Security - cannot run or debug any VSTO documents
From: Peter Torr \(MS\) (ptorr_at_microsoft.com)
Date: 09/30/04
- Next message: Peter Torr \(MS\): "Re: Excel 2003 assembly"
- Previous message: Peter Torr \(MS\): "Re: FormulaLocal / FormulaR1C1Local not working"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 30 Sep 2004 10:06:19 -0700
"Cappy Popp" <CappyPopp@discussions.microsoft.com> wrote in message
news:FC2E20DF-4D09-4256-8A0B-713F74A4CDBF@microsoft.com...
> I can now at least *open* the .xls files without the security error;
> however, I still cannot debug them. Excel still flashes onscreen for a
> moment
> and then disappears. I never see the worksheet.
Hi,
Unfortunately you cannot debug an assembly hosted by the Whidbey CLR from
the Everett debugger; either you have to manually boot the Whidbey VS IDE
and attach to the process, OR you can use a configuration file to lock Excel
to the Everett CLR.
Place the configuration file in the same folder as Excel.exe and call it
Excel.exe.config.
Peter
-- Please post questions to the newsgroup - everyone benefits. This post is provided "AS IS" with no warranties, and confers no rights Sample code subject to http://www.microsoft.com/info/cpyright.htm Office / Security / Random weblog -- http://weblogs.asp.net/ptorr
- Next message: Peter Torr \(MS\): "Re: Excel 2003 assembly"
- Previous message: Peter Torr \(MS\): "Re: FormulaLocal / FormulaR1C1Local not working"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
