Which files to import to WinCVS
-
I want to use WinCVS as my version control tool in the visual Studio 2003 .net. I do not want to use it in an integrated manner (Jalindi Igloo is often suggested but do not want to use this). I will run WinCVS as a separate program and check-in and out as required. What I want to know is which files will I have to import to allow me to reproduce a project? Some of the extensions taht may be cause for concern is *.resources, *.pdb, *.projdata, *.suo ... there is s along list but what to a really need? What I want to know is what i need to put int the .cvsignore file? Thanks, Liam
-
I want to use WinCVS as my version control tool in the visual Studio 2003 .net. I do not want to use it in an integrated manner (Jalindi Igloo is often suggested but do not want to use this). I will run WinCVS as a separate program and check-in and out as required. What I want to know is which files will I have to import to allow me to reproduce a project? Some of the extensions taht may be cause for concern is *.resources, *.pdb, *.projdata, *.suo ... there is s along list but what to a really need? What I want to know is what i need to put int the .cvsignore file? Thanks, Liam
Add only to your repository files that you can't recreate. To check, do a 'clean solution' before you start adding files. For more information on what each file extension signifies check msdn. If you are unsure whether a file type is binary, try opening it in a text editor - however wincvs is pretty smart and most of the time it will autodetect the correct settings. As a starting point, you should consider adding the following types as text: *.sln *.vcproj *.cpp *.cxx *.c *.h *.hpp *.hxx *.rc *.rc2 And the following types as binaries: *.ico *.bmp (and other image types) You can safely ignore: *.obj *.exe *.dll *.lib *.pch *.ncb *.suo *.idb *.pdb *.bsc *.ilk
-
Add only to your repository files that you can't recreate. To check, do a 'clean solution' before you start adding files. For more information on what each file extension signifies check msdn. If you are unsure whether a file type is binary, try opening it in a text editor - however wincvs is pretty smart and most of the time it will autodetect the correct settings. As a starting point, you should consider adding the following types as text: *.sln *.vcproj *.cpp *.cxx *.c *.h *.hpp *.hxx *.rc *.rc2 And the following types as binaries: *.ico *.bmp (and other image types) You can safely ignore: *.obj *.exe *.dll *.lib *.pch *.ncb *.suo *.idb *.pdb *.bsc *.ilk
Andrew, Thanks for the reply - that is very useful. I tried to to a clean but I could not find the menu option. Building in the Development Environment according to the help page I should be able to:- To clean the active project On the Build menu, choose Clean. But I don't have a Clean option. Any suggestions? By the way I am using Visual Studio 2003 .net Thanks
-
Andrew, Thanks for the reply - that is very useful. I tried to to a clean but I could not find the menu option. Building in the Development Environment according to the help page I should be able to:- To clean the active project On the Build menu, choose Clean. But I don't have a Clean option. Any suggestions? By the way I am using Visual Studio 2003 .net Thanks
LiamD wrote: I don't have a Clean option. Any suggestions? 'Clean Solution' is the third item in the build menu in a default install of Visual Studio 2003. If it isn't in the right place try customising your menus / toolbars