471,317 Members | 2,590 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,317 software developers and data experts.

Figuring out what dlls another dll requires

I have my auto update and auto update/ download new plugins system
working. The only thing I'm missing now is the ability to "uninstall"
plugins that are currently installed.

Currently I'm shutting down my app and running a batch file behind the
scenes to delete the dll that corresponds to the plugin which the user
wants to uninstall, however if that plugin came with any other dlls,
they are currently not removed. What I'd like to do is check what dlls
that plugin requires, then make sure none of the other plugins require
those dlls prior to making the batch file. I'd also like to do this
without relying on the plugin creator to make a config file which lists
these dependencies.

Is there any way to do this?
Dec 28 '05 #1
3 1216
Benny,

I don't think that this is a good idea. The reason for this is that the
plug in probably references DLLs that you have no business deleting.

For example, pretty much every assembly in existence has a reference to
mscorlib.dll. The second-most referenced is probably System.dll. Do you
want to delete these? You can't. In reality, for your plug ins, you should
make the requirement that the plug in have references to private assemblies
(in the same directory as it) and thats it. This way, you can just delete
the directory.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Benny Raymond" <be***@pocketrocks.com> wrote in message
news:u%***************@tk2msftngp13.phx.gbl...
I have my auto update and auto update/ download new plugins system working.
The only thing I'm missing now is the ability to "uninstall" plugins that
are currently installed.

Currently I'm shutting down my app and running a batch file behind the
scenes to delete the dll that corresponds to the plugin which the user
wants to uninstall, however if that plugin came with any other dlls, they
are currently not removed. What I'd like to do is check what dlls that
plugin requires, then make sure none of the other plugins require those
dlls prior to making the batch file. I'd also like to do this without
relying on the plugin creator to make a config file which lists these
dependencies.

Is there any way to do this?

Dec 28 '05 #2
Ya... I guess I never thought of the normal dlls that would be refrenced...

The main problem with seperate folders is that I required to set the
plugins up in the same domain as the program itself, which means that
the plugins folder is listed in the app.config inorder to load dlls from
there.

Guess I may have to rely on config files per plugin :(

Nicholas Paldino [.NET/C# MVP] wrote:
Benny,

I don't think that this is a good idea. The reason for this is that the
plug in probably references DLLs that you have no business deleting.

For example, pretty much every assembly in existence has a reference to
mscorlib.dll. The second-most referenced is probably System.dll. Do you
want to delete these? You can't. In reality, for your plug ins, you should
make the requirement that the plug in have references to private assemblies
(in the same directory as it) and thats it. This way, you can just delete
the directory.

Hope this helps.

Dec 29 '05 #3
Benny,

There is no reason to have to do that. Rather, why not have your folder
for the plugins and then have each plugin have its own sub-directory? That
would be better, and you wouldn't have to have a separate config file for
each plugin (rather, they can have their own settings in the config file).
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Benny Raymond" <be***@pocketrocks.com> wrote in message
news:uO**************@TK2MSFTNGP09.phx.gbl...
Ya... I guess I never thought of the normal dlls that would be
refrenced...

The main problem with seperate folders is that I required to set the
plugins up in the same domain as the program itself, which means that the
plugins folder is listed in the app.config inorder to load dlls from
there.

Guess I may have to rely on config files per plugin :(

Nicholas Paldino [.NET/C# MVP] wrote:
Benny,

I don't think that this is a good idea. The reason for this is that
the plug in probably references DLLs that you have no business deleting.

For example, pretty much every assembly in existence has a reference
to mscorlib.dll. The second-most referenced is probably System.dll. Do
you want to delete these? You can't. In reality, for your plug ins, you
should make the requirement that the plug in have references to private
assemblies (in the same directory as it) and thats it. This way, you can
just delete the directory.

Hope this helps.


Dec 30 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by darrel | last post: by
5 posts views Thread by Jesper Schmidt | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.