[MonoDevelop] Non-writeable referenced assemblies
cmarshall at pacificbiosciences.com
Mon Jul 21 15:26:05 EDT 2008
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.
More information about the Monodevelop-list