[MonoDevelop] Perforce problem with MonoDevelop

Lluis Sanchez Gual slluis.devel at gmail.com
Tue Aug 3 13:50:31 EDT 2010


El dt 03 de 08 de 2010 a les 12:39 -0400, en/na Krogerma at aol.com va
escriure:
> Dear monodevelop-list:
>  
> I'm a cross-platform consultant currently working under contract for a
> large company.
>  
> We are using MonoDevelop on Mac, SuseLinux and Windows. I must say
> that the tool is quite usable and has come a long way in the past
> couple of years since I used it last.
>  
> We are currently having an annoying problem with the Perforce version
> control system. When the Perforce client downloads files to the local
> workspace they are copied down as readonly files. It's quite often the
> case that we need to only work on one project or two within a
> solution. However, MonoDevelop seems to require that all ".csproj"
> files are writable if anything in the solution is changed. We've
> gotten around this problem by running scripts that change the
> permissions of all of the project files in the solution so that they
> are writable, then change them back before checkin to Perforce.

Can you please file a bug report for this problem? I'll see what can I
do.

Lluis.





More information about the Monodevelop-list mailing list