extending a click once application with plugins(deployment issue)

[krach.aran]

I'm creating a winforms click-once application that is plugin
enabled.
The application is working, and so are the plugins. but now i have
got the following problem:

after deployment i do not want to touch _ANY_ file of my deployment,
but i have got one directory that contains all the plugins.
As soon as the application starts i want to get all these dll's and
hook them up to the main application.

i've looked in to adjusting my manifest file's, referencing to the
dll's(which is the only working thing at the moment)

Does anybody know of a simple mechanism so i can deploy all dll's in a
single directory without adjusting my solution for every dll that i
want to copy ????

TIA

[Nicholas Paldino [.NET/C# MVP]]

What you want to do is in your ClickOnce manifest, you will mark the
add-in files as optional. Then, in your application, when you want to call
the DownloadFileGroup method on the ApplicationDeployment class in the
System.Deployment namespace.

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

<kr********@gmail.comwrote in message
news:11**********************@s48g2000cws.googlegr oups.com...

I'm creating a winforms click-once application that is plugin
enabled.
The application is working, and so are the plugins. but now i have
got the following problem:

after deployment i do not want to touch _ANY_ file of my deployment,
but i have got one directory that contains all the plugins.
As soon as the application starts i want to get all these dll's and
hook them up to the main application.

i've looked in to adjusting my manifest file's, referencing to the
dll's(which is the only working thing at the moment)

Does anybody know of a simple mechanism so i can deploy all dll's in a
single directory without adjusting my solution for every dll that i
want to copy ????

TIA