The VideoLAN Forums

A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in System.Windows.Forms.dll


Lads & Gents,

Environment: Xp / VisualStudio 2005 / VideoLAN 0.8.6 (newest, own build from source code)
(it might have been the case with 0.8.5, too).

We encounter the problem in a simple stripped dowm 'Window-form' application (sample for tracing that bug.
A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in System.Windows.Forms.dll

That happens in the auto generated line with
''cli::safe_cast<System....''
...snip
this->Name = L"Form1";
this->Text = L"Form1";
this->Load += gcnew System::EventHandler(this, &Form1::Form1_Load);
(cli::safe_cast<System::ComponentModel::ISupportInitialize^ >(this->axVLCPlugin1))->EndInit();
this->ResumeLayout(false);
...snap

Wie also see two pieces in the studio´s tool.general chapter 'Choose items' as COM Components
VideoLAN VLC ActiveX Plugin v.1
VideoLAN VLC ActiveX Plugin v.2
same name, same location, same date.
It does not matter what we choose to implement, v1, v2, or both.
The objects appear correctly, but on start up, it gives that mentioned trouble.

Any (simple?) proposal / solution on hand ? Would be a great favour.
Many regards from The Netherlands - digi
and btw, did someone tell you, that xmas is coming up soon?

Do you have AxInterop.AXVLC.dll and Interop.AXVLC.dll in your output directory? Try deleting them and forcing VS 2005 to re-create them for you from the latest 0.8.6 ActiveX dll. And of course why not just install and try the pre-built binaries so you can tell if the problem is with your own build?

Be sure to register axvlc.dll by hand in either case before anything.

No further action required,...
...we live with that 'misfortune' so far.
It does not actually crash our application, though it looks pretty annoying.
When that case is solved, I will report it here.
Thank you, Tappen, whish you hell of a nice Christmas.

Do you have AxInterop.AXVLC.dll and Interop.AXVLC.dll in your output directory? Try deleting them and forcing VS 2005 to re-create them for you from the latest 0.8.6 ActiveX dll.
Well, I did that when the strippd down project was created completey from scratch.

And of course why not just install and try the pre-built binaries so you can tell if the problem is with your own build?
Yes, sure, I did that, too.

Be sure to register axvlc.dll by hand in either case before anything.
This I did not do yet, will keep an eye on that.