Re: stuck with WinForms issue, not sure how to proceed

Frank Bergmann <[email protected]> Thu, 19 Jun 2014 21:43:00 +0200
Newsgroups gmane.comp.gnome.winforms
Message-ID <[email protected]>
Try running your assembly like this: =


MONO_LOG_LEVEL=3Ddebug mono --trace TestJemForms.exe

this sets the MONO_LOG_LEVEL environment variable to debug, so you see what=
 native libraries are loaded. Adding the =97trace option will let you see w=
hat is being executed. (You could even add filtering there by namespace, so=
 you see only things that are interesting to you). =


for me your assembly ultimately crashed, as it was looking for some resourc=
e not bundled in your archive: =


[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Images\=
group.ico
  at System.Drawing.Image.FromFile (System.String filename, Boolean useEmbe=
ddedColorManagement) [0x00000] in <filename unknown>:0 =


Cheers
Frank

On Jun 19, 2014, at 8:10 PM, RhinoNY <[email protected]> wrote:

> Hi there,
> =

> I have a Windows Forms custom control assembly which I have authored that
> does not run under Mono and I=92m stuck trying to figure out why.  I have
> provided a link to the testbed exe and the DLL below.  Both target Framew=
ork
> 2.0.  The DLL has a custom splitter, group bar, and navigation bar that I
> have authored.
> =

> http://www.ryanrogers.com/monotest.zip
> =

> I have ran both the DLL and EXE through Mono Analyzer and there were no
> issues found.  Of course, I make no p/invoke calls or anything like that.
> =

> I have compiled under VS 2010 as well as Mono.  No warnings or errors
> compiling with either.  I used the CSC.exe syntax out from VS and ran it
> through the Mono compiler.
> =

> However, it doesn=92t matter whether I run the MS-compiled assemblies of =
the
> Mono-compiled assemblies.  In both cases I see a stack overflow warning
> (when run with =96verbose), and the UI never launches.
> =

> Everything runs fine using the MS runtime.
> =

> I have tried both the =93latest=94 and =93stable=94 builds of Mono, and g=
et the same
> result.
> =

> I=92m new too Mono, but a .Net veteran.  How do I get more info out of Mo=
no so
> that I can tell what is causing the problem?  =

> =

> I know it=92s my NavBar / GroupBar control that is causing the issue, as =
when
> I remove their creation from the testbed exe, it launches.  So something
> these controls are doing is causing an issue, but I have no idea what, and
> am not sure the best way to diagnose this using Visual Studio.  They are
> quite complex controls so I need some way to diagnose this.  Do I need to=
 be
> running MonoDevelop?  Was hoping to avoid that...
> =

> Are there some log files or logging options I'm overlooking?
> =

> Any help or pointers would be most appreciated!
> =

> Thanks,
> Ryan
> =

> =

> =

> =

> =

> --
> View this message in context: http://mono.1490590.n4.nabble.com/stuck-wit=
h-WinForms-issue-not-sure-how-to-proceed-tp4663153.html
> Sent from the Mono - WinForms mailing list archive at Nabble.com.
> _______________________________________________
> Mono-winforms-list maillist  -  [email protected]
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list

_______________________________________________
Mono-winforms-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-winforms-list