Thanks Alex,
Is there a time when you wouldn't want to put ApplicationDomain.currentDomain
in the IModuleInfo.load call?
Freundliche Grüße / Best regards,
Bill Franklin
Computer Integrated Mfg.
[cid:image001.gif@01CD16F9.19A16DD0]
Bayer CropScience LP
8400 Hawthorne Road, Room 2447
Kansas City,
Actually, you have four commonly used options whenever a parameter or property
is of type ApplicationDomain:
null
new ApplicationDomain()
ApplicationDomain.currentDomain
new ApplicationDomain(ApplicationDomain.currentDomain)
New ApplicaitonDomain() will never work for modules.
Thanks...I think that clears it up.
So, if I am understanding correctly, for consistency, I should call .load(new
ApplicationDomain(ApplicationDomain.currentDomain)); for module loads inside of
modules, and from inside the main application as well (since apparently that is
the same thing that h
I seem to remember 4.6 being a bit lacking in that respect, try adding it
anyway, compiling and seeing if it works. I think it should.
Yes, that is correct.
On 4/10/12 8:49 AM, "Bill Franklin" wrote:
Thanks…I think that clears it up.
So, if I am understanding correctly, for consistency, I should call .load(new
ApplicationDomain(ApplicationDomain.currentDomain)); for module loads inside of
modules, and from inside the m
5 matches
Mail list logo