dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

Multiple VS.NET projects and CVS common sub directories

( CVSSCC )
Type: Public Status:Closed Created: 26 Apr 04 04:00 Updated: 26 Apr 04 04:00
--> Igor Pushkov (admin)  at 26 Apr 04 04:00 writes

VS .NET allows to isolate binding with SourceControl (CVS) based on
the project level. I.e. theoretically each project can be connected to
its own SourceControl server and path (CVSROOT and module).
However, by default, when you add entire solution to SourceControl, VS
.NET, without any prompts add entire solution and all sub projects
under the same module tree into repository. You can change this
behavior if will add solution to CVS project by project. This way you
will be able to specify for each project it's own source control
binding.
Later, when you will need to "reuse" some project in other solution
you can use "Add from source control" command, which will allow to add
project from any server location (that can be not part of solution
module).
Please only note that SourceControl granularity term is Project. You
cannot share same way single files or directories, only projects.
Let me know if this answer to your question.
--> pat (user)  at 26 Apr 04 04:00 writes

I have multiple VS.NET C# web apps that use some common directories with
*.ascx files. My current setup is that the primary solution folder and the
specifics are checked into a specific CVS module. The common directories
point to a common CVS module that other projects share. That way I've only
got one copy/module in CVS and fixing an ascx for one project automatically
fixes it for another as long as I do an update on the others. However, I've
noticed a problem adding new sub folders beneath the common folders. It
seems that in VS.NET it's adding the folder to the primary module of the
solution, not the parent directory of where the folder was added. Is there
a way for it to automatically add it to whatever module it's parent folder
is in?

Thank You
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9543319 visitor since 20 Jan 2003.
1664 visitors today and 2 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com