Is the versioning scheme broken in SharedFrameworks?
Is the versioning scheme broken in SharedFrameworks?
- Subject: Is the versioning scheme broken in SharedFrameworks?
- From: Brant Vasilieff <email@hidden>
- Date: Mon, 29 Apr 2002 13:47:15 -0700
I've been experimenting with the framework versioning and it doesn't
seem to work reliably.
I created two frameworks with identical APIs. The only difference is
that the old version prints log messages in each of the methods.
So I compile two applications. App1 against version A 1.0.0 of the
framework, and app2 against version A 2.0.0 of the framework. In both
cases the appropriate framework is bundled within the shared frameworks
section of the application.
If I run them from the finder, app1 prints the log messages from version
1.0 or the framework. Yet, if I run them from within the debugger, it
correctly finds the newer compatible framework and runs without logging
the messages.
The final goal was to test what the documentation says is supposed to
happen, when a newer version of the framework is introduced to a system,
even within a bundled application.
I drag install app1 on a machine with no copies of the framework, and
run it. I get the log messages, as expected. Then I install app2 with
the newer framework version, and run it. It runs fine, with no log
messages. When I run the first app again, it is supposed to find the
newest version of the framework and use it. Yet, it continues to
display the log messages.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.