RE: Visual Studio .NET projects and CVS
Dror == info-cvs-admin [EMAIL PROTECTED] writes: Dror Hi,=20 I think I need to clarify myself a little, what am I Dror looking for is not a Visual Studio (.NET) plugin for CVS. Dror My team is working on an Intranet project and using Visual Dror Studio .NET. While we where looking at the source directory Dror in order to decide what goes to the repository and what Dror should be left outside (local files created by the VS) we Dror noticed a large number of files that we could not decide Dror their purpose or the effect of managing them in the Dror repository. I'm looking for someone who has succeeded in Dror managing such project with CVS.=20 Thanks, Dror Hi, In addition to source code and header files, I only manage the .sln and .vcproj files. These, of course, are text files. The solutions and projects build the same way every time. Depending on your apps, the .config files may also need to be managed in cvs. HTH, Rob ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Visual Studio .NET projects and CVS
Title: RE: Visual Studio .NET projects and CVS Hi, I think I need to clarify myself a little, what am I looking for is not a Visual Studio (.NET) plugin for CVS. My team is working on an Intranet project and using Visual Studio .NET. While we where looking at the source directory in order to decide what goes to the repository and what should be left outside (local files created by the VS) we noticed a large number of files that we could not decide their purpose or the effect of managing them in the repository. I'm looking for someone who has succeeded in managing such project with CVS. Thanks, Dror -Original Message- From: Oliver Marx [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 27, 2002 8:04 PM To: Dror Braznitzki Subject: RE: Visual Studio .NET projects and CVS igloo -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dror Braznitzki Sent: 27. oktober 2002 18:02 To: Info CVS at GNU (E-mail) Subject: Visual Studio .NET projects and CVS Hi, Has anyone managed to manage a Visual Studio .NET project using CVS ? There are so many files that I have no idea if to put in the ignore list or not. Any help will be very appreciated. 10X, Dror ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. [EMAIL PROTECTED] **
RE: Visual Studio .NET projects and CVS
Dror Braznitzki wrote: [...] decide what goes to the repository and what should be left outside (local files created by the VS) Not terribly familiar with recent revisions of Visual C++, but in previous versions (e.g. 5.0 and 6.0), there were really only two files that needed to be checked in (the project and workspace files - foo.dsp and foo.dsw). Everything else was generated (*.ncb, which was the static analysis database for symbol browsing, *.pdb which was the program database, *.pch, which was the precompiled header database, etc.). -Original Message- From: [EMAIL PROTECTED] [mailto:info-cvs-admin;gnu.org] On Behalf Of Sent: Monday, October 28, 2002 3:26 AM To: Info CVS at GNU (E-mail) Subject: RE: Visual Studio .NET projects and CVS Hi, I think I need to clarify myself a little, what am I looking for is not a Visual Studio (.NET) plugin for CVS. My team is working on an Intranet project and using Visual Studio .NET. While we where looking at the source directory in order to decide what goes to the repository and what should be left outside (local files created by the VS) we noticed a large number of files that we could not decide their purpose or the effect of managing them in the repository. I'm looking for someone who has succeeded in managing such project with CVS. Thanks, Dror -Original Message- From: Oliver Marx [mailto:oliver;tekk.dk] Sent: Sunday, October 27, 2002 8:04 PM To: Dror Braznitzki Subject: RE: Visual Studio .NET projects and CVS igloo -Original Message- From: [EMAIL PROTECTED] [mailto:info-cvs-admin;gnu.org]On Behalf Of Dror Braznitzki Sent: 27. oktober 2002 18:02 To: Info CVS at GNU (E-mail) Subject: Visual Studio .NET projects and CVS Hi, Has anyone managed to manage a Visual Studio .NET project using CVS ? There are so many files that I have no idea if to put in the ignore list or not. Any help will be very appreciated. 10X, Dror ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. [EMAIL PROTECTED] ** ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Visual Studio .NET projects and CVS
On Mon, 28 Oct 2002, Dror Braznitzki wrote: Hi, I think I need to clarify myself a little, what am I looking for is not a Visual Studio (.NET) plugin for CVS. My team is working on an Intranet project and using Visual Studio .NET. While we where looking at the source directory in order to decide what goes to the repository and what should be left outside (local files created by the VS) we noticed a large number of files that we could not decide their purpose or the effect of managing them in the repository. Knowing what files are primary objects that should be version controlled is a Visual .NET problem, not a CVS problem. It's your responsibility to understand the development tool you are using, and know what all the .dsw, .opt, .ncb, .aps and whatever files mean. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Visual Studio .NET projects and CVS
Kaz Kylheku wrote: Knowing what files are primary objects that should be version controlled is a Visual .NET problem, not a CVS problem. It's your responsibility to understand the development tool you are using, and know what all the .dsw, .opt, .ncb, .aps and whatever files mean. So that means no asking for help? Sheesh! If you want to just jump somebody's case, do it for something legitimate, like sending HTML email to a mailing list. I have successfully rebuilt Visual projects with nothing more than a *.dsp or *.dsw file, as of Visual Studio 6, but have not tried with .NET. I have also archived all the files, and that worked fine, too. My general rules for archiving projects from development environments that produce mystery files: 1) Examine each file with a text editor. Do NOT use a text editor that autosaves to the original file. Do NOT use a text editor that cannot handle binary data. I use emacs and never have a problem. It should be immediately obvious if this is a binary file. If so, add it as binary. 2) Add the remaining files as text individually. If CVS feels that the file may be binary, abort the add and add it as Unicode. This is especially relevant for Microsoft-on-Microsoft development systems such as the Visual line. 3) If you are working in a read-only-by-default configuration, do `cvs edit` on all such files. 4) Just do your work as usual, and check in all the changed files as updates before doing any reference tags. This methodology has a few niceties: 1) You need know nothing about which files are what. 2) If you need to go back to a certain tag, your development environment will go back with you (sometimes this may not be so good). 3) You can highly customize the development environment, using branches to develop features, and get the customizations for each branch. Of course, you need to trade off the value to your team of these niceties with the cost of archiving them before deciding which you would like to do. HTH, /|/|ike ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
