Hello,
I have created an AppDomain to load an Assembly, used Reflection on it
and then Unloaded the AppDomain. Is there any Remoting Issues
associated with Unloading of an Assembly. Iam getting exceptions.
AppDomain newDomain = AppDomain.CreateDomain("NewDoa
Hey,
You might be running into this one:
http://bugzilla.ximian.com/show_bug.cgi?id=27663
Zoltan
On 2/25/06, vijaya raghava mutharaju <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have created an AppDomain to load an Assembly, used
>
El sáb, 25-02-2006 a las 11:49 +0530, vijaya raghava mutharaju escribió:
>
>Hello,
>What went wrong ? Please tell me.
Hello !
I'm writting a little component framework, and i have to do assembly
unloading.
The component container, must inspect assemblies searching comp
Hi, Zoltan - That bug is different. There are similarities. Mine is related to communication between different AppDomains. My application is as follows:
1) Domain1 - Loading an assembly - SampleApplication.exe From next statement, the current domain starts.
Hi,
Try creating a simple test case and report it at our bug tracking
system, attaching the
test case.
Zoltan
On 2/26/06, vijaya raghava mutharaju <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> Zoltan - That bug is different. There are similaritie
Hi Zoltan,
I don't think it is a bug in Mono.Iam getting the same
exception in VS.NET also. It is bug in my code itself.
When I take the part of the code which creates a new AppDomain, does
reflection on it outside and put it in a separate file to check it,
Iam getting the same excep
Hi,
The assembly file should be in the current directory itself. It
cannot be in any other directory. If it is, then it should be either
strong named or put in GAC.
There is another problem. When Iam trying to use Mono.Cecil for
Step - 2 described above, Iam getting an exception that
Hi,
I was going through an MSDN article by Eric Gunnerson. He
says that if we want the runtime to probe for the assembly in any
other location then we should setup the ApplicationBase property of
AppDomainSetup class.By default, runtime will lock that assembly. So
we have to set the Shado
AFAIK, ShadowCopyFiles isn't implemented yet in Mono.
:|
On 2/27/06, vijaya raghava mutharaju <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was going through an MSDN article by Eric Gunnerson. He
> says that if we want the runtime to probe for the assembly in any
> other location then we should
Hi,
The issue is resolved. The mistake I have been doing was,
though I loaded the assembly into another AppDomain, I was
referencing(using Reflection) it in the CurrentDomain. Also I used
"MarshalByRefObject" in a wrong manner.
I thought it should be used by the Assembly Iam loa
10 matches
Mail list logo
