Source control problems
-
Hi, I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. On my laptop, I've created a web-project located on the local hard drive, lets call it http://work.domain.dk. All files are in, say, d:\wwwroot\work.domain.dk\homepage, except from the solution file which is in d:\wwwroot\work.domain.dk. I then submitted it to a VSS server (using the build-in feature in Visual Stuido 2003), which created a "work.domain.dk" folder with the subfolders "work.domain" and "work.domain.dk". (folders, as in VSS "folders") - holding respectively the solution file and the project files. Now I want to open that project on my desktop pc, and place the phycical files (the working copy ?) on a network drive on my dev. server which is reachable via http://work.domain.dk. All files are on the network drive, the IIS looks in that folder, the DNS pionts at the dev. server. Everything works just nicely - except I can't get VSS / Visual studio to open the project. Usually, when a project is opened where the files are placed e.g. on a network drive, you get a dialog stating that the files cant be reached throuhg \\blahbla\url-here. Then you just point visual studio to the files on the network drive, and it works. Next time you dont get this question so it must be stored somewhere. Anyway, I've copied all files to the right location (as I didn't know how to get it out of VSS correctly X| ) on my dev. server. I try to open the solution - and VSS asks me for a URL to the files. I enter http://work.domain.dk, and then it just gives me an error about not being able to find the files on the \\blahblah\url-here. But it doesn't allow me to point out the correct location. So I would very must like to enter this information the correct place first. Does anybody know where this is stored ? Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Do you have any recommandations regarding whether or not to use VSS ? Should we go for something else, or just wait for VS2005 (it's build-in, right ?) I'm going crazy here.. please help me a bit :-D Sigh.. /Jan Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
Jan R Hansen wrote: I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. Don't worry, no one can :) Jan R Hansen wrote: Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Don't use it. Simply put, VSS sucks. It's not client-server, so it is anything but safe. It's slow. It does not scale. It stores files in a proprietary format, and if its files become corrupt (and it occurs often), you're doomed. The file-locking model is a hassle. ("Hey, Joe, can you please release the lock on the file xyz.csproj?"). Branching is a joke. Readonly files are a creation of a sadistic. Damn, I don't want a tool to be in my way all the time. I only want to care about the source code control tool when I use it (checkin, checkout, update, branch and merge). I don't want to care about it everytime I need to do a minor change to a file. Why should the repository need to know where on the disk you put the files? What if I want to move the files on my disk, or, what if I use different drive letters on different machines? Ever tried a single VSS repository with 30 developers? Ever heard of ANALYZE.EXE? If not, run it and try not to faint when you read the results. Over a 256K VPN, a "get latest version" can easily take 20 minutes! Try to migrate your history to other SCC systems. You can't - although there are some ugly hacks that allow you to migrate it to CVS. Most decent SCC systems have straightforward, well documented file/database formats and an export/import tool to allow you to migrate data to other SCC systems. The only advantages I can see on using VSS is that it's tightly integrated into VS and that it does not need any setup, since it's installed with VS.NET. Next time, try using CVS, Subversion, Perforce, anything but VSS. Setting up other SCC systems will take you a day, but you'll recover it quickly. Yes, even I am blogging now!
-
Jan R Hansen wrote: I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. Don't worry, no one can :) Jan R Hansen wrote: Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Don't use it. Simply put, VSS sucks. It's not client-server, so it is anything but safe. It's slow. It does not scale. It stores files in a proprietary format, and if its files become corrupt (and it occurs often), you're doomed. The file-locking model is a hassle. ("Hey, Joe, can you please release the lock on the file xyz.csproj?"). Branching is a joke. Readonly files are a creation of a sadistic. Damn, I don't want a tool to be in my way all the time. I only want to care about the source code control tool when I use it (checkin, checkout, update, branch and merge). I don't want to care about it everytime I need to do a minor change to a file. Why should the repository need to know where on the disk you put the files? What if I want to move the files on my disk, or, what if I use different drive letters on different machines? Ever tried a single VSS repository with 30 developers? Ever heard of ANALYZE.EXE? If not, run it and try not to faint when you read the results. Over a 256K VPN, a "get latest version" can easily take 20 minutes! Try to migrate your history to other SCC systems. You can't - although there are some ugly hacks that allow you to migrate it to CVS. Most decent SCC systems have straightforward, well documented file/database formats and an export/import tool to allow you to migrate data to other SCC systems. The only advantages I can see on using VSS is that it's tightly integrated into VS and that it does not need any setup, since it's installed with VS.NET. Next time, try using CVS, Subversion, Perforce, anything but VSS. Setting up other SCC systems will take you a day, but you'll recover it quickly. Yes, even I am blogging now!
Daniel Turini wrote: Next time, try CVS So he would have bothered us in no earlier than two days, after walking through all the docs? ;P Integration with Visual Studio 6?
we are here to help each other get through this thing, whatever it is Vonnegut jr.
boost your code || Fold With Us! || sighist | doxygen -
Daniel Turini wrote: Next time, try CVS So he would have bothered us in no earlier than two days, after walking through all the docs? ;P Integration with Visual Studio 6?
we are here to help each other get through this thing, whatever it is Vonnegut jr.
boost your code || Fold With Us! || sighist | doxygen -
Daniel Turini wrote: Next time, try CVS So he would have bothered us in no earlier than two days, after walking through all the docs? ;P Integration with Visual Studio 6?
we are here to help each other get through this thing, whatever it is Vonnegut jr.
boost your code || Fold With Us! || sighist | doxygenpeterchen wrote: Integration with Visual Studio 6? While the idea behind CVS is controlling files, not projects (e.g., docs, images, etc), there are lots of free tools like this[^] that integrate CVS into VS. Since with CVS you don't need to keep checking in/out files only to be able to do minor changes to files, you tipically use it once or twice a day, and IDE integration is a feature less appealing. peterchen wrote: So he would have bothered us in no earlier than two days, after walking through all the docs? Setting up CVS is really hard for those without *nix experience, but it won't be more than one or two days. Anyways, once setup, you never will have problems again. BTW, what's the biggest team you saw accessing a VSS repository? Yes, even I am blogging now!
-
Jan R Hansen wrote: I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. Don't worry, no one can :) Jan R Hansen wrote: Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Don't use it. Simply put, VSS sucks. It's not client-server, so it is anything but safe. It's slow. It does not scale. It stores files in a proprietary format, and if its files become corrupt (and it occurs often), you're doomed. The file-locking model is a hassle. ("Hey, Joe, can you please release the lock on the file xyz.csproj?"). Branching is a joke. Readonly files are a creation of a sadistic. Damn, I don't want a tool to be in my way all the time. I only want to care about the source code control tool when I use it (checkin, checkout, update, branch and merge). I don't want to care about it everytime I need to do a minor change to a file. Why should the repository need to know where on the disk you put the files? What if I want to move the files on my disk, or, what if I use different drive letters on different machines? Ever tried a single VSS repository with 30 developers? Ever heard of ANALYZE.EXE? If not, run it and try not to faint when you read the results. Over a 256K VPN, a "get latest version" can easily take 20 minutes! Try to migrate your history to other SCC systems. You can't - although there are some ugly hacks that allow you to migrate it to CVS. Most decent SCC systems have straightforward, well documented file/database formats and an export/import tool to allow you to migrate data to other SCC systems. The only advantages I can see on using VSS is that it's tightly integrated into VS and that it does not need any setup, since it's installed with VS.NET. Next time, try using CVS, Subversion, Perforce, anything but VSS. Setting up other SCC systems will take you a day, but you'll recover it quickly. Yes, even I am blogging now!
thought so.... Actually, I once tried to set up a CVS system - but never got far. Then I was recommended Subversion, never got very far with that either. Are there any decent Windows-clients and / or VS integrated tools that run against Subversion ? Should I pefer that over CVS ? - they claim that they want to re-do CVS, just making it better... And then, just out of curiosity (spell check, please...) : How many of you know / have worked with "Continuus", these days known as "CM/Synergy" ? It's a source code control / configuration management system that took me 3 years of daily use as a developer to "understand". But now we're friends :) I have no illusions about being less than a year about setting that up.. and its probably extremely expencive... Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
-
peterchen wrote: Integration with Visual Studio 6? While the idea behind CVS is controlling files, not projects (e.g., docs, images, etc), there are lots of free tools like this[^] that integrate CVS into VS. Since with CVS you don't need to keep checking in/out files only to be able to do minor changes to files, you tipically use it once or twice a day, and IDE integration is a feature less appealing. peterchen wrote: So he would have bothered us in no earlier than two days, after walking through all the docs? Setting up CVS is really hard for those without *nix experience, but it won't be more than one or two days. Anyways, once setup, you never will have problems again. BTW, what's the biggest team you saw accessing a VSS repository? Yes, even I am blogging now!
Daniel Turini wrote: you never will have problems again Until you try to checkin a binary file type that it does not recognise! ;) Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
peterchen wrote: Integration with Visual Studio 6? While the idea behind CVS is controlling files, not projects (e.g., docs, images, etc), there are lots of free tools like this[^] that integrate CVS into VS. Since with CVS you don't need to keep checking in/out files only to be able to do minor changes to files, you tipically use it once or twice a day, and IDE integration is a feature less appealing. peterchen wrote: So he would have bothered us in no earlier than two days, after walking through all the docs? Setting up CVS is really hard for those without *nix experience, but it won't be more than one or two days. Anyways, once setup, you never will have problems again. BTW, what's the biggest team you saw accessing a VSS repository? Yes, even I am blogging now!
Not to sound OSBashing, but here is exactly where the "Open Source Model" fails. I know the pains of VSS inside out (Team of 5). if there would be a tool that provides simple no-think migration to CVS, people woud abandon VSS like lemmings a cliff. There is a market. it is an ugly market, since it's a one-time-tool, however, this is a busines problem solved before. So there is a market. there is a set of tools, that need integration, and there is some development work to do. But it's simply not happening. What *does* happen is that I can hire an expensive consultant for the price of a high performance SCS, who sets up everything and vanishes, and leaves me with a vital system I haven't set up, configured, or understood. regarding CVS, for one I'm a bit uneasy on the "merge thing" (maybe because that's really crappy in VSS). Second, after installing comes retraining, and for such a vital tool it must be "instant". It took our new developer an introductory session of 30 minutes (including explanation of the project structure), plus foud or five short questions over two days to work with VSS smoothly. How long with CVS?
we are here to help each other get through this thing, whatever it is Vonnegut jr.
boost your code || Fold With Us! || sighist | doxygen -
Not to sound OSBashing, but here is exactly where the "Open Source Model" fails. I know the pains of VSS inside out (Team of 5). if there would be a tool that provides simple no-think migration to CVS, people woud abandon VSS like lemmings a cliff. There is a market. it is an ugly market, since it's a one-time-tool, however, this is a busines problem solved before. So there is a market. there is a set of tools, that need integration, and there is some development work to do. But it's simply not happening. What *does* happen is that I can hire an expensive consultant for the price of a high performance SCS, who sets up everything and vanishes, and leaves me with a vital system I haven't set up, configured, or understood. regarding CVS, for one I'm a bit uneasy on the "merge thing" (maybe because that's really crappy in VSS). Second, after installing comes retraining, and for such a vital tool it must be "instant". It took our new developer an introductory session of 30 minutes (including explanation of the project structure), plus foud or five short questions over two days to work with VSS smoothly. How long with CVS?
we are here to help each other get through this thing, whatever it is Vonnegut jr.
boost your code || Fold With Us! || sighist | doxygenpeterchen wrote: How long with CVS? I don't actually remember when I installed it, probably 5~7 years ago. peterchen wrote: So there is a market. there is a set of tools, that need integration, and there is some development work to do. But it's simply not happening. And there's a proprietary, undocumented file format. Have you heard about "vendor lock-in"? Other problem is that some concepts are highly different on both SCCs and there's no automated tool to do the migration. What we done is let the history on VSS and importing the whole code tree was done with a 'cvs import' after it was setup. Yes, even I am blogging now!
-
Hi, I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. On my laptop, I've created a web-project located on the local hard drive, lets call it http://work.domain.dk. All files are in, say, d:\wwwroot\work.domain.dk\homepage, except from the solution file which is in d:\wwwroot\work.domain.dk. I then submitted it to a VSS server (using the build-in feature in Visual Stuido 2003), which created a "work.domain.dk" folder with the subfolders "work.domain" and "work.domain.dk". (folders, as in VSS "folders") - holding respectively the solution file and the project files. Now I want to open that project on my desktop pc, and place the phycical files (the working copy ?) on a network drive on my dev. server which is reachable via http://work.domain.dk. All files are on the network drive, the IIS looks in that folder, the DNS pionts at the dev. server. Everything works just nicely - except I can't get VSS / Visual studio to open the project. Usually, when a project is opened where the files are placed e.g. on a network drive, you get a dialog stating that the files cant be reached throuhg \\blahbla\url-here. Then you just point visual studio to the files on the network drive, and it works. Next time you dont get this question so it must be stored somewhere. Anyway, I've copied all files to the right location (as I didn't know how to get it out of VSS correctly X| ) on my dev. server. I try to open the solution - and VSS asks me for a URL to the files. I enter http://work.domain.dk, and then it just gives me an error about not being able to find the files on the \\blahblah\url-here. But it doesn't allow me to point out the correct location. So I would very must like to enter this information the correct place first. Does anybody know where this is stored ? Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Do you have any recommandations regarding whether or not to use VSS ? Should we go for something else, or just wait for VS2005 (it's build-in, right ?) I'm going crazy here.. please help me a bit :-D Sigh.. /Jan Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
You just set a "working folder" and make a get latest of the solution file... Then open the solution file and let VS get all the remaining files/projects. Trust me, the problems is not with VSS it's with VS and Webprojects ;) When accessing the same webproject files from multible computers (like on a laptop and a workstation where it's the same files from your source control) it's important that the path to the web project (like c:\inetpub\wwwroot\someproject\) is the same or it will not work with VS on multible computers... If you get tired of VSS, try Vault[^]. - Anders My Photos
WDevs - The worlds first DSP, free blog space, email and more
-
Not to sound OSBashing, but here is exactly where the "Open Source Model" fails. I know the pains of VSS inside out (Team of 5). if there would be a tool that provides simple no-think migration to CVS, people woud abandon VSS like lemmings a cliff. There is a market. it is an ugly market, since it's a one-time-tool, however, this is a busines problem solved before. So there is a market. there is a set of tools, that need integration, and there is some development work to do. But it's simply not happening. What *does* happen is that I can hire an expensive consultant for the price of a high performance SCS, who sets up everything and vanishes, and leaves me with a vital system I haven't set up, configured, or understood. regarding CVS, for one I'm a bit uneasy on the "merge thing" (maybe because that's really crappy in VSS). Second, after installing comes retraining, and for such a vital tool it must be "instant". It took our new developer an introductory session of 30 minutes (including explanation of the project structure), plus foud or five short questions over two days to work with VSS smoothly. How long with CVS?
we are here to help each other get through this thing, whatever it is Vonnegut jr.
boost your code || Fold With Us! || sighist | doxygen -
You just set a "working folder" and make a get latest of the solution file... Then open the solution file and let VS get all the remaining files/projects. Trust me, the problems is not with VSS it's with VS and Webprojects ;) When accessing the same webproject files from multible computers (like on a laptop and a workstation where it's the same files from your source control) it's important that the path to the web project (like c:\inetpub\wwwroot\someproject\) is the same or it will not work with VS on multible computers... If you get tired of VSS, try Vault[^]. - Anders My Photos
WDevs - The worlds first DSP, free blog space, email and more
thanks... That seems to be the exact problem. On my laptop, the path is e.g.c:\wwwroot\blah - where on my desktop it would be n:\customers\blah\website. So you're telling me I'm on a dead end here ? Is vault good ? As good ad $1200 ? Anyone else with vault experience ? Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
-
thanks... That seems to be the exact problem. On my laptop, the path is e.g.c:\wwwroot\blah - where on my desktop it would be n:\customers\blah\website. So you're telling me I'm on a dead end here ? Is vault good ? As good ad $1200 ? Anyone else with vault experience ? Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
Jan R Hansen wrote: That seems to be the exact problem. On my laptop, the path is e.g.c:\wwwroot\blah - where on my desktop it would be n:\customers\blah\website. So you're telling me I'm on a dead end here ? Yep, it will not work with VS You could use subst to map a drive on both computers, so your web would be at someting like "u:<\webs\someweb\" or whatever... Jan R Hansen wrote: Is vault good ? As good ad $1200 ? Anyone else with vault experience ? They have a free demo, actually they have a free single developer version ;) You could try it, it integrates nicely into VS and form the developers point of view it works almost just like VSS. I did write a bit about it here[^]. - Anders My Photos
WDevs - The worlds first DSP, free blog space, email and more
-
thanks... That seems to be the exact problem. On my laptop, the path is e.g.c:\wwwroot\blah - where on my desktop it would be n:\customers\blah\website. So you're telling me I'm on a dead end here ? Is vault good ? As good ad $1200 ? Anyone else with vault experience ? Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
If you open up your *.webinfo file in notepad you can edit the URL for the site Cheers James
-
Hi, I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. On my laptop, I've created a web-project located on the local hard drive, lets call it http://work.domain.dk. All files are in, say, d:\wwwroot\work.domain.dk\homepage, except from the solution file which is in d:\wwwroot\work.domain.dk. I then submitted it to a VSS server (using the build-in feature in Visual Stuido 2003), which created a "work.domain.dk" folder with the subfolders "work.domain" and "work.domain.dk". (folders, as in VSS "folders") - holding respectively the solution file and the project files. Now I want to open that project on my desktop pc, and place the phycical files (the working copy ?) on a network drive on my dev. server which is reachable via http://work.domain.dk. All files are on the network drive, the IIS looks in that folder, the DNS pionts at the dev. server. Everything works just nicely - except I can't get VSS / Visual studio to open the project. Usually, when a project is opened where the files are placed e.g. on a network drive, you get a dialog stating that the files cant be reached throuhg \\blahbla\url-here. Then you just point visual studio to the files on the network drive, and it works. Next time you dont get this question so it must be stored somewhere. Anyway, I've copied all files to the right location (as I didn't know how to get it out of VSS correctly X| ) on my dev. server. I try to open the solution - and VSS asks me for a URL to the files. I enter http://work.domain.dk, and then it just gives me an error about not being able to find the files on the \\blahblah\url-here. But it doesn't allow me to point out the correct location. So I would very must like to enter this information the correct place first. Does anybody know where this is stored ? Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Do you have any recommandations regarding whether or not to use VSS ? Should we go for something else, or just wait for VS2005 (it's build-in, right ?) I'm going crazy here.. please help me a bit :-D Sigh.. /Jan Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
this is a huge problem right now IMO. Most source control systems either suck or are way too expensive to be useful. I am currently using WIN CVS but it's barely limping along and I don't understand enough about it to fix some of the quirks it has (god help you if you want to move a directory to another project and keep it's history without doing it manually on the server). Because of this I wrote a source control system which turned out to be harder than I expected. However, due to many other projects working out well and taking all my time I wasn't able to finish it. I'm hoping to get it done sometime next year. I can relate to your frustration.
-
Hi, I've just spend well over 2 hours trying to get Visual SourceSafe to do what I want. But I can't. On my laptop, I've created a web-project located on the local hard drive, lets call it http://work.domain.dk. All files are in, say, d:\wwwroot\work.domain.dk\homepage, except from the solution file which is in d:\wwwroot\work.domain.dk. I then submitted it to a VSS server (using the build-in feature in Visual Stuido 2003), which created a "work.domain.dk" folder with the subfolders "work.domain" and "work.domain.dk". (folders, as in VSS "folders") - holding respectively the solution file and the project files. Now I want to open that project on my desktop pc, and place the phycical files (the working copy ?) on a network drive on my dev. server which is reachable via http://work.domain.dk. All files are on the network drive, the IIS looks in that folder, the DNS pionts at the dev. server. Everything works just nicely - except I can't get VSS / Visual studio to open the project. Usually, when a project is opened where the files are placed e.g. on a network drive, you get a dialog stating that the files cant be reached throuhg \\blahbla\url-here. Then you just point visual studio to the files on the network drive, and it works. Next time you dont get this question so it must be stored somewhere. Anyway, I've copied all files to the right location (as I didn't know how to get it out of VSS correctly X| ) on my dev. server. I try to open the solution - and VSS asks me for a URL to the files. I enter http://work.domain.dk, and then it just gives me an error about not being able to find the files on the \\blahblah\url-here. But it doesn't allow me to point out the correct location. So I would very must like to enter this information the correct place first. Does anybody know where this is stored ? Does anybody have any good tips for working with VSS / Visual studio when it comes to web projects ? Do you have any recommandations regarding whether or not to use VSS ? Should we go for something else, or just wait for VS2005 (it's build-in, right ?) I'm going crazy here.. please help me a bit :-D Sigh.. /Jan Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
The Urls have to be the same to use the same solution. However solutions are independent of projects so you can have 2 solutions one for your laptop and one for your desktop, either that or you can open the solution in notepad and edit it manually. This works because projects don't store location data in the project itself so you can have it in different locations without breaking the project. Also check out the VSWebCache directory in your profile. If VS.Net keeps trying to load the project from the old location no matter what you do, then delete the files for the project from here. VS.net 2003 is better with this, but the files in here can still cause problems if you've tried loading the same project from different locations. Personally I use subversion whenever I can. However every job I've had uses VSS. The best VS.Net build system I've worked with using VSS stored only the projects in VSS and then we used a seperate xml driven application that would pull the selected projects out of vss and then create a solution to contain them.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Jan R Hansen wrote: That seems to be the exact problem. On my laptop, the path is e.g.c:\wwwroot\blah - where on my desktop it would be n:\customers\blah\website. So you're telling me I'm on a dead end here ? Yep, it will not work with VS You could use subst to map a drive on both computers, so your web would be at someting like "u:<\webs\someweb\" or whatever... Jan R Hansen wrote: Is vault good ? As good ad $1200 ? Anyone else with vault experience ? They have a free demo, actually they have a free single developer version ;) You could try it, it integrates nicely into VS and form the developers point of view it works almost just like VSS. I did write a bit about it here[^]. - Anders My Photos
WDevs - The worlds first DSP, free blog space, email and more
i wont bother asking if you liked vault, since i am assuming you do, otherwise you wouldn't be linking to it ;) is it *really* easy to use? i have a few small app's at home that i write, and i have been looking into a source control system. we use CVS at work, which certainly does the job. however i don't want all the fuss at home. if it isn't simple and easy to use i will stick with making zip's of the source code every now and then *shrug* i am lazy like that :)
-
i wont bother asking if you liked vault, since i am assuming you do, otherwise you wouldn't be linking to it ;) is it *really* easy to use? i have a few small app's at home that i write, and i have been looking into a source control system. we use CVS at work, which certainly does the job. however i don't want all the fuss at home. if it isn't simple and easy to use i will stick with making zip's of the source code every now and then *shrug* i am lazy like that :)
have you considered Tortoise SVN in "sand box" mode? no server, it takes a directory of your choice and stores the subversion source control format from client only. Both Tortoise CVS and SVN clients have this ability, though at work we use full CVS client-server model, at work I have been running client server CVS but debating on testing out SVN at home so I am looking into it. http://tortoisesvn.tigris.org/[^] _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
this is a huge problem right now IMO. Most source control systems either suck or are way too expensive to be useful. I am currently using WIN CVS but it's barely limping along and I don't understand enough about it to fix some of the quirks it has (god help you if you want to move a directory to another project and keep it's history without doing it manually on the server). Because of this I wrote a source control system which turned out to be harder than I expected. However, due to many other projects working out well and taking all my time I wasn't able to finish it. I'm hoping to get it done sometime next year. I can relate to your frustration.
supposedly that was the reason for Subversion. Take the power of CVS, add capability seen in a few other commercial apps, and fix all the bugs, add flexibility. Note the first 3 points off the subversion website: Subversion's Features http://subversion.tigris.org/[^] Most current CVS features. Subversion is meant to be a better CVS, so it has most of CVS's features. Generally, Subversion's interface to a particular feature is similar to CVS's, except where there's a compelling reason to do otherwise. Directories, renames, and file meta-data are versioned. Lack of these features is one of the most common complaints against CVS. Subversion versions not only file contents and file existence, but also directories, copies, and renames. It also allows arbitrary metadata ("properties") to be versioned along with any file or directory, and provides a mechanism for versioning the `execute' permission flag on files. Commits are truly atomic. No part of a commit takes effect until the entire commit has succeeded. Revision numbers are per-commit, not per-file; log messages are attached to the revision, not stored redundantly as in CVS. They come right and say their goal was to fix CVS, and then start listing the main complaints on CVS. My one complaint about Subversion is that our security folks will not approve Apache, and the mini-client is not secure (everything passed in the open), so outside of home use, I am not sure I will be able to use Subversion at work for a very long time. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
thought so.... Actually, I once tried to set up a CVS system - but never got far. Then I was recommended Subversion, never got very far with that either. Are there any decent Windows-clients and / or VS integrated tools that run against Subversion ? Should I pefer that over CVS ? - they claim that they want to re-do CVS, just making it better... And then, just out of curiosity (spell check, please...) : How many of you know / have worked with "Continuus", these days known as "CM/Synergy" ? It's a source code control / configuration management system that took me 3 years of daily use as a developer to "understand". But now we're friends :) I have no illusions about being less than a year about setting that up.. and its probably extremely expencive... Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
For Subversion there is TortoiseSVN that is a Windows Explorer shell. Very handy. I believe there are tools to integrate Subversion into Visual Studio, but have not used them. Subversion really is good stuff... been using it for a while now. In particular, the nice thing is that the whole repository has a version (so you can do atomic commit operations), and directories are under version control (not just files.) An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
-
supposedly that was the reason for Subversion. Take the power of CVS, add capability seen in a few other commercial apps, and fix all the bugs, add flexibility. Note the first 3 points off the subversion website: Subversion's Features http://subversion.tigris.org/[^] Most current CVS features. Subversion is meant to be a better CVS, so it has most of CVS's features. Generally, Subversion's interface to a particular feature is similar to CVS's, except where there's a compelling reason to do otherwise. Directories, renames, and file meta-data are versioned. Lack of these features is one of the most common complaints against CVS. Subversion versions not only file contents and file existence, but also directories, copies, and renames. It also allows arbitrary metadata ("properties") to be versioned along with any file or directory, and provides a mechanism for versioning the `execute' permission flag on files. Commits are truly atomic. No part of a commit takes effect until the entire commit has succeeded. Revision numbers are per-commit, not per-file; log messages are attached to the revision, not stored redundantly as in CVS. They come right and say their goal was to fix CVS, and then start listing the main complaints on CVS. My one complaint about Subversion is that our security folks will not approve Apache, and the mini-client is not secure (everything passed in the open), so outside of home use, I am not sure I will be able to use Subversion at work for a very long time. _________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
You can set subversion to use SSH. Also there is a Subversion Visual Studio .NET plugin that you can use called ankhsvn at http://ankhsvn.com/(Sorry don't know how to do the cliketty thing) combined with tortoise its pretty good.