You pretty much have the picture... Usually when you manually load an
appdomain it is because you would like to manually unload it later... that
is not supported either (or unloading assemblies). Sounds like you have to
"Chris Walker" <ChrisWalker@newsgroup.nospam> wrote in message
news:e%23ii1d61EHA.1076@TK2MSFTNGP09.phx.gbl...
> So is there no way to create an AppDomain in which to create an object?
> As it stands right now, it seems that .NET CF only allows AppDomains to
> launch additional programs, basically.
>
> There is a project on the Internet (without source available) called
> NADABS which purports to do exactly this under .NET CF.
>
> Chris
>
> "Daniel Moth" <dmoth74@hotmail.com> wrote in message
> news:ew3qT841EHA.2624@TK2MSFTNGP11.phx.gbl...
>> CreateInstanceFromAndUnwrap is not supported on the CF. I believe you are
>> probably out of luck in this area.
>>
>> Cheers
>> Daniel
>> --
>>
http://www.danielmoth.com/Blog/ >>
>>
>> "Chris Walker" <ChrisWalker@newsgroup.nospam> wrote in message
>> news:O1rwoP21EHA.3336@TK2MSFTNGP11.phx.gbl...
>>> On the desktop, I can create an AppDomain and then load an assembly into
>>> it -- and then create a component in that appdomain and get a reference
>>> to it.
>>>
>>> With the compact framework, I can create an AppDomain and launch an
>>> executable in it.
>>>
>>> How can I load an assembly into an AppDomain under Windows CE, and then
>>> how can I create an instance of a component from that DLL?
>>>
>>> Under .NET, I would do something like:
>>> newAppDomain.CreateInstanceFromAndUnwrap(assemblyPath,
>>> "Project1.AppDomainTestComponent")
>>>
>>> Under .NET CF, I have no idea :)
>>>
>>> Chris
>>>
>>>
>>>
>>
>>
>
>