Codebase to locate assemblies

[Guest]

I have placed my assemblies in different folders (as per project req.). I am
using config file with <codebase> option and registry with codebase option
(COM Interop) to enable the runtime to locate the assemblies. Will I face any
problems in future versions due to the usage of 'codebase' option? What
precautionary measures need to be taken if the 'codebase' option is used?

 

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

Tim,

I don't think you will have a problem in the future. I think that the
biggest problem is that you have to have your assemblies in a specific
location which can't change.

You could put your assemblies in the GAC (if appropriate), and that
might make deployment a little easier for you.

Hope this helps.

 

[Guest]

Thanks Nicholas for the immediate response. Regarding using the codebase
option to register the managed dll in the registry for COM Interop, will it
lead to DLL HELL kind of problems?



Also, Regarding using the <codebase> option in the config file, if I have to
change the path of the managed assemblies for a future deployment, can I just
change the path in the config file to make it work. Will there be any
problems of doing so?

Tim,

I don't think you will have a problem in the future. I think that the
biggest problem is that you have to have your assemblies in a specific
location which can't change.

You could put your assemblies in the GAC (if appropriate), and that
might make deployment a little easier for you.

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

I have placed my assemblies in different folders (as per project req.). I
am
using config file with <codebase> option and registry with codebase option
(COM Interop) to enable the runtime to locate the assemblies. Will I face
any
problems in future versions due to the usage of 'codebase' option? What
precautionary measures need to be taken if the 'codebase' option is used?