asked on Load assembly to another domain in COM+ application
Hi all,
Few day ago, I have a question about how to load assembly to another application domain. Now I met another issue.
My main application is running in COM+. Right now, already succeed to load dynamic compiled assembly to new application domain create within COM+ session. But the problem is: When I unload the domain and wish to delete the loaded assembly, but I can't.
(1) In the normal application (not COM+), I have succeed to compiled a C# file in runtime to assembly, then create new app domain -> load compiled assembly to new domain -> invoke method -> unload domain -> delete compiled assembly -> successfully.
(2) In COM+ application, I have succeed to compiled a C# file in runtime to assembly, then create new app domain -> load compiled assembly to new domain -> invoke method -> unload domain -> but cannot delete compiled assembly -> exception: the file was used by another process.
When running in debug mode, I've found the main difference is:
In (1) C# file store in D:\test.cs -> compile to test.dll assembly -> test.dll stored in D:\test.dll (same directory with C# file).
In (2) C# file store in D:\test.cs -> main application place in D:\MainApp -> compile to test.dll assembly -> test.dll stored in D:\MainApp\bin\Debug\test.
I think this is the reason why I cannot delete the assembly file.
Anyone please help me.
Few day ago, I have a question about how to load assembly to another application domain. Now I met another issue.
My main application is running in COM+. Right now, already succeed to load dynamic compiled assembly to new application domain create within COM+ session. But the problem is: When I unload the domain and wish to delete the loaded assembly, but I can't.
(1) In the normal application (not COM+), I have succeed to compiled a C# file in runtime to assembly, then create new app domain -> load compiled assembly to new domain -> invoke method -> unload domain -> delete compiled assembly -> successfully.
(2) In COM+ application, I have succeed to compiled a C# file in runtime to assembly, then create new app domain -> load compiled assembly to new domain -> invoke method -> unload domain -> but cannot delete compiled assembly -> exception: the file was used by another process.
When running in debug mode, I've found the main difference is:
In (1) C# file store in D:\test.cs -> compile to test.dll assembly -> test.dll stored in D:\test.dll (same directory with C# file).
In (2) C# file store in D:\test.cs -> main application place in D:\MainApp -> compile to test.dll assembly -> test.dll stored in D:\MainApp\bin\Debug\test.
I think this is the reason why I cannot delete the assembly file.
Anyone please help me.
C#
Last Comment
dungla
In COM+ you need to deal with signed assemblies. By default a signed assembly cannot reference any not signed assembly.
ASKER
ptmcomp, what did you mean?
So how can I do this task?
So how can I do this task?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
set the CachePath of AppDomainSetup is mean the application will load assembly into the CachePath right? Did you mean when I first compile my C# file (D:\test.cs) and return an assembly named test.dll into D:\MyApp\bin\Debug\test.dl
Yes, you're right. But first I would check why the assembly is still loaded and by what process. Is the debugger loading it and fooling you?
ASKER
ptmcomp,
I've got it :-), very simple. Before compile the C# file, set GenerateInMemory property of CompilerParameters to true, it will use the assembly in memory (not use in physical folder). Set AppDomainSetup.ShadowCopyF
CompilerParameters.Generat
CompilerParameters.OutputA
AppDomainSetup setup = new AppDomainSetup();
setup.ApplicationBase = AppDomain.CurrentDomain.Ba
setup.ShadowCopyFiles = "true";
AppDomain domain = AppDomain.CreateDomain("Se
// load assembly and execute
// unload domain
AppDomain.Unload(domain);
domain = null;
File.Delete (CompilerParameters.Output
Thank for your help
I've got it :-), very simple. Before compile the C# file, set GenerateInMemory property of CompilerParameters to true, it will use the assembly in memory (not use in physical folder). Set AppDomainSetup.ShadowCopyF
CompilerParameters.Generat
CompilerParameters.OutputA
AppDomainSetup setup = new AppDomainSetup();
setup.ApplicationBase = AppDomain.CurrentDomain.Ba
setup.ShadowCopyFiles = "true";
AppDomain domain = AppDomain.CreateDomain("Se
// load assembly and execute
// unload domain
AppDomain.Unload(domain);
domain = null;
File.Delete (CompilerParameters.Output
Thank for your help
Do you also delete the shadow copy?
ASKER
Yes I do, and thank again for your help