[Mono-osx] [MonoMac] patch for MM-addin, Existing Framework

Michael Hutchinson m.j.hutchinson at gmail.com
Wed Jan 26 19:28:33 EST 2011

On Wed, Jan 26, 2011 at 6:57 PM, Miguel de Icaza <miguel at novell.com> wrote:
>> I'm not sure about the symlinking, since the apps we build are
>> currently distributable without additional packaging steps, and
>> symlinking would break that. Frameworks won't really hurt build
>> iteration times if we fix it to to only copy frameworks when they
>> change.
> This is great!   I was under the assumption that we wiped out the
> resulting .app every time, as opposed to updating the contents.
> If that is the case, how do we deal with old, stale content that the
> user might have added (secret.png) and later realized it was a
> mistake, but accidentally shipping it?

We don't currently handle stale content. Cleaning or doing a rebuild
(clean+build) will wipe out and regenerate the whole app though, so
I'd recommend a rebuild before shipping. The same is true of content
in MonoTouch apps.

When we move to using MSBuild as our build engine for MonoMac and
MonoTouch projects, this will get handled by its "incremental
cleaning" support, which removes stale files automatically. I'd like
to do this as soon as I have time, now that we've stabilized MD's
MSBuild support for MonoDroid.

Michael Hutchinson

More information about the Mono-osx mailing list