471,618 Members | 1,529 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,618 software developers and data experts.

Codebase to locate assemblies

Tim
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?
Dec 27 '05 #1
2 2112
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]
- mv*@spam.guard.caspershouse.com

"Tim" <Ti*@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
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?

Dec 27 '05 #2
Tim
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?

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


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?

"Nicholas Paldino [.NET/C# MVP]" wrote:
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]
- mv*@spam.guard.caspershouse.com

"Tim" <Ti*@discussions.microsoft.com> wrote in message
news:73**********************************@microsof t.com...
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?


Dec 28 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Ram | last post: by
7 posts views Thread by Ruslan Popov | last post: by
reply views Thread by Dinesh Upare | last post: by
2 posts views Thread by BentleyInc | last post: by
reply views Thread by Nikander & Margriet Bruggeman | last post: by
1 post views Thread by XIAOLAOHU | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.