Join 149,492 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 1,307 people online right now. Registration is fast and FREE... Join Now!
How do you handle versioning for your applications? I'm aware of products like subversion for web based applications, but what are you using for your compiled apps and such?
How do you handle versioning for your applications? I'm aware of products like subversion for web based applications, but what are you using for your compiled apps and such?
I've used Subversion and CVS for compiled apps - currently CVS.
I've never used it for compiled apps, does it work the same as for a web app? Are there other products that you are aware of?
At work we don't have "versioning" per-se, but just a development, staging, and production web server. Not ideal, but it works for what we need it for.
I would love to setup some sort of version control though so we could do regression testing and the like.
We are using CVS right now, but subversion is being evaluated. Using a version control system is a very good thing, but you have to think a lot about what to put into it (binary files, that can not be merged, etc.), and check the tools that are going to use it, wether they can be used together, or just one at a time ( I had a nightmare once, when I was naiv using Eclipse and WinCVS, and they went out of sync, so hell was unleashed... )
I have used rational rose (as a user not an administrator). Unfortently talking to some administrators binary files are checked in as whole intenties rather than file differences (like text files). Brain storming about it; other than trying to save hard drive space; the difference tracking of binary files is rather pointless if the versioning tool does not understand the underlying format.
So I guess basically, is unless we are capturing binary files as a baseline for a test (ie the binary file is not compiled from the source), we avoid the issue.
I've never used it for compiled apps, does it work the same as for a web app? Are there other products that you are aware of?
At work we don't have "versioning" per-se, but just a development, staging, and production web server. Not ideal, but it works for what we need it for.
I would love to setup some sort of version control though so we could do regression testing and the like.
My use of SVN is limited, so I can't say how different it works for regular apps vs. web apps. Frankly, though, I prefer CVS. Maybe it's because I'm familiar with it. Maybe it's because the CVS functionality in Eclipse is more familiar to me and seems more robust than the SVN plug-in interface. All I know is that I get more done with CVS. Here's an interesting, if brief, comparison of the two:
Well setting the version of your app can be done when you compile the exe file. Of course some tools do it even easier, but I am used to set the version like that.
Well setting the version of your app can be done when you compile the exe file. Of course some tools do it even easier, but I am used to set the version like that.
Chris et al
There are a swag of tools out there. The basis for most of them is RCS, which is a simple one-user at a time control system.
There is also Concurrent CVS which is deigned to work with a number of users and enable the same file to be modified and merged from several sources.
If you are running any ISO 9001 based system, the use of Version Control is a requirement, so you must select the tool that is pertinent to your needs and ensure you back its use with documentation for your purpose. Refer to HB90.9 - ISO 9001 Guide to Software Management.
At work and at home I use subversion. This is all 'compiled' apps and it works great. It doesn't really matter if it's compiled or a web app. We do maintain a few binaries in SVN, but they rarely change. It's almost all source code.
| 