Crash at exit when embedding Visio in WPF

[b.alex]

Hi,

I've embedded the Visio drawing control in a WPF app. It runs fine, but when
I exit, I get a crash: "The instruction at '0x734eb17a' referenced memory at
'0x734eb17a'. The memory could not be 'read'.

The interesting thing is that this crash only happens if, in the project's
Debug properties, 'Enable the Visual Studio hosting process' is checked and
'Enable unmanaged code debugging' is not checked. If both are checked or
neither are checked, the crash does not happen.

Has anyone else seen this? Has anyone else solved it?

Thank you,
Bob Alexander

 

[AlEdlund]

I just ran a test on some sample code and it appears to work for me. There
were some issues at one time that were discussed with Visual Studio and
trust setups.

http://blogs.msdn.com/mailant/archive/2005/04/22/411042.aspx

al

 

[AlEdlund]

While I'm thinking of it (and to possibly help others who might be able to
assist you), what version of Visio and what Visual Studio are you using?
(fix packs, service packs, etc.) Can you compile and run the example project
in the VisioSDK for the activex drawing control (I understand it is WinForms
and not WPF but it goes to compile options)?
al

 

[BobA]

I have Visual Studio 2008, version 9.0.30729.1 SP; Microsoft .NET Framework
3.5 SP1; Visio 2007 (12.0.6423.1000) SP2 MSO (12.0.6425.1000).

I'll have to give the example project a try.

Thanks.

- Bob

 

[AlEdlund]

Bob,
I'm pretty much the same. I put an example over on Chris Roth's site. The
primary difference is that it is a v2010 activex control but that should be
easy enough to change.

http://visguy.com/vgforum/index.php?topic=1324.0

al

 

[b.alex]

OK, I tried running the OfficePlanSample in the Visio SDK and I get the exact
same error - right down to the address that can't be read. Again, the error
only happens if 'Enable the Visual Studio hosting process' is checked and
'Enable unmanaged code debugging' is not checked.

Any ideas?

Thank you,
Bob

 

[AlEdlund]

well that pretty much eliminates your code as the source of the issue and
falls to either v2007 or vs2008 as the source. Do you have any add-ins
loaded in visio that might be interacting with it (check the trust center)?
al