[MonoDevelop] [Fwd: Re: Non-writeable referenced assemblies]
casey.s.marshall at gmail.com
Mon Jul 28 21:17:44 EDT 2008
Casey Marshall wrote:
> -------- Forwarded Message --------
> From: Casey Marshall <cmarshall at pacificbiosciences.com>
> To: lluis at novell.com
> Cc: monodevelop-list <monodevelop-list at lists.ximian.com>
> Subject: Re: [MonoDevelop] Non-writeable referenced assemblies
> Date: Mon, 21 Jul 2008 12:26:05 -0700
> On Mon, 2008-07-21 at 13:48 +0200, Lluis Sanchez Gual wrote:
>> El dv 11 de 07 de 2008 a les 14:53 -0700, en/na Casey Marshall va
>>> One problem I've run into while running MonoDevelop is when a project
>>> references an assembly file that's read-only on the file system: when it
>>> gets copied to the object directory, the copy is read-only too, so you
>>> can't clean or rebuild the project.
>>> I've been using the attached patch to work around this; I don't know if
>>> there's a better way to handle this case.
>>> (and yeah, this is thanks to Perforce, where non-checked-out files are
>>> marked read-only on the file system)
>> What about changing the read-only flag after copying? looks easier to
>> implement a new copy loop.
> I think you mean "looks easier than," but yes, that's fine.
So, uh, how to you toggle the owner/write bit on a file in C#?
More information about the Monodevelop-list