I have a situation where I am running 2 copies of VS 2003. One copy is debugging 2 applications at the same time and the other
copy is debugging a 3rd application.

The 2nd application (.net remoting client) connects to the 1st application (.net remoting server) via remoting. Two way channels
for events are setup and (mostly) operational. Both of these are running under copy 1 of VS.

The 3rd application connects (via TCP/IP Socket) to the 1st application and then the 1st application (server) fires .net remoting
events to the 2nd application which in turn calls remote methods on the 1st application. Application 3 is running under its own
copy of VS and continues to pass data back and forth to the 1st application using TCP/IP sockets.

I get this mess in a situation where the 2nd application (a multi-threaded windows forms application) will hang (not respond to
mouse etc) and at the same time the debugger (VS copy 1 that is debugging the remoting apps) will hang (not responding to mouse
etc). If I wait long enough (probably around 5 mins), the debugger will start responding some, but will not do anything to the
hung program. Before or after the debugger wakes up, a click of the close X on the windows form will result in the not responding
message and saying yes to terminate will USUALLY terminate the application. I don't really know if the application is hanging VS
or VS is hanging the application.

I suspect that I have all sorts of issues with the event callbacks from the server to the client and UI thread issuers, but it is
unreasonable for VS to hang.

I noticed some previous posts concerning virus scanners interfering with VS debugging.
1) - Nothing has changed in that area in about 1 year other than new virus definitions.
2) - The hang only occurs after I create the 2nd CAO in from the client
3) - I am using NAI Virusscan Enterprise
4) - Other programs being debugged to not hang including the 2nd copy of VS

I am running on Windows 2000 server with a hyper threaded processor. The server application (1st application) is configured to
use the multi-processor/server version framework runtime.

Any ideas on how to resolve either the application hang or the VS hang?

Thanks
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.

Hi Roy,

[quoted text, click to view]


Does this problem occur in a clean-boot machine?

Many VS.NET debugging problems could be caused by an anti-virus software in
the system, and sometimes only shuting-down the anti-virus software doesn't
still work, I suggest you may completely uninstall it and test the
debugging again...

By the way, does your application work alright outside the VS.NET IDE?


Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

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

Yes, the application does work outside of the IDE and it also works if I do NOT have breakpoints in a certain code path.
The code path in question is in remoting. By that I mean that if I set a breakpoint in the server code that is called by the
client, then things get totally hung up. If I don't have those breakpoints, things run fine.

I am not even going down the anti-virus path. It does not really matter if it works without anti-virus or not or if it works on a
clean boot machine or not. These are not usable development environments and what does matter is that your code (VS) does work in
a reasonable and industry accepted development environment.

If you want to pursue this based on the remoting code path issue, I will assist but I do not have the time to chase clean boot and
anti-virus ghosts because I can not run that way, so it does not matter if those issues make it work or not.

[quoted text, click to view]
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.

Hi Roy,

Since your programs could work well outside the IDE, I think there may be
some anti-virus software caused such problem, and from my experience the
anti-virus software does matter the VS.NET's debugger in many other
scenarios, so this is why I suggest you take a test in a clean-boot
machine, is it possible for you to perform this in a Virtual PC environment.

Meantime, I have checked this problem in our internal database, but did not
find a similar case, and also consulted our corresponding product team
members, they have no idea about such problem neither.

So in current stage, it is better if one of our PSS support engineers could
work with you. This may need you submit a support incident in Microsoft PSS
(Product Support Service). As a MSDN subscriber, you have two free support
incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.

For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at
http://support.microsoft.com/d-efault.aspx?scid=fh;EN-US;Offe-rProPhone

If there is anything unclear, please feel free to post here. We are glad to
be of assistance.


Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

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