Re: Relative Paths
Re: Relative Paths
- Subject: Re: Relative Paths
- From: Gordon Apple <email@hidden>
- Date: Sat, 05 Feb 2011 17:13:11 -0600
- Thread-topic: Relative Paths
Uh, that was "re-compile", not "recomplie".
What I'm trying to do is use the older version to create a CoreData database
in the old format, so I can test data migration in the new version of the
app, before fostering it on an unsuspecting public and wiping out their old
data files. (I hate hate mail.)
The problem seems to be that compiling the project does automatically
compile and include the current project data model. I do have complier
switches to allow me to delete the old database file for testing
start-from-scratch. Unfortunately, running the old version does not revert
to the old data model included in that project. I tried a slight change in
the model, then a change back. That seems to have triggered it, but then it
wouldn't migrate in the new version. Going back to the old version again
resulted in it trying to use the new data model.
What is the right way to force a recompile of the data model?
On 2/5/11 12:12 PM, "Gordon Apple" <email@hidden> wrote:
> I'm trying to re-complie an older version of my iPad app which I pulled off my
> backup disk. In spite of cleaning the project, it seems to be compiling using
> a newer version of my CoreData date model. The console is giving me messages
> that relate only to the newer data model. These projects are in parallel
> folders.
>
> My questions is why is this happening? Isn't the default to use everything in
> the folder containing the current project? All source paths I have checked
> relate to the correct folder. What do I need to reset?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden