[Mono-bugs] [Bug 77673][Wis] New - Resgen does not properly encode a gif from a .ResX

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Feb 28 22:52:31 EST 2006

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by simon at nureality.ca.


--- shadow/77673	2006-02-28 22:52:30.000000000 -0500
+++ shadow/77673.tmp.16571	2006-02-28 22:52:31.000000000 -0500
@@ -0,0 +1,105 @@
+Bug#: 77673
+Product: Mono: Class Libraries
+Version: 1.0
+OS: GNU/Linux [Other]
+OS Details: 
+Status: NEW   
+Priority: Wishlist
+Component: Windows.Forms
+AssignedTo: peter at novonyx.com                            
+ReportedBy: simon at nureality.ca               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Resgen does not properly encode a gif from a .ResX
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem: Using prj2make to compile a System.Windows.Forms 
+application. Resgen is used I believe to convert the .resx file.
+Application compiles properly but on runtime the resource does not load 
+properly. Tested with different image formats besides the .GIF one 
+causing troubles and JPG's etc seemed fine.
+Steps to reproduce the problem:
+1. unzip
+2. make
+3. cd bin/Debug
+4. mono Resgen.exe
+Actual Results: 
+Unhandled Exception: System.Reflection.TargetInvocationException: 
+Exception has been thrown by the target of an invocation. ---> 
+System.ArgumentException: Invalid Parameter. A null reference or invalid 
+value was found.
+in <0x00084> System.Drawing.GDIPlus:CheckStatus (Status status)
+in <0x001e0> System.Drawing.Image:InitFromStream (System.IO.Stream stream)
+in <0x00103> System.Drawing.Bitmap:.ctor 
+(System.Runtime.Serialization.SerializationInfo info, StreamingContext 
+in <0x00000> <unknown method>
+in (wrapper managed-to-native) 
+System.Reflection.MonoCMethod:InternalInvoke (object,object[])
+in <0x0008d> System.Reflection.MonoCMethod:Invoke (System.Object obj, 
+BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] 
+parameters, System.Globalization.CultureInfo culture)--- End of inner 
+exception stack trace ---
+in <0x0010e> System.Reflection.MonoCMethod:Invoke (System.Object obj, 
+BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] 
+parameters, System.Globalization.CultureInfo culture)
+in <0x0001a> System.Reflection.MethodBase:Invoke (System.Object obj, 
+System.Object[] parameters)
+in <0x001e1> System.Runtime.Serialization.ObjectRecord:LoadData 
+(System.Runtime.Serialization.ObjectManager manager, ISurrogateSelector 
+selector, StreamingContext context)
+in <0x00110> System.Runtime.Serialization.ObjectManager:DoFixups ()
+in <0x00042> 
+ (System.IO.BinaryReader reader)
+in <0x000ab> 
+h (System.IO.BinaryReader reader, Boolean readHeaders, System.Object 
+result, System.Runtime.Remoting.Messaging.Header[] headers)
+in <0x0011f> 
+rialize (System.IO.Stream serializationStream, 
+System.Runtime.Remoting.Messaging.HeaderHandler handler)
+in <0x0000f> 
+ (System.IO.Stream serializationStream)
+in <0x00035> System.Resources.ResourceReader:ReadNonPredefinedValue 
+(System.Type exp_type)
+in <0x00321> System.Resources.ResourceReader:ReadValueVer1 (System.Type 
+in <0x0017b> System.Resources.ResourceReader:ResourceValue (Int32 index)
+in <0x00028> System.Resources.ResourceReader+ResourceEnumerator:get_Value 
+in <0x0008c> System.Resources.ResourceSet:ReadResources ()
+in <0x00049> System.Resources.ResourceSet:GetObject (System.String name, 
+Boolean ignoreCase)
+in <0x0007a> System.Resources.ResourceManager:GetObject (System.String 
+name, System.Globalization.CultureInfo culture)
+in <0x00010> System.Resources.ResourceManager:GetObject (System.String 
+in <0x00096> Resgen.Form1:InitializeComponent ()
+in <0x00013> Resgen.Form1:.ctor ()
+in (wrapper remoting-invoke-with-check) Resgen.Form1:.ctor ()
+in <0x00018> Resgen.Form1:Main ()
+Expected Results: Should load resource properly.
+How often does this happen? 
+Additional Information:
+I have included the prj2make Makefile already generated. Just simply need 
+to make.

More information about the mono-bugs mailing list