VB.net "Split" function wants to do a context switch ??

[groleau]

Seg_Array = Split(String_X12N, Seg_Delim)

Last week, this code was working. Now, it consistently triggers an MDA pop-up which says

"The CLR has been unable to transition from COM context 0x18f650 to COM context 0x18f7a0 for 60 seconds. et cetera"

It does NOT wait sixty seconds. It is immediate upon clicking single-step on the Split line.

--
Wes Groleau

http://www.Parkview.com/

 

[SiriusBlackOp]

This looks to be a problem only while debuging.

Try disabling the MDA ContextSwicthDeadlock by placing this into the app.config file

  <mdaConfig>
    <assistants>
      <contextSwitchDeadlock enable="false" />
    </assistants>
  </mdaConfig>

For more info:

http://msdn2.microsoft.com/en-us/library/ms172233(VS.80).aspx

Senior Software Developer

http://www.scoutsft.com

 

[groleau]

I do not have an app.config file
(Or maybe the solution explorer is hiding it)
Do I create it? Where does it go?

thanks

--
Wes Groleau

http://www.Parkview.com/

 

[SiriusBlackOp]

This fix is for VS-2005... is that what you are using?

If so, it might be easier to test if this is acutally the problem first by using the registry editor (RegEdit from the command line)

Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
Value(Enable): "MDA"="1"
Value(Disable): "MDA"="0"

If it's not there then create it. Try setting it to 0 to disable it, build your project and run it again in debug.

Source:

http://msdn2.microsoft.com/en-us/library/d21c150d(VS.80).aspx

Senior Software Developer

http://www.scoutsft.com

 

[groleau]

The Registry has no MDA in that node.

I check the MSDN link you offered. At first, it just
seemed a pile of cryptic gibberish that an IRS bureaucrat
could be proud of.

But I studied it carefully, and if it is correct in
saying "falsely activated when all of the following
conditions are met" than I should avoid it by removing
one of those conditions. So I'll turn on
"unmamaged code debugging" and see what happens.

Thanks

--
Wes Groleau

http://www.Parkview.com/

 

[groleau]

unmamaged code debugging" did[/code] stop it.

I figured that as long as I do not step into a COM call,
I wouldn't notice the difference. Wrong! It seems
security is unmanaged, so you get a popup saying that
security debugging is not allowed and will be turned off.

But click OK, and the rest of it is no problem.

Thanks for the link!

--
Wes Groleau

http://www.Parkview.com/