[MonoDevelop] Perforce problem with MonoDevelop

Ian Norton-Badrul ian.norton-badrul at thales-esecurity.com
Wed Aug 4 02:32:24 EDT 2010

Hi Troy,

I use perforce and MD alot at work too, You can get around your
read-only for un-edited (p4 edit) files by working in two ways,

1. p4 edit your whole solution

$ cd Solution
$ p4 edit ...
##  work work, edit edit
$ p4 revert -a ...  # revert files with no changes
$ p4 add new_files
$ p4 submit


2. switch off perforce's read-only mode 

$ p4 client

# set workspace Options field to include 
# "allwrite" instead of "noallwrite"

I perfer variations of #1, In my monodevelop I also have an external tool
setup to run p4 edit and p4 add on files, but usually have to manually
p4 edit at least the solution and csproj files before starting work.

I also have a perforce plugin for monodevelop about 25% done but I'm
currently planning on looking into how well the new git vcs plugin works
with p4-git to get at perforce

Best Regards


On Tue, Aug 03, 2010 at 05:39:07PM +0100, Krogerma at aol.com wrote:
>    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.
>    We are planning to introduce our development process and tools (incuding
>    MonoDevelop) to our team very soon. The team is quite large and we'd like
>    to make it painless as possible for them to adopt the new workflow which
>    is necessary for our cross-platform application.
>    We are wondering if this is the desired behavior of MonoDevelop and if
>    not, whether there are plans to address this problem.
>    Sincerely;
>    Kurt Matis
>    Troy, NY

Content-Description: ATT1360933.txt
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list

Ian Norton-Badrul
Software Engineer
+44 1223 723 600

Thales e-Security Limited is incorporated in England and Wales with company
registration number 2518805. Its registered office is located at 2 Dashwood
Lang Road, The Bourne Business Park, Addlestone, Nr. Weybridge, Surrey KT15

The information contained in this e-mail is confidential. It may also be
privileged. It is intended only for the stated addressee(s) and access to it by
any other person is unauthorised. If you are not an addressee or the intended
addressee, you must not disclose, copy, circulate or in any other way use or
rely on the information contained in this e-mail. Such unauthorised use may be
unlawful. If you have received this e-mail in error, please inform us
immediately on +44 (0)1223 723600 and delete it and all copies from your
system.  Commercial matters detailed or referred to in this e-mail are subject
to a written contract signed for and on behalf of Thales e-Security Limited.                                 

More information about the Monodevelop-list mailing list