Use Case
| • | You want to create and deploy a new application based on the CC Framework. |
Remarks
There may be times when you want to completely deviate from the standard CC Workstation distribution and write your own CC based application. If that's the case, then there are a number of things that you must understand about how a CC application is deployed:
| • | If your application makes use of plugins and extension points, then your deployment must include at least the following: |
Path/File |
\common \ClearCanvas.Common.dll \log4net.dll \logs \plugins \YourPlugin1.dll \YourPlugin2.dll YourExecutable.exe YourExecutable.exe.config Logging.config |
| • | As of version 1.3, If you want to put all your assemblies in the same folder, you can now do so; you are no longer required to follow the above directory structure, although it is still recommended. If you want to follow the above directory structure, YourExecutable.exe.config must contain the XML below. The important part is the <probing> element, which tells .NET to look in the \common and \plugins folders for dependencies. |
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="common;plugins" />
</assemblyBinding>
</runtime>
</configuration>
| • | Make sure your installation directory (i.e., the directory in which your executable resides) does not contain any stray DLLs. This is a very common mistake because In Visual Studio, any referenced assemblies the executable has are automatically copied over. To prevent that, set the Copy Local property on each referenced assembly to false. |