Comments for Advanced .NET Debugging http://dotnetdebug.net Because sometimes you need to dig deep! Thu, 20 Nov 2008 01:03:30 +0000 http://wordpress.org/?v=2.6.2 Comment on Runtime Callable Wrapper Internals and common pitfalls by Korry http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/459008463/ Korry Thu, 20 Nov 2008 00:14:32 +0000 #comment-23173 Hi Eran Thanks for reply To 1 yes I am passing the string array from vb.net to the Com. To 2 the com.dll is a 3rd party DLL supplied through Bentley Cad software. I dont know the threading model or what software it was written in. I do know that it was written pre .net days. I have asked Bentley for help but they just arent interested. This week I have installed the App on a Desktop PC and have had no problems, I have also installed it on a Laptop(Dell M6300) and again no problems Regards Korry Hi Eran
Thanks for reply
To 1 yes I am passing the string array from vb.net to the Com.
To 2 the com.dll is a 3rd party DLL supplied through Bentley Cad software.
I dont know the threading model or what software it was written in. I do know that it was written pre .net days.
I have asked Bentley for help but they just arent interested.
This week I have installed the App on a Desktop PC and have had no problems, I have also installed it on a Laptop(Dell M6300) and again no problems

Regards Korry

]]> http://dotnetdebug.net/2005/09/10/runtime-callable-wrapper-internals-and-common-pitfalls/#comment-23173 Comment on Running .NET 2.0 and 1.1 side-by-side by Eran Sandler http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/457141186/ Eran Sandler Tue, 18 Nov 2008 12:08:30 +0000 #comment-23017 You cannot use Visual Studio 2003 (which uses .NET 1.1) to debug a .NET 2.0 process. You can, however, use Visual Studio 2005 to debug a .NET 2.0 process that runs a .NET 1.1 DLL as long as you have the right symbols. You cannot use Visual Studio 2003 (which uses .NET 1.1) to debug a .NET 2.0 process.

You can, however, use Visual Studio 2005 to debug a .NET 2.0 process that runs a .NET 1.1 DLL as long as you have the right symbols.

]]> http://dotnetdebug.net/2006/01/02/running-net-20-and-11-side-by-side/#comment-23017 Comment on Runtime Callable Wrapper Internals and common pitfalls by Eran Sandler http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/457141187/ Eran Sandler Tue, 18 Nov 2008 12:04:54 +0000 #comment-23016 There are two possible problems: 1) I'm assuming the string you are passing is from .NET to the COM DLL, there might be some memory leak or a problem in the COM DLL that might cause memory corruption after a while. 2) You might be having some threading issues between the COM DLL and .NET. Do you know the threading model of the COM DLL? Do you know in what language it was written? There are two possible problems:

1) I’m assuming the string you are passing is from .NET to the COM DLL, there might be some memory leak or a problem in the COM DLL that might cause memory corruption after a while.

2) You might be having some threading issues between the COM DLL and .NET. Do you know the threading model of the COM DLL? Do you know in what language it was written?

]]> http://dotnetdebug.net/2005/09/10/runtime-callable-wrapper-internals-and-common-pitfalls/#comment-23016 Comment on Running .NET 2.0 and 1.1 side-by-side by JC http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/457141188/ JC Mon, 17 Nov 2008 16:11:32 +0000 #comment-22891 We have our main project complied in .net 1.1 using vs 2003 and one small section that is complied using vs 2008 and .net 2.0. When you have iis set to 2.0, it seems you can't debug the code that is still built in 1.1 using vs 2003 anymore? Is that correct? We have our main project complied in .net 1.1 using vs 2003 and one small section that is complied using vs 2008 and .net 2.0. When you have iis set to 2.0, it seems you can’t debug the code that is still built in 1.1 using vs 2003 anymore? Is that correct?

]]> http://dotnetdebug.net/2006/01/02/running-net-20-and-11-side-by-side/#comment-22891 Comment on ConstraintException - A helpful tip by Piektdienas krikumi - Ivara blogs http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/457141189/ Piektdienas krikumi - Ivara blogs Fri, 14 Nov 2008 09:31:54 +0000 #comment-22220 [...] Savukārt, tiem, kuriem vēl nākas strādāt ar DataSetiem un saprast, kas ir par iemeslu baismajai ConstraintException, varu ieteikt izlasīt šo nelielo padomu. [...] [...] Savukārt, tiem, kuriem vēl nākas strādāt ar DataSetiem un saprast, kas ir par iemeslu baismajai ConstraintException, varu ieteikt izlasīt šo nelielo padomu. [...]

]]> http://dotnetdebug.net/2006/07/16/constraintexception-a-helpful-tip/#comment-22220 Comment on Runtime Callable Wrapper Internals and common pitfalls by Korry http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/457141190/ Korry Fri, 14 Nov 2008 04:25:17 +0000 #comment-22209 Hi I have been searching for a solution to a RCW problem that I have. The app I have written is in vb.net and it accesses a com dll. The app can work fine just as I want and would expect but it will crash or hang occasionally when it accesses the com object. The more common of these calls/methods is for example iRet = oAccessMxSB.MFWFireMinor(strMinorCode, strFields1to10) iRet is a return code for errors etc strMinorCode is a string strFields1to10 is an array of strings The call works fine most of the time but occasionally the data in the string array gets corrupted. Such as StrFields(0) should be "CS00", but somehow the value the com object gets is nothing or just "CS". When this happens the com executes correctly but returns an error code which is returned in iRet. Other methods in the com call are less kind and just cause the software to hang. I have been looking at your web page on RCWs and wonder if it is what I should be looking at. I have tried lots of different things but am not getting any closer to a solution. Perhaps its not the com call thats the problem, and maybe its something else in my own .net code. I have also coded up try catch exceptions but this doesnt catch anything Any pointers, ideas etc would be welcome as I have been trying to find a solution off and on for the last couple of years. Regards Korry Hi
I have been searching for a solution to a RCW problem that I have.
The app I have written is in vb.net and it accesses a com dll.
The app can work fine just as I want and would expect but it will
crash or hang occasionally when it accesses the com object.

The more common of these calls/methods is for example
iRet = oAccessMxSB.MFWFireMinor(strMinorCode, strFields1to10)
iRet is a return code for errors etc
strMinorCode is a string
strFields1to10 is an array of strings

The call works fine most of the time but occasionally the data in the string
array gets corrupted. Such as StrFields(0) should be “CS00″, but somehow
the value the com object gets is nothing or just “CS”.
When this happens the com executes correctly but returns an error code which
is returned in iRet.
Other methods in the com call are less kind and just cause the software to hang.

I have been looking at your web page on RCWs and wonder if it
is what I should be looking at. I have tried lots of different
things but am not getting any closer to a solution. Perhaps its not the com
call thats the problem, and maybe its something else in my own .net code.
I have also coded up try catch exceptions but this doesnt catch anything

Any pointers, ideas etc would be welcome as I have been trying to find
a solution off and on for the last couple of years.

Regards Korry

]]> http://dotnetdebug.net/2005/09/10/runtime-callable-wrapper-internals-and-common-pitfalls/#comment-22209 Comment on Debug.Assert and ASP.NET (and other server applications) by Eugene http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/428434399/ Eugene Wed, 22 Oct 2008 02:10:52 +0000 http://dotnetdebug.net/?p=122#comment-19831 Nice article. Thanks. :) Eugene Nice article. Thanks. :) Eugene

]]> http://dotnetdebug.net/2008/09/08/debugassert-and-aspnet-and-other-server-applications/#comment-19831 Comment on Loading and using SOS from within Visual Studio by Kirill Osenkov : Kirill's Visual Studio Tips http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/428434400/ Kirill Osenkov : Kirill's Visual Studio Tips Tue, 21 Oct 2008 23:57:55 +0000 #comment-19820 [...] sos, !clrstack, !dumpheap, !gcroot, [...] [...] sos, !clrstack, !dumpheap, !gcroot, [...]

]]> http://dotnetdebug.net/2006/03/20/loading-and-using-sos-from-within-visual-studio/#comment-19820 Comment on “External component has thrown an exception” in ASP.NET by luka http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/423509993/ luka Thu, 16 Oct 2008 20:23:15 +0000 http://dotnetdebug.net/2007/05/21/external-component-has-thrown-an-exception-in-aspnet/#comment-19185 Thanks Isaiyavan! I have been suffering for a LOOOOOOOOOOOOOOOOOOOONG time TOO and you comment help Thanks Isaiyavan!

I have been suffering for a LOOOOOOOOOOOOOOOOOOOONG time TOO and you comment help

]]> http://dotnetdebug.net/2007/05/21/external-component-has-thrown-an-exception-in-aspnet/#comment-19185 Comment on When $addHandler is not working RTFM by labreaks http://feeds.feedburner.com/~r/CommentsForAdvancednetDebugging/~3/423509994/ labreaks Tue, 14 Oct 2008 20:23:14 +0000 http://dotnetdebug.net/2007/02/06/when-addhandler-is-not-working-rtfm/#comment-18964 Thanks, this is exactly what I was looking for. Thanks, this is exactly what I was looking for.

]]> http://dotnetdebug.net/2007/02/06/when-addhandler-is-not-working-rtfm/#comment-18964