One of my concerns at my day job is that some new developer will install VS
2013 and see the new shiny button for creating a local GIT repository and then
think they are covered. One day it'll all be lost and I'll get thrown into a
mess. It doesn't matter that they are matrix resources... it'll somehow by my
fauly.
BTW... I know... you can't fix stupid. I wonder if it's possible to make that
go away using group policy. :-)
----------------------------------------
From: "Christopher Painter" <chr...@iswix.com>
Sent: Saturday, November 16, 2013 6:29 AM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>,
"Windows Installer XML toolset developer mailing list"
<wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Useless, stupid rant
I've played with Git in VS Online. I don't think the experience is nice. You
lose the source control explorer and have to go outside of the IDE to see your
files. I think at that point I add to use Tortoise Git to add my file and Team
Explorer to commit it.
Creating build definitions is not as good either. The source settings only
seems to allow me to select which branches to monitor and not to narrow the
scope of what folders to include. The default templates doesn't give you the
ellipse to select your solution to build nor does it allow you to select
building multiple solutions. GitTemplate12 seems to add this.
So I guess my main question is why do I have to include the entire repository
in a build definition? It seems like they are forcing you into creating more
and more repos and team projects to get the granular control over CI builds.
Compared to how we work today, I don't like this at all.
----------------------------------------
From: "Heath Stewart" <hea...@outlook.com>
Sent: Friday, November 15, 2013 11:46 PM
To: "Windows Installer XML toolset developer mailing list"
<wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Useless, stupid rant
VS Online still works great with Git. I've been using it with all the same
ALM benefits like build and test controllers. So I don't think moving away from
git - where it's so easy to fork/branch changes even in your own reps is
necessary even if you want ALM.
- Heath from his Surface Pro
From: Christopher Painter
Sent: ?Friday?, ?November? ?15?, ?2013 ?12?:?13? ?PM
To: Windows Installer XML toolset developer mailing list, Windows Installer XML
toolset developer mailing list
I've been a CM / ALM / build / release engineer / consultant / architect for 17
years. I'm currently a manager responsible for setting the developer tools
vision for a Fortune 50 company with thousands of developers. I've worked
either at or for dozens of companies. I've used more SCC tools then I care to
remember: CVS, RCS, PVCS, VSS, Vault, ClearCase, TFS, SubVersion, StarTeam,
Accurev.... probably a few more I don't remember.
I am a big fan of TFS. It's not the best X, Y or Z but when you consider it
all together, it's pretty darn good. The whole centralized vs decentralized
source control argument is usually from developers with a Steve Jobs syndrome
when it comes to ALM. They read a couple blogs and suddenly think they know
everything. When I counter their arguments they just whine about argument of
authority.
Microsoft just posted their hosted TFS pricing and it's crazy good. For the
cost of a monthly cell phone plan I can give someone a license of Visual Studio
and an ALM in a box with build server. In 5 minutes I can create an MVC app,
package it up in an MSI using WiX and deploy it to a VM for testing. It's that
crazy good.
Anyways, Blair... I hear you and agree with you. But in some places the
developers run the show and you'll see Git or whatever next cool source control
is popular. Anyways as long as TFS gets all their other pieces to integrate
nicely with a Git provider.... then I'll be fine with that too.
----------------------------------------
From: "Bruce Cran" <br...@cran.org.uk>
Sent: Friday, November 15, 2013 12:51 PM
To: "WiX toolset developer mailing list" <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Useless, stupid rant
On 11/15/2013 6:42 PM, Hoover, Jacob wrote:
Blair, It would help if you were to provide more details on why you got
so frustrated. I switched to git over two years ago, and compared to our
previous version control I'm nothing but ecstatic for git. I'm betting the HG
experience has you thinking the VCS should work one why, when in fact it works
another. Sharing experiences here could lead to answers that others may need in
the future in order to contribute to WIX.
I've used both Hg and Git, and the user interface for Hg seems more logical.
Having said that, after a few weeks of total frustration I started to
understand how Git works (fetch, merge, checkout, add, commit, rebase), and
ended up being able to use it quite efficiently. I do like that things like
history editing is built-in whereas with Hg it's an extension.
In the past I've used cvs, svn, ClearCase and some other SCM, so I don't think
it's familiarity with a way of working that tripped me up.
--
Bruce Cran
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
