[AccessD] Visual Studio and source control
Gustav Brock
gustav at cactus.dk
Sat Nov 14 12:07:26 CST 2015
Hi John
First question: Why not VS2015?
You may have your reasons for choosing VS2013, but I believe the GitHub support (the add-in) is better in VS2015. That said, it works, but I think the user interface and way to operate is primitive and clumsy - but it works when you have found out ... it's not difficult but not very logical.
Second: I just use a shared network folder for my Git repositories. Then, when I tell so from VS, the current project is synced to GitHub (I only use the public site).
GitHub is a Linux thing, so it shouldn't be very offending to you ... but as you seem to be in a hurry, I binged for alternatives (because also I actually would like to have my own server as the public server is, eh, just that: Public) and found GitStack targeted at lazy people like me having other things to do:
http://gitstack.com/
They sport a "Basic" full-featured community version limited to two users, but wouldn't that fit your setup?
I'll give it a look in the near future.
/gustav
________________________________________
Fra: AccessD <accessd-bounces at databaseadvisors.com> på vegne af John Colby <jwcolby at gmail.com>
Sendt: 14. november 2015 18:38
Til: dba-vb at databaseadvisors.com; Access Developers discussion and problem solving; jwcolby at gmail.com
Emne: [AccessD] Visual Studio and source control
I have been using Visual Studio 2008 and 2010 for many years. I am
about to move up to 2013, which has built-in support for GitHub. I have
VS 2013 Community edition installed on a new dev virtual machine and
upgraded to the latest service pack (pack 3).
I would like to run a local GitHub server on my Windows 2008 R2 VM
server which hosts my dev virtual machines, then build a project from an
already existing 2010 project.
To this point I have found all kinds of "it can be done" but no clear
instructions to getting the server set up on Windows and from there
getting connected from inside of Visual Studio. Can anyone point me to
a clear and concise instruction for making this work?
Any assistance much appreciated.
--
John W. Colby
More information about the AccessD
mailing list