A
Amitai
Hi,
(this is a phrased version of my other post)
I have an Exe AddOn for Visio written in C#.
The AddOn is run using the RUNADDONWARGS macro - everything is fine.
If I want to debug the AddOn, well:
I can run the AddOn and a regualr Exe, it surely works well, but then I have
to manually supply the context information, e.g. parameters, shape selection
and so forth - everything that similates the runtime environment.
I do not want to work this way.
I attached to the Visio process, set a breakpoint and then hoped the AddOn
will break at "main" once I activate the AddOn from the RUNADDWARGS command
(from within the "actions" section) .
However, it didn't happen. My breakpoint didn't work. The add-on executed
well but didn't stop at the breakpoint.
The other issue is security. I signed the AddOn assembly with a string name
key file but still Visio issues security warnings.
I would like to get over these problems. I wouldn't like to use AddIn (using
the QueueMarkerEvent) instead of the AddOn. I would like to remain as much
loosly coupled as possible from Visio so that other programmers (me
included) could not crash the whole solution but only their own AddOn.
Many many thanks
Amitai Palmon
Ectel ltd.
(this is a phrased version of my other post)
I have an Exe AddOn for Visio written in C#.
The AddOn is run using the RUNADDONWARGS macro - everything is fine.
If I want to debug the AddOn, well:
I can run the AddOn and a regualr Exe, it surely works well, but then I have
to manually supply the context information, e.g. parameters, shape selection
and so forth - everything that similates the runtime environment.
I do not want to work this way.
I attached to the Visio process, set a breakpoint and then hoped the AddOn
will break at "main" once I activate the AddOn from the RUNADDWARGS command
(from within the "actions" section) .
However, it didn't happen. My breakpoint didn't work. The add-on executed
well but didn't stop at the breakpoint.
The other issue is security. I signed the AddOn assembly with a string name
key file but still Visio issues security warnings.
I would like to get over these problems. I wouldn't like to use AddIn (using
the QueueMarkerEvent) instead of the AddOn. I would like to remain as much
loosly coupled as possible from Visio so that other programmers (me
included) could not crash the whole solution but only their own AddOn.
Many many thanks
Amitai Palmon
Ectel ltd.