Embedding a resource at runtime
in [Visual C]
|
Prev: Help Using WinDBG
Next: IOCTL_DISK_CREATE_DISK
From: Dave Brown on 6 Jun 2006 11:31 Hi there. Does anyone know if it's possible to embed a new resource into an assembly at runtime as well as update an existing (assembly) resource. Any assistance would be appreciated. Thanks.
From: Nicholas Paldino [.NET/C# MVP] on 6 Jun 2006 11:47 Dave, Do you want to do this to an assembly that is loaded in the runtime? If that is the case, then this is not possible. Changing the assembly at runtime is a bad, bad idea. If you need to manage resources (and I use this term not in the .NET space, but as a general term) in a dynamic manner, then you should have some sort of storage solution to do that. Hope this helps. -- - Nicholas Paldino [.NET/C# MVP] - mvp(a)spam.guard.caspershouse.com "Dave Brown" <no_spam@_nospam.com> wrote in message news:Ol4pG5XiGHA.5036(a)TK2MSFTNGP04.phx.gbl... > Hi there. Does anyone know if it's possible to embed a new resource into > an assembly at runtime as well as update an existing (assembly) resource. > Any assistance would be appreciated. Thanks. >
From: Dave Brown on 6 Jun 2006 12:06 > Do you want to do this to an assembly that is loaded in the runtime? If > that is the case, then this is not possible. Changing the assembly at > runtime is a bad, bad idea. If you need to manage resources (and I use > this term not in the .NET space, but as a general term) in a dynamic > manner, then you should have some sort of storage solution to do that. > > Hope this helps. Thanks for the feedback. In my particular case however, adding and updating resources in the assembly (exe) itself would have been the simplest way to go for my users. I wanted to avoid dealing with extraneous file(s) that is and just ship one ".exe". Perhaps a religious issue but the specialized nature of my application actually lends itself to this technique (it involves the processing of resources). Since it's not doable however I'll have to package them up another way. In any case, thanks again (appreciated).
From: Nicholas Paldino [.NET/C# MVP] on 6 Jun 2006 12:13 Dave, It's one thing to process resources in an assembly that you actually don't load in the CLR, but to do it in an assembly already loaded in the CLR, that's just not feasible. -- - Nicholas Paldino [.NET/C# MVP] - mvp(a)spam.guard.caspershouse.com "Dave Brown" <no_spam@_nospam.com> wrote in message news:%23QVttMYiGHA.4512(a)TK2MSFTNGP04.phx.gbl... >> Do you want to do this to an assembly that is loaded in the runtime? If >> that is the case, then this is not possible. Changing the assembly at >> runtime is a bad, bad idea. If you need to manage resources (and I use >> this term not in the .NET space, but as a general term) in a dynamic >> manner, then you should have some sort of storage solution to do that. >> >> Hope this helps. > > Thanks for the feedback. In my particular case however, adding and > updating resources in the assembly (exe) itself would have been the > simplest way to go for my users. I wanted to avoid dealing with extraneous > file(s) that is and just ship one ".exe". Perhaps a religious issue but > the specialized nature of my application actually lends itself to this > technique (it involves the processing of resources). Since it's not doable > however I'll have to package them up another way. In any case, thanks > again (appreciated). >
From: Dave Brown on 6 Jun 2006 12:29
> It's one thing to process resources in an assembly that you actually don't > load in the CLR, but to do it in an assembly already loaded in the CLR, > that's just not feasible. I really didn't think so since updating a running executable isn't normally viable as you said (but I'm fairly new to .NET so I chanced it). Do you know off-hand how it can be done for an assembly that isn't currently loaded (without relying on command line tools if possible - I normally prefer to avoid shelling out to launch external utilities). Thanks. |