Hey Avi,
The strong name is a good solution not becouse of its uniqueness, but
becouse of the fact that it gives you additional "goodies" that come as a
part of the package deal :)
- ability to register it in the GAC,
- ability to check if the assembly hasn't being tampered with (by checking
the hash).
- and others
About the redirections - they are possible in both cases - with or without
strong name usage. You can find good examples about binding redirect at the
MSDN - check out
http://msdn.microsoft.com/library/de...direction.asp; http://msdn.microsoft.com/library/de...blyBinding.asp
and
http://msdn.microsoft.com/library/de...permission.asp
Cheers,
Branimir
--
Branimir Giurov
MCSD.NET, MCDBA
www.sofiadev.org
"Avi" <Av*@discussions.microsoft.com> wrote in message
news:D1**********************************@microsof t.com...
I have a c# .NET application. V15 & V16
I have a DBAccess DLL assembly. V15 & V16
I want the .Net Application V15 will work with V15 DBAccess.dll
I want the .Net Application V16 will work with V16 DBAccess.dll
Is there a way to do it without SN key's ?
is SN key is the best way to handle it ?
I thought that I will simpy be able to write in web.config work with
DBAcess V 15.0.0.* but I couldnt fined any example to that.
Tanks,
Avi