Adding existring project - VS.NET

( CVSSCC )

Type: Public Status:Closed Created: 20 May 04 05:00 Updated: 23 May 04 05:00

--> Owen W (user) at 23 May 04 05:00 writes

Thanks for your prompt and informative reposonse Igor!

After a few tries at scenario 2, i eventually decided just to try scenario
1 and it worked seamlessly :)

thanks again for your help

--> Igor Pushkov (admin) at 20 May 04 05:00 writes

Normally the better way is use IDE for initial adding. However you are
right, you have some specific case. I not sure which scenario is
better for your case. For me better use plug-in, but I really
experienced to work with it.
NOTE. I am see some probability that you will not manage this task with
one attempt. So best way first to try this with some test repository.
To do this:
1. Backup your existing sources as they is.
2. Create temporary CVS repository, or copy your existing to temporary
location. Access it locally (local protocol, or just the path name as
CVS ROOT). Back up it also.
Having this after unsuccessful attempt you can restore both your
sources, and clear repository. After you successfully manage this task,
restore initial sources and add them into real repository.
So now two scenarios:
1. Adding with plug-in
a) Open first solution and add it as is to CVS. Now any comments for
this, this should be processed automatically.
b) Open second solution. Exclude all common files (project from it).
Add it in this state.
c) Launch "Source control/Add project from source control" to add
previously deleted common projects again to second solution, but now from
CVS.
d) all
2. Adding with CVS import and then binding.
a) Add entire tree under "projects" to CVS.
b) open first solution. Select "Change source control". Choose there
common projects, and press "bind" button. Connect to CVS dialog
appears. Just press there ok.
c) In the same window now select solition 1 specific projects
(probably only solution). Press bind.
d) Then check in changed files. You will see them in pending checkins.
e) Open second solution. Probably at this point common project appears
as controlled. If this so repeat steep c for second solution. If not,
repeat steep b,c.
Let me know if this will not help.
Regarding wrappers. You setup it correct. However I just want to
notice that plug-in can work without this, as long as it have
automatic file type recognition procedure.

--> Owen W (user) at 20 May 04 05:00 writes

Hi,

First of all i'd like to point out that i did read the help file, i am just
unclear as to which way would be best
to add our project to CVS initially. I could import the solution via the
IDE, or i could import the files using
CVS import then bind later, the reason i am unclear is the directory
structure of our projects (there are 2 solutions
that share some common code).

We are using Visual Studio.NET w/ Visual Basic.

Our tree is similar to this :

/project
/project/src_common
/project/solution1/
/project/solution2/
/project/lib/

I want to have both solutions in CVS but it is important the the src_common
files are shared between
the two solutions still, so in my thinking, it would be better to go with
importing manually, otherwise
there might be conflicts when adding each solution through the IDE.

I did not try it yet as i dont want to get it wrong and find out later ;)

Also i have included the following in my cvswrappers file, could you tell
me if any of these
will cause a problem with Visual Studio, or if i am missing any?

All with -k 'b'

*.aps
*.bak
*.bpt
*.bro
*.bsc
*.cab
*.cdb
*.class
*.clw
*.dep
*.dll
*.doc
*.dpd
*.err
*.exe
*.exp
*.get
*.gid
*.gif
*.gz
*.idb
*.ilk
*.jar
*.jpeg
*.jpg
*.lib
*.licenses
*.licx
*.lnk
*.log
*.mdp
*.msi
*.mso
*.ncb
*.opt
*.out
*.pch
*.pdb
*.pfw
*.pjt
*.plg
*.png
*.ppt
*.res
*.resources
*.resx
*.sbr
*.scc
*.sit
*.sln
*.suo
*.suo
*.tar
*.tlb
*.tlh
*.tli
*.trg
*.vsd
*.wav
*.wmz
*.xls
*.zip

Many thanks,

Owen

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Adding existring project - VS.NET