[p4] Perforce integration with VS .NET 2003

[Elkins, Mark]

We use VS.NET 2003 with Perforce extensively and do not have the any
problems like you describe.  Actually, since moving from VSS to Perforce
we have been very pleased with the SCC plug-in.  Web projects are the
only real catch, but there are workarounds for that problem.

That being said, if you are having binding problems, then I would check
that the client you use with the SCC-plug-in is correct.  If the
mappings in that client are correct, then VSS should have no trouble
binding the projects to Perforce.

Mark
 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Silgi, Nir
Sent: January 8, 2007 10:44 AM
To: perforce-user at perforce.com
Subject: [p4] Perforce integration with VS .NET 2003

Hi,

 

I wanted to ask if it's only me who is eating so much c#$% making
Perforce integrate with .NET 2003 IDE or is it something that is
commonly known.

Adding a solution with 20 projects is half hour work per developer, with
errors, crashes and whatnot. I still have projects which I try to bind
but simply nothing happens!! It really drives me crazy. I don't know if
I should blame Perforce, Visual Studio or the SCC plugin, I lean towards
VS because the integration with Eclipse works like a charm.

 

If anyone has experience with this, I will be more that happy to hear
about it, at least so I won't feel I'm alone in this :-)

 

Thanks,

 

NirS

 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user