Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / CLR / June 2004

Tip: Looking for answers? Try searching our database.

Supporting .NET libraries version consistency

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ostap Radkovskiy - 01 Jun 2004 10:27 GMT
Hi!

How can I achieve the situation like that:
there is some application (.NET) and it is using some class library
(strongly named, installed by .msi, registered within GAC). I'd like to have
a crash on my client application when the class library version differs from
the one compiled with my application earlier e.g. my_app_version1 and
my_class_lib_version1 works fine but my_app_version1 and
my_class_lib_version2 cause crash.

I have one approach but it doesn't fit my scheme: to pool all the assembly
strings out of code to .config file and supply them with version numbers
(then my class factories will not be able to instantiate some objects
because there will be a different version)

Thanks in advance for any advises/suggestions!
Ostap Radkovskiy - 01 Jun 2004 12:01 GMT
Now I've got the other point  - to restrict application working with only
certain lib version - e.g. I have some library installed, I'm building my
project with that library although my project should work with it's older
version. The project compiles successfully (no interface differences), but
acutally there is an error prone situation because my project is expecting
to execute the older functionality of the library. Here I'd like to get an
error saying "wrong library/component version"

Any ideas?

> Hi!
>
[quoted text clipped - 12 lines]
>
> Thanks in advance for any advises/suggestions!
Richard Lander - 17 Jun 2004 16:02 GMT
I sounds like you want your application to hard-bind to a particular
version of an assembly and that you'd like a fatal error to occur in the
case that the application cannot find the particular version needed. This
how the loader already works. Are you seeing different behaviour?

Are you using publisher policy or binding redirects?

thanks -- rich

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.