Prism and Click

Question

I wonder how others did Prism and Click Once.

In particular, if you have a / dll module that is used in several applications, how do you handle the update deployment for this / dll module? Do you need to open each application and click "Publish"?

In addition, sometimes the Prism application does not have links to the entire DLL used. It simply imports them through ModuleCatalog from the file. Because the project does not see these DLLs as links, it does not put them in their deployment. How do you click once to deploy random dlls?

To solve this problem, I tried to add all the DLLs that I used as a reference to my Shell project. But when I do the assembly, I don’t even copy all of them to the output directory, because he cannot see that they are used directly. This happens most often when the module is used only through IEventAggregator. This (of course) means that when I do the publication, these dlls are missing.

So can I use Click Once for Prism? Or is it too limited? Is there a better way?

Any advice is appreciated.

Answer 1

This document contains answers to some of the questions I asked (in particular, dynamic libraries).

http://msdn.microsoft.com/en-us/library/gg405497%28PandP.40%29.aspx

: , . (, - , .) .

Answer 2

, - , clickonce , , , A C.