Assembly.Load() with strong name but no version!

[edge]

Is there any way to Assembly.Load() dynamically the DLLs of my project, with
their strong names, but without the need to specify a version? I just want
the public/private key to exist as a measure of safety for their
authenticity. I don't want to narrow down the valid DLLs to only those that
share the same version.

Because if later i decide to upgrade a DLL, I'll have to recompile and send
to the customer the WHOLE project, and not just the newer DLL, because its
version will differ from the others...

Thanks!

[David Levine]

If you know the path to the assembly you can use this...

Assembly.Load( AssemblyName.GetAssemblyName(assemblyPath));

Assembly.Load requires that the assembly be located in a folder where the
runtime can automatically resolve the assembly (e.g. in the same folder as
the executable).

"edge" <[e-mail]> wrote in message news:cp**********@usenet.otenet.gr...

Is there any way to Assembly.Load() dynamically the DLLs of my project,
with
their strong names, but without the need to specify a version? I just want
the public/private key to exist as a measure of safety for their
authenticity. I don't want to narrow down the valid DLLs to only those
that
share the same version.

Because if later i decide to upgrade a DLL, I'll have to recompile and
send
to the customer the WHOLE project, and not just the newer DLL, because its
version will differ from the others...

Thanks!

[Richard Blewett [DevelopMentor]]

Of couse you don't need to deploy the whole project, you could send the new assembly along with a publisher policy that peformed a version redirection

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

If you know the path to the assembly you can use this...

Assembly.Load( AssemblyName.GetAssemblyName(assemblyPath));

Assembly.Load requires that the assembly be located in a folder where the
runtime can automatically resolve the assembly (e.g. in the same folder as
the executable).

"edge" <[e-mail]> wrote in message news:cp**********@usenet.otenet.gr...

Is there any way to Assembly.Load() dynamically the DLLs of my project,
with
their strong names, but without the need to specify a version? I just want
the public/private key to exist as a measure of safety for their
authenticity. I don't want to narrow down the valid DLLs to only those
that
share the same version.

Because if later i decide to upgrade a DLL, I'll have to recompile and
send
to the customer the WHOLE project, and not just the newer DLL, because its
version will differ from the others...

Thanks!

[David Levine]

True, but publisher policy files must be installed in the GAC. If the
assembly is located local to the application then the version binding
redirect can be done locally in the application configuration file. If
dynamically loaded then neither is needed though the option is still there
if needed.

"Richard Blewett [DevelopMentor]" <ri******@NOSPAMdevelop.com> wrote in
message news:%2****************@TK2MSFTNGP10.phx.gbl...

Of couse you don't need to deploy the whole project, you could send the
new assembly along with a publisher policy that peformed a version
redirection

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

If you know the path to the assembly you can use this...

Assembly.Load( AssemblyName.GetAssemblyName(assemblyPath));

Assembly.Load requires that the assembly be located in a folder where the
runtime can automatically resolve the assembly (e.g. in the same folder as
the executable).

"edge" <[e-mail]> wrote in message news:cp**********@usenet.otenet.gr...

Is there any way to Assembly.Load() dynamically the DLLs of my project,
with
their strong names, but without the need to specify a version? I just
want
the public/private key to exist as a measure of safety for their
authenticity. I don't want to narrow down the valid DLLs to only those
that
share the same version.

Because if later i decide to upgrade a DLL, I'll have to recompile and
send
to the customer the WHOLE project, and not just the newer DLL, because
its
version will differ from the others...

Thanks!