[Mono-devel-list] Re: Fwd: Re: Question regarding the bug 52399

[Tiago Lima]

I found a nice workaround: using Assembly.GetTypes() and see if the type I am 
looking for is in there instead of relying on the Assembly.GetType(string) 
method...
It works fine now!! :)

Thanks for the help,
	Tiago Lima

On Saturday 20 December 2003 21:21, Ben Maurer wrote:
> It goes into mono/mono/metadata/icall.c
>
> grep in there
>
> -- Ben
>
> On Sat, 2003-12-20 at 16:14, Tiago Lima wrote:
> > This might be important...
> > I was hacking mono class code  (mcs from cvs) trying to figure it out how
> > to fix it but I found an internal function and stop there because I dont
> > know where to look next...
> >
> > Thanks,
> > 	Tiago Lima
> >
> > ----------  Forwarded Message  ----------
> >
> > Subject: Re: Question regarding the bug 52399
> > Date: Saturday 20 December 2003 20:50
> > From: Tiago Lima <tiago.lima at vianw.pt>
> > To: Ben Maurer <bmaurer at users.sourceforge.net>
> >
> > Ok, but the code is not recursive... :(
> > Do you have any idea of another way how to get a type from a dynamically
> > loaded assembly?
> >
> > Now, regarding the "urgency" I appologise because I didnt know what was a
> > "critical" bug, as it does not appear aside the dropdown box, and I chose
> > the first one by default... But I dont know... i am very very sorry.... I
> > only filed two bugs in Bugzilla...
> > The "urgent" mail the other day was an error of my part, I again
> > appologise.... I was trying finally to update a deployed site and that
> > bug appeared and I was very worried... Sorry about that...
> >
> > I'm currently migrating an application from windows (Microsoft .NET) to
> > linux (mono) and now it may mean that I begin coding "mono" because bugs
> > appear unexpectedly... :(  I really would like to help mono to grow.
> >
> > I had migrated a site to mono (:-)) before as a test for mono, because at
> > the time someone said it was production ready and thanks to Gonzalo and
> > all others (a big hug to them), I could place it online (with a few
> > setbacks still).
> >
> > It was a major bet that I won inside the company, that made them look
> > more into mono. I had placed my job on the line and I have survived with
> > your help. Now I have streached the line a bit and convinced them to
> > migrate all our apps to linux, and make mono our main platform.
> >
> > So the port begun, but while we are starting to port the core utils, hell
> > broke loose, and I'm in trouble again, I'm sorry if I bothered you or
> > others, the rest of the people is out on their weekends, buying Christmas
> > gifs, and I'm stuck here, so that mono doesn't look bad. My good fortune
> > is that Christimas is at the moment more important. :-)
> >
> > You see, if they believe a bit more in mono, I might convince them to
> > give a hand in something, but I have to port this applications or no
> > mono... (humm and my job, likelly...) :-(
> >
> > Thanks,
> > 	Tiago Lima
> >
> > On Saturday 20 December 2003 20:14, you wrote:
> > > On Sat, 2003-12-20 at 14:55, Tiago Lima wrote:
> > > > Hi,
> > > >
> > > > In the bug:
> > > > 	http://bugzilla.ximian.com/show_bug.cgi?id=52399
> > > >
> > > > In that case what is the workaround?
> > > > I want to dynamically load assemblies, how do I do this ?
> > >
> > > Just dont make it recursive.
> > >
> > > Really, the problem here is that you are marking all your reports
> > > urgent/critical/whatever. Though they may be urgent to *you* (and I
> > > agree, they very well may be), yelling and screeming just annoys the
> > > developers.
> > >
> > > Would you ever call the tech support for a major company and say
> > >
> > > `HELLO! I HAVE AN URGENT PROBLEM! I NEED THIS FIXED RIGHT NOW! ITS
> > > REALLY URGENT. WHEN I OPEN UP YAHOO.COM IT CRASHES.'
> > >
> > > At best, the representative would be annoyed, you probably wouldnt get
> > > much help.
> > >
> > > By marking your bugs all critical you are crying wolf. If you do
> > > someday find a critical bug (an example would be that someone made a
> > > change in CVS that caused a major regression), many people would filter
> > > you out.
> > >
> > > In general, for a bug to be marked Critical, Urgent, etc. it should:
> > >
> > >      1. Be affecting multiple people
> > >      2. Be a *major* regression
> > >
> > > Note, that for the most part, it must be either a huge bug in existing
> > > code, or a regression. It also must be *common*.
> > >
> > > I really do appreciate the time you are spending with mono, and your
> > > reporting of bugs. Please, let us help you by using bugzilla the way it
> > > was meant. If you mark bugs correctly, it will help developers allocate
> > > their time in the best possible manner.
> > >
> > > Thanks,
> > > Ben
> >
> > -------------------------------------------------------