[p4] Simpler Perforce integration with Visual Studio 2005 / 2008

[Snellenberger, Reed]

We are using Gordon Tetlow's p4bindgen Perforce add-in [1], and it makes
the whole VS 2005 binding issue disappear by generating the MSSCCPRJ.SCC
files [2] that the plug-in uses to provide the source binding.  The
particular solution I'm working on contains around 70 projects, so
p4bindgen is a life-saver... 

The only issue we have remaining is the horrible performance of the
"Pending Checkins" window; we just avoid it altogether and use the
p4v/p4w clients directly.

[1]
http://public.perforce.com:8080/@md=d&cd=//guest/gordon_tetlow/&c=zR0@//
guest/gordon_tetlow/p4bindgen/?ac=83 
[2] http://msdn2.microsoft.com/en-us/library/bb165760(VS.80).aspx 


Reed Snellenberger
||| Senior Software Developer
Aspen Technology, Inc. ||| +1 (281) 504-3226 ||| fax: +1 (281) 584-4329
||| www.aspentech.com

> -----Original Message-----
> From: perforce-user-bounces at perforce.com [mailto:perforce-user-
> bounces at perforce.com] On Behalf Of Andrew Beatty
> Sent: Friday, December 07, 2007 5:54 PM
> To: perforce-user at perforce.com
> Subject: Re: [p4] Simpler Perforce integration with Visual Studio 2005
> / 2008
> 
> 
> Sure,
> 
> * SCC always chokes when you try to change the directory structure
> from the MS default. Getting it to accept any other directory
> structure is a constant hassle requiring an intimate knowledge of the
> right way in which to bind & unbind projects and files. For large or
> multplatform projects, the MS default directory structure just won't
> do.
> 
> * SCC keeps information about the version control system in the
> project files themselves (very bad idea), which with Perforce seems
> to  mean that when different people work on the same project they
> have binding issues esp. if their local directory is different and
> have to constantly unbind, deal with above problem, rebind, just to
> load the project.
> 
> So basically not usable.
> 
> 
> > Care to expand on issues?
> >
> > Give the incredibly bad implementation (by MS) of VS .net
> > integrations, though maybe improving somewhat since 2002... I have
> > thought of the opportunity for doing a (commercial) alternative.
> >
> > Robert
> >
> > > -----Original Message-----
> > > From: perforce-user-bounces at perforce.com
> > > [mailto:perforce-user-bounces at perforce.com] On Behalf Of Andrew
> > > Beatty Sent: 06 December 2007 08:55 To: perforce-user at perforce.com
> > > Subject: [p4] Simpler Perforce integration with Visual Studio 2005
> /
> > > 2008
> > >
> > >
> > > I've tried using p4scc but the VS SCC API is just not
> > > suitable for many reasons that I won't go into here.
> > >
> > > What I would like is a simple way to checkout, checkin and
> > > add C++ source files while working in VS, without using the
> > > SCC API, just like what has been done with the MS Word plugin
> > > in p4ofc.
> > >
> > > Does anyone know of a macro / VB program to do this ?
> > >
> > > Thanks,
> > > Andrew.
> > > _______________________________________________
> > > perforce-user mailing list  -  perforce-user at perforce.com
> > > http://maillist.perforce.com/mailman/listinfo/perforce-user
> > >
> >
> 
> 
> |----------------------------------------------
> |        Andrew Beatty,
> |        Singular Inversions Inc.
> |        abeatty at FaceGen.com
> |        604-730-1727 (PST)
> |        www.FaceGen.com
> |----------------------------------------------
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

This e-mail and any attachments are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify the sender and permanently delete the original copy and any copy of any e-mail, and any printout thereof.