1
Vote

Members sometimes do not get exported when needed

description

I ran into a small bug with the exporting. I'm attaching Microsoft.Xna.Framework.Game.dll. If you export it with FileGenerator, it almost works perfectly. Just one little thing.
 
It's not exporting the private EventHandler members "deviceCreated", "deviceDisposing", and a couple others from GraphicsDeviceManager, into the .cs file. The csproj wouldn't compile until I copied them in from the Reflector disassembly.
 
Note that when I do add those in and compile, I get a warning from the compiler that they are never assigned to (yet they are still referenced in the .cs file). Could that be the reason they do not get exported?

file attachments

comments

jasonrbock wrote Mar 2, 2009 at 9:21 PM

I'm not sure. FileGenerator is very "light-weight" in that I don't do much of anything other than write to a file what Reflector generates for the assemblies. So if Reflector doesn't generate this stuff for a type, I won't see it.

BTW I can't gen the files based on this assembly alone, I need other references. But PLEASE don't post all the other XNA assemblies as well :).

scottbilas wrote Mar 12, 2009 at 1:25 AM

Posting Microsoft.Xna.Framework.dll.

wrote Mar 12, 2009 at 1:25 AM

wrote Feb 21, 2013 at 10:37 PM