Bootstrapping your Application's AppDomainManager

Gaaaac, gac, gac.

Marc Hoeppner — Fri, 09 Mar 2007 19:51:16 GMT

Gerade noch überlegte ich, wie man denn programmatisch eine gesignte Assembly in die GAC bekommen könnte,

re: Bootstrapping your Application's AppDomainManager

shawnfa — Fri, 29 Jul 2005 03:28:15 GMT

Actually debugging this is pretty easy now that I think about it. What you want to do is force the application to not relaunch itself. It will only relaunch itself if it sees that the AppDomainManager is not setup. So all you need to do is ensure that the debugger sets the environment variables before launching the app for the first time.

You could even set the variables, then launch your debugger, which would inherit them and pass them on to the debuggee.

-Shawn

re: Bootstrapping your Application's AppDomainManager

Brien — Thu, 28 Jul 2005 19:38:10 GMT

Shawn-

I was able to debug by throwing a Debug.Fail() into the code. It worked if I launched a new copy of DevStudio, but it caused DevStudio to hang if I tried to reuse the instance that launched the shim. It would be nice if there were some call like Debug.ConnectToParentDebugger() or the like.

Brien

re: Bootstrapping your Application's AppDomainManager

shawnfa — Wed, 27 Jul 2005 23:07:50 GMT

Brien -- that's good feedback. The most obvious way I can think of is to use gflags tool that comes with the Debugging Tools for Windows. You can use that tool to setup a debugger that is launched whenever an application starts. This way when the second application is started, a second debugging session will also start.

-Shawn

re: Bootstrapping your Application's AppDomainManager

shawnfa — Wed, 27 Jul 2005 23:06:29 GMT

Leon -- in v2.0, you'll need to create an AppDomainManager which interacts and creates new AppDomains. If you set the Flags property on your AppDomainManager to RegisterWithHost, then you IHostControl::SetAppDomainManager callback will get called with a pointer to your AppDomainManager object. You can then QI for an interface that you define, and control AppDomains that way.

-Shawn

re: Bootstrapping your Application's AppDomainManager

Brien — Wed, 27 Jul 2005 20:25:46 GMT

Is there any way to do this so that it's debugger friendly? The code example prevents StartApplication from being debugged when you Run the app in the debugger since it is spawned as a new process.

Can the shim tell the debugger to start debugging the new process?

re: Bootstrapping your Application's AppDomainManager

Leon — Wed, 27 Jul 2005 19:20:40 GMT

Hi, we have a new interface in 2.0 to control the CLR: ICLRRuntimeHost. Earlier samples for CLR hosting used ICLRRuntimeHost::GetDefaultDomain/etc, but in beta 2 any AppDomain creation/manipulation is gone from that interface. How should one GetDefaultDomain/CreateDomain in .NET 2.0? I can't get both ICLRRuntimeHost and ICorRuntimeHost. Thanks for any pointers