Thanks for the reply.
My parameters ought to be decorated correctly since they are all generated
using impLib and aximp.
But maybe these tools made a mistake. I'll check on them again.
"Fábio Chicout" <(E-Mail Removed)> wrote in message
news:0E962400-0128-48FB-8FA2-(E-Mail Removed)...
> Hi Willy,
>
> Well, I've got this message when my parameters weren't decorated
> (atributes,
> out, in modifiers) correctly.
>
> "Willy Van den Driessche" wrote:
>
>> Hi,
>> i have a rather simple question with a large background. We have a huge
>> existing VB6 application consisting of 100+ VB6 com components. We are
>> rewriting this app in .NET. Since there is more than 30 man years in the
>> existing aplication, we are doing this step by step. In the meantime,
>> the
>> old components are hosted in the new .NET Winforms application. They all
>> behave in a similar way : they show a list of items and have a toolbar on
>> top of it. The grid and the toolbar are activeX controls, hosted on the
>> main screen of the .NET application. All components expose a COM class
>> with a common interface. These classes are instantiated by the .NET
>> application and passed to the grid. The grid displays fine and behaves
>> as
>> planned. However, when the popup menu of the grid is invoked to display
>> a
>> modal (COM) form. Here however things go wrong. On Windows XP the
>> application occasionally hangs. On Windows Vista the application crashes
>> 95% of the time with the exception :
>>
>>
>> ---> System.AccessViolationException: Attempted to read or write
>> protected
>> memory. This is often an indication that other memory is corrupt.
>> at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageA(MSG& msg)
>> at
>> System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.Uns
>> afeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32
>> dwComponentID, Int32 reason, Int32 pvLoopData)
>> at
>> System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
>> reason, ApplicationContext context)
>> at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
>> reason, ApplicationContext context)
>> at System.Windows.Forms.Application.RunDialog(Form form)
>> at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
>> at System.Windows.Forms.Form.ShowDialog()
>>
>> I can explain for 3 more pages but that's not the idea. We have tried
>> everything. *any* idea is welcome.
>>
>>
>>
>>
>> __________ Informatie van ESET NOD32 Antivirus, versie van database
>> viruskenmerken 4794 (20100121) __________
>>
>> Het bericht is gecontroleerd door ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>
> __________ Informatie van ESET NOD32 Antivirus, versie van database
> viruskenmerken 4794 (20100121) __________
>
> Het bericht is gecontroleerd door ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Informatie van ESET NOD32 Antivirus, versie van database viruskenmerken 4794 (20100121) __________
Het bericht is gecontroleerd door ESET NOD32 Antivirus.
http://www.eset.com
Similar Threads
