|
We use something similar to this[^] for storing copies of our code.
cheers
Chris Maunder
|
|
|
|
|
Funny, I was actually being serious with my question and you give that as an answer. Interesting...
|
|
|
|
|
 That made my day!
Thanks,
Robin.
|
|
|
|
|
I love the security in your system--using the net to keep the upper level data from corruption. Of course, I expect the database could be rebuilt for any dropped clusters.
|
|
|
|
|
I've used Git, Mercurial, SourceSafe and TFS, even (from the dark ages) DECset on VMS and an SCM on CDC Kronos systems (darn, can't remember the name, and yeah, SCMs have been around on mainframes since the 1960s). TFS gave me the least amount of trouble. I develop both C# and .NET alongside embedded "bare iron" ARM GCC using Eclipse. TFS worked fine for both.
Working with embedded involves building boards as well as writing code. I used TFS to version schematics, PCB layouts and reference manuals, even field service work instructions, along with code. That's where the database method is handy; it stores binary BLOBs as wll as code deltas.
What I like best is the lack of "file droppings" in source code directories. TFS puts everything in a SQL database. This is developing in a commercial enterprise environment where project management is critical. TFS has a very nice work item structure to track design, bugs, testing, even deployment, and it integrates well with both VS and Eclipse, along with MS Project.
The type of programing is not quite the usual mix. What I need is a common pool of drivers and RTOS tasks that I pick and choose for different circuit boards, sort of an a la carte program design methodology. Code is added to individual files with conditional compiles for different variations, due to IC pinouts, but basically similar targets. Directory level commit gets in the way because individual files are shared across several target builds, not the entire directory. Sure, other SCMs can do file level check in/out, but TFS does it best.
These days I have to use Github, management directives from on high, but I do miss the ease of use with TFS.
|
|
|
|
|
I have found TFS or TFS services ( the free online version) to be the easiest I've ever experienced. I recently used Github and find myself cursing the creators. Most of my problems seem to be related to large file handling. I ended up having to learn the commandline just to clean up the messes.i've never experienced anything that frustrating with TFS. Others will swear by Github, but use TFS unless you like pain
|
|
|
|
|
In our AX 2012 development, TFS was nothing but a pain. We had issues attempting to implement it with multiple users in two different domains. It just couldn't handle it.
|
|
|
|
|
Git or Mercurial (Hg). Very small footprint and extremely easy to install and get started with.
They encourage committing early and often so everything is tracked.
They are both extremely easy to use though I think Hg's commands are a bit easier to remember for some reason -- though as you'll see they share many commands.
1. Download and install Git or Mercurial.
2. download a .gitignore or .hgignore file (for your language like C#) so binaries etc are (ignored) not committed.
3. c:\MyProject\>git init <ENTER>
3. c:\MyProject\>hg init <ENTER>
4. c:\MyProject\>git add . <ENTER>
4. c:\MyProject\>hg add . <ENTER>
5. c:\MyProject\>git commit -a -m "initial commit of project" <enter>
5. c:\MyProject\>hg commit -m "initial commit of project" <enter>
You are set up and ready to go. now all your changes will be tracked.
you can do hg diff or git diff and you'll see diffs
You can do hg status or git status and you'll see files that have been changed.
it's so easy. once you use it you will never want to do anything without it because everything is tracked and you can easily move to a previous revision and throw the current branch away.
modified 12-Sep-16 21:05pm.
|
|
|
|
|
raddevus wrote: it's so easy
I hate command line. I do prefer keyboard over mouse but I'm getting too old, I guess, to have to learn another "language."
Thanks for the feedback though.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
RyanDev wrote: I hate command line.
Oh, well, when you install Hg it will also install TortoiseHg Workbench which is a UI.
Also, if you decided to go with the git bash installation then you can type c:/>gitk<ENTER> and a Tortoise-like UI will appear and you can do the work from there.
Good luck
|
|
|
|
|
As well as TortoiseHg, you have the option of Sourcetree[^], which is a GUI client for both Git and Mercurial repos, or GitKraken[^], which (as the name suggests) is a Git client GUI.
Personally, I prefer TortoiseHg for Mercurial and GitKraken for Git, but I've got all three installed...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
I'm using VisualSVN on a server box at my office.
Free save for the static ip, os and box.
|
|
|
|
|
Another thumbs up for VisualSVN plus the Tortoise SVN client. Very intuitive. If you have access to a remote server you get the additional security of off-site repository storage.
|
|
|
|
|
I'd add a vote for Atlassian SourceTree - how you get your repos in one place I dont know unless you go github public - I use local git repos and occasionally when working on one project pull from a colleagues company private repo
- source control is one thing where I like to 'see' what Im doing, as opposed to command-line, so SourceTree works well for me
|
|
|
|
|
|
I like the look of Gitblit  thanks
I'll stick with SourceTree though instead of TortoiseGit, it means its the same on my Mac as it is on windows
|
|
|
|
|
|
I'd recommend Mercurial, and since you don't like CLI, more specifically TortoiseHG[^].
It's simple to use, filebased, distributed and more consistent than GIT[^].
Joel Spolsky made a tutorial that you can find here[^], it's for the CLI version, but I'd still recommend reading it.
|
|
|
|
|
Thanks.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I'd recommend GIT but with something simpler than source tree if you are after simplicity.
What IDE/Language you using? Visual Studios GIT tools are not bad.
|
|
|
|
|
Subversion: very simple, doesn't need a server, can access via shared disk repository.
|
|
|
|
|
Seconded, this is what I use at home, shared folder on NAS, VisualSvn plug in. Simple, free and up and running in under an hour.
Regards,
Rob Philpott.
|
|
|
|
|
Richard MacCutchan wrote: Subversion: very simple, doesn't need a server
I thought it did. Thanks.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I think there is a version that may need one, but the basic version just uses simple disk to disk copy. Not much use in a business environment, but ideal for home use.
|
|
|
|
|
I am using SVN and the server is built in. Works very well with Tortoise and Ankhsvn.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
