WinForms Application Deployment

[Mythran]

All library assemblies get installed into {cf}\CompanyNam e\Assemblies
All executable assemblies get installed into
{cf}\CompanyNam e\Products\Prod uctName

What do I need to do so that the executable assemblies can see the
configuration files that are in the ProductName directory and use the class
library assemblies located in the Assemblies directory (some sort of
configuration change)?

Thanks,
Mythran

[Richard]

If you really want the Assemblies directory at or above the installed
product directory - aka suggesting that the Assemblies are shared across
products - then you will need to add codeBase elements to your app.config
file for each shared assembly. Codebase is documented here:

http://msdn.microsoft.com/library/de...rfCodeBase.asp

If the assemblies are not shared across products but you want them in a
seperate directory for organizational purposes then - if you're Ok placing
the assembly directory under the product install directory - you can add a
single privatePath probing element to your app.config and place the
assemblies in a subfolder, probing is documented here:

http://msdn.microsoft.com/library/de...grfProbing.asp
"Mythran" wrote:

All library assemblies get installed into {cf}\CompanyNam e\Assemblies
All executable assemblies get installed into
{cf}\CompanyNam e\Products\Prod uctName

What do I need to do so that the executable assemblies can see the
configuration files that are in the ProductName directory and use the class
library assemblies located in the Assemblies directory (some sort of
configuration change)?

Thanks,
Mythran

[Mythran]

If the assemblies are not shared across products but you want them in a
seperate directory for organizational purposes then - if you're Ok placing
the assembly directory under the product install directory - you can add a
single privatePath probing element to your app.config and place the
assemblies in a subfolder, probing is documented here:

http://msdn.microsoft.com/library/de...grfProbing.asp

Aye, found that... thanks :)

Mythran

[Mythran]

If the assemblies are not shared across products but you want them in a
seperate directory for organizational purposes then - if you're Ok placing
the assembly directory under the product install directory - you can add a
single privatePath probing element to your app.config and place the
assemblies in a subfolder, probing is documented here:

http://msdn.microsoft.com/library/de...grfProbing.asp

Aye, found that... thanks :)

Mythran