I trying to write
something like container for objects, wich will be available through
remoting. I want implement hot deploying - when new version of assembly
(with some descriptor) appears in some folder, container unload old
version of assembly and loads new version (like application servers in
Java). But I can unload assembly only if it loaded in another
AppDomain. I tried to create separate AppDomain for every assembly,
but I can't access objects through remoting, as channel (HttpChannel in
my case) should be registered in every AppDomain and channels cannot
share same tcp port.
Is there exist any ways to implement hot deploying in .Net
Here
- http://blogs.msdn.com/mohammadakif/archive/2005/12/26/507416.aspx - I
found mention about something named "Indigo". What is it Will it be
remoting extensions to make
hot deploying simpler
Remoting and hot deploying
Hot Topic
- Code serialization in custom control
- Get a value from an SQL database into a Session Variable
- How to copy new data from server to a local database.
- Incorrect structure size of RasConnStatus
- How to create a new test Certificate ?
- Use .net dll in VB6?
- How do you generate <T> or (of T) using codeDom
- Plural of word
- Reading files from Temporary Internet Files directory
- could not find localhost when creating new project
.NET Development
- Serializing an object to send through remoting
- OPENXML: Error inserting xml into SQL Server 2000
- The type or namespace name 'SqlConnection' could not be found
- Setting DNS suffix through .NET?
- delete a row from an xml file using DataView
- HELP ACCESS DB , ASP.NET and a whole lot of pain
- adding resources dynamically
- Overwrite one section of binary file
- Ndoc dead link
- C# - OleDb - Access(MDB) : storing and retrieving images
Remoting and hot deploying