Visual Studio 2005. Debugging visio addin 2

[nbelyh]

Some time ago I have described the problem.

Visual Studio 2005. Debugging visio addin...
Why on the earth Visual Studio 2005 is starting desperate search for
Visio debug symbols in the internet each time I start debug session?

Some more info on the problem.
Actually it turned out that that I am having troubles with the fact
that
VISIO HAS HARDCODED REFERECES TO DEBUG SYMBOL FILES IN LAN IN EXE (!)

In particual, if you open Visio.exe or some visio .DLLs (say,
VISLIB.DLL), in notepad (!)
you can find the following reference to teh debug symbols. The actual
path depends on language and service pack, but it is always there (!)

\\daddev\visio\visio11.0\3216\Setup\x86\ship\files\pfiles\msoffice\visio11\visio.pdb
- or - [ after installing SP2 ] -
\\offlab\labs\visio\visio11\visio11.0\5509\Setup\x86\ship\files\pfiles\msoffice\visio11\visio.pdb

This file refers to a symbol in local network (!)
[that is obviously located in Redmond, no?]

And, as a honest guy, Visual Studio 2005
tries to search this \\offlab or \\daddev server in LAN when you start
debug session (!)

In Visio 12 this is:
t:\visio\x86\ship\0\visio.pdb

This sound much better!

Does anyone know,
is there a way to prevent Visual studio 2005 looking for servers
\\offlab or \\daddev ?

Regards, Nikolay.

 

[Roger]

Hello Nikolay

I had a similar, but not identical problem when using the Visio 2003 Drawing
Control. I'm not sure whether this will solve the problem you've encountered
but it may be worth checking out.

I found there was a delay of several minutes when the Visio 2003 ActiveX
control was loading except when there was no network connection or if access
was blocked by a software firewall. I believe the Visio Drawing Control tries
to verify if the certificate has expired. Below is a solution to stop Windows
from trying the verify if a certificated driver's certificate has expired:
* Start Internet explorer and click... Tools>Internet Options
* Click the Advanced tab, then scroll down to Security:
* Uncheck the boxes that say "Check for publishers certificate revocation"
and "Check for servers certificate revocation" (requires restart)

Best regards
Roger Billsdon

Some time ago I have described the problem.

Visual Studio 2005. Debugging visio addin...
Why on the earth Visual Studio 2005 is starting desperate search for
Visio debug symbols in the internet each time I start debug session?

Some more info on the problem.
Actually it turned out that that I am having troubles with the fact
that
VISIO HAS HARDCODED REFERECES TO DEBUG SYMBOL FILES IN LAN IN EXE (!)

In particual, if you open Visio.exe or some visio .DLLs (say,
VISLIB.DLL), in notepad (!)
you can find the following reference to teh debug symbols. The actual
path depends on language and service pack, but it is always there (!)

\\daddev\visio\visio11.0\3216\Setup\x86\ship\files\pfiles\msoffice\visio11\visio.pdb
- or - [ after installing SP2 ] -
\\offlab\labs\visio\visio11\visio11.0\5509\Setup\x86\ship\files\pfiles\msoffice\visio11\visio.pdb

This file refers to a symbol in local network (!)
[that is obviously located in Redmond, no?]

And, as a honest guy, Visual Studio 2005
tries to search this \\offlab or \\daddev server in LAN when you start
debug session (!)

In Visio 12 this is:
t:\visio\x86\ship\0\visio.pdb

This sound much better!

Does anyone know,
is there a way to prevent Visual studio 2005 looking for servers
\\offlab or \\daddev ?

Regards, Nikolay.

 

[nbelyh]

Hello, Roger.

* Start Internet explorer and click... Tools>Internet Options
* Click the Advanced tab, then scroll down to Security:
* Uncheck the boxes that say "Check for publishers certificate revocation"

No, this does not help (I have checked that before posting)

The actual problem is NOT that Visual Studio tries to
connect to the internet. The problem is that it tries to
RESOLVE addresses \\offlab and \\daddev. These addresses
are hardcoded in visio executalbe and some visio DLLs
as addresses of servers where Visio's debug symbols are.
These were obviously frozed in wehn visio was built in MS...

Before Visual Studio 2005, this PDB info seems to be ignored by VS...
Am I wrong?

Regards, Nikolay.