|
I'm looking at it this way - it has worked for what little i've been able to throw at it. It's *hard* to test right now but will be easier to test when more of the project comes together - a lot of the project is like that right now. I have some of the foundation but I'm building a house in the middle of a hurricane so to speak. It's a bit hectic.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Dust off your rubber duck and prepare for a heart-to-heart.
|
|
|
|
|
|
|
She still looks hot and can still belt em out
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Tina Turner with her Bunsen burner 
|
|
|
|
|
So, after my last post, I still need some source control. With MS saying not to use VSTS, and I DON'T WANT GIT, what are my options?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
SVN?
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Hosted where?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Own computer acting as server?
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Yep 
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
I actually have a server, and I've hosted SVN on it, but having the source in a repo in the same room as my dev PC doesn't keep me from losing the code if my house burns down.
I could of course back up the SVN repo, but that's what cloud based systems are for.
I guess I could set up backup of the repos to some cloud storage, but I'm looking for easy.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
You shouldn't consider source control as a backup system - separate the concerns and implement a planned backup strategy, by all means in conjunction with source control. They really aren't there for the same things, and you sound like you need disaster recovery rather than source control.
Backup to the cloud, or onto physical media which you rotate into a mates house (and perhaps rotate his into yours) instead.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I never said source control was backup.
I said doing source control on a server next to my Dev PC doesn't make sense in case the house burns down
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: I never said source control was backup.
I said I need source control as a backup in case the house burns down
That's what I hear.
If you want to secure your work against the case where your house burns down, seek a backup solution.
If you want to be able to maintain different versions of your codebase, seek a source control system.
There's no reason you can't use both.
Technically, you can setup a source control system as a backup solution. But it would be very inefficient. I've tried it once but found it to be painfully slow. Plus it clogs your drives with version control info that you might not even need - at least not on your local drives!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
Host the repo locally. Store the backups of the repo off-site.
I believe that's the crux of Griff's point.
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
|
|
|
|
|
My personal ISP (DreamHost) allows SVN installations. Check your ISP.
|
|
|
|
|
Try Assembla.com, I have had good luck with them and integrating into Visual Studio with Ankhsvn
|
|
|
|
|
|
|
|
git is fine if you use it right. It's branching is better than SVN. Get a UI like Sourcetree and use 'git flow'.
|
|
|
|
|
I've worked with Git for years and never amended anything.
I don't get the issue with reverting.
How would you solve that using TFSC or SVN?
The fact is you pushed something that didn't work to the master branch, people made other changes to that code and now you want it removed.
I've been in the situation where I had to revert multiple commits and this was as easy as selecting the commit I wanted to go back to and selecting "revert to this commit".
As the author says, all backward changes were added to the branch, but my coworkers had some merge conflicts.
Those conflicts are to be expected since I just messed up the whole code base that everyone was working on.
SVN or any other SCM isn't going to handle that gracefully either...
Actually, I don't recognize anything he talks about in that post, except this little sentence in the intro:
János Kubisch wrote: Fortunately, it is really hard to irrevocably mess something up with git, as long as you have the .git hidden folder in your project intact!
In my experience it takes some getting used to.
I worked in a team who worked with SVN for years and they were also a bunch of bunglers, so they complained about Git for years and never got the hang of it.
Another team who moved to Git was amazed at how easy the transition was.
At first, I thought it was overly complicated compared to SVN, but now I never want to go back.
It's very easy to branch and merge, which makes developing new features and cooperating in teams so much easier.
I wouldn't dismiss Git based on that one article...
Just be sure to get some GUI tool.
Not the default or the command line, those are for script kiddies who think they're so cool because they use command line.
I use SourceTree or Visual Studio 2019 and those work well.
|
|
|
|
|
I use the builtin with VS 2017 and it works. I've only run into one major problem with it - it sometimes tries to push my entire Projects folder. But I've worked around the issue
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: it sometimes tries to push my entire Projects folder
Do you have a .gitignore?
I've never used it before because I was missing stashing functionality.
I used to like SourceTree A LOT better (VS 2015-2017), but with 2019 it's just slightly better I think.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
