VS.NET pauses while loading symbols (CPVSBUILD)

[Pierre Arnaud]

Whenever I start my application using VS.NET integrated debugger, I observe
a pause of about 5 seconds after the Output window prints:

'...': Loaded 'C:\WINDOWS\SYSTEM32\OLE32.DLL', Symbols loaded.

and just before it prints:

'...': Loaded
'C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\diasymreader.dll',
No Symbols loaded.

I investigated the problem and realised that somehow, at this point, VS.NET
was trying to resolve the CPVSBUILD computer name on the network, using the
NetBIOS name service (NB NAME QUERY).

Can anybody out there (or at Microsoft) explain to me what this computer is
and why VS.NET desperately tries to access it when starting my application?
This makes the whole debugging process more painful.

Any insight greatly appreciated!

[Gregg Miskelly [MSFT]]

The problem is that the symbol information for diasymreader.dll tells the
debugger that it's symbols are on \\cpvsbuild\....\diasymreader.pdb. When
you debug a process which has diasymreader loaded, the debugger will try and
get the symbols for you. Unfortunately, this is not at all what you want.
There are two work around:

1. Edit your lmhosts file and edit it so that cpvsbuild has an address of
'127.0.0.1'
2. Using a hex editor, open diasymreader.dll and find \\cpvsbuild and change
it to some local non-existent path of the same length (i.e. replace '\\c'
with 'c:\')

Good luck,

Gregg

This posting is provided "AS IS" with no warranties, and confers no rights.

"Pierre Arnaud" <no-...@opac.ch> wrote in message
news:3cbe7b15$1...@news.bluewin.ch...