It's a feature of COM. :-}
Once you venture out of the .NET box and use unmanaged code you are potentially exposing yourself to the same old problems.
Are you using any COM objects (or third part .NET classes that do so) ?
Any direct Win API calls ?

As before, I'm not claiming those *are* the source of the problem - just that it you are using them then that should be the first place to look.
If you're not using COM then perhaps you can provide a bit more detail about when the error occurs.
When you say 'in development' do you mean when running the app in debug mode ?
What's the app? - Winforms, ASP.NET etc....


>O so this is a feature? And I thought that the "code and pray" days were behind us.
>
>My problems started when I added a New to one of my business classes. I have the intention to use excel, but surely, Viv, that does not count, does it :).
>
>Thanks.
>
>>>>I'm getting this error only in development, in certain circumstances.
>>>>
>>>>Should I worry? :)
>>>
>>>Yes. Check very long discussion
>>>http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/6adca20b-649f-41a4-8fa1-09534882d76c
>>
>>Certainly a long discussion. But only one post of any merit (James Kovacs , 9/18/2006) and one section in there that shows why most other suggested solutions were not solutions at all:
>>
>>"You will also see small changes (like changing compiler optimizations, or re-ordering instructions) cause code to start working. What you've done is mask the problem. The memory corruption is still occuring, it's just not occuring to a critical piece of memory such as a return address. You will likely see it re-appear later as you continue modifying the code"
>>
>>I'll bet Marc's problem stems from the use of a COM object ( I could lose but the odds are in my favour)