System.Executio nEngineExceptio n

[John O'Neill]

Hi

I have been having a strange problem with a c# application I have been
developing. My application detects when a Pocket PC device has been
connected (via ActiveSyc) and queries the registry on the device to find out
the Device ID and whether or not any of our Pocket PC applications have been
previously installed on it so we can notify users if updates are available
etc. Every now and again though, a System.Executio nEngineExceptio n is thrown
and my application terminates without warning! I haven't managed to find out
what part of my code causes this abnormal termination as it seems to occur
randomly.

I have done a few searches for "System.Executi onEngineExcepti on" and one
article of interest is a Microsoft Knowledge Base post:
http://support.microsoft.com/?kbid=327106 BUG:
Some Marshal Class APIs Throw System.Executio nEngineExceptio n If You Pass a
Pointer, ByRef, or Array Type

The MS knowledge base article states that this is a known bug affecting .NET
Framework 1.0 & 1.1

Now I don't know anything about the Marshal Class API, or writing unmanaged
code, but I am using the OpenNETCF.org Desktop.Communi cation Libray wrappers
for RAPI to read the registry on the PPC device and there seems to be some
marshalling going on in there.

I then decided to download the .NET Framework 1.1 Service Pack 1 Tech
Preview to see if that resolved my problem - and it did! So it would seem
that the bug has been fixed, but this still leaves me with a problem - I
can't release my software until the .NET Framework Service Pack 1 is
officially released later in 2004!

Does anybody have any ideas for a workaround until the SP 1 final release is
available?

Thanks

John

[Kevin Yu [MSFT]]

Hi John,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that a known issue in .NET framework
prevents you from releasing your application. If there is any
misunderstandin g, please feel free to let me know.

Since this issue will be fixed in .NET framework 1.1 SP1, it is recommended
that you contact Microsoft PSS for it. If you have business impact on it,
they might provide you with a hotfix on this free of charge. You can find
contact information from the following link:

http://support.microsoft.com/default.aspx?scid=sz;[ln];top

HTH. If anything is unclear, please feel free to reply to the post.

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