Comments on: AutoMapper upgraded to .NET 4 and VS 2010http://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/
Strong opinions, weakly heldTue, 03 Mar 2015 07:43:00 +0000hourly1http://wordpress.org/?v=3.4.2By: How to install Automapper for .net 3.5 | FaceColony.com - Developers Networkhttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-4252
How to install Automapper for .net 3.5 | FaceColony.com - Developers NetworkWed, 18 Jan 2012 17:32:52 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-4252[...] have found a branch on Git hub, thanks to this post by the creator Jimmy [...][...] have found a branch on Git hub, thanks to this post by the creator Jimmy [...]
]]>By: Anonymoushttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-3620
AnonymousThu, 21 Jul 2011 00:41:00 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-3620Nah, not yet.Nah, not yet.
]]>By: Allen Firthhttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-3618
Allen FirthWed, 20 Jul 2011 12:06:00 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-3618do you support mapping from dynamic (.NET 4.0) objects in the latest version of AutoMapper?do you support mapping from dynamic (.NET 4.0) objects in the latest version of AutoMapper?
]]>By: Nick Berardihttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-2545
Nick BerardiWed, 18 Aug 2010 11:59:01 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-2545I think you used a round about way to actually create a branch.
http://learn.github.com/p/branching.html
because you can do
git branch NET35
git checkout NET35
... do some git stuff and commit ...
git push origin NET35
to me that seems more straight forward then the method you took.I think you used a round about way to actually create a branch.

]]>By: Charles Strahanhttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-2544
Charles StrahanTue, 17 Aug 2010 17:17:21 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-2544Nice post, Jimmy.
in general, the `:' separates the "source" from the "destination", so `git pull origin foo:bar' will pull the "foo" branch down from your remote, while naming it locally "bar"; whereas `git push origin bar:foo' will push your local "bar" branch to your remote as "foo".
You can also delete a remote branch by doing `git push origin :foo', which will delete the foo branch (it essentially says "push nothing up to my remote origin as 'foo'" - Yoda speak for "delete foo").
You may already know most of that, but I figured I'd share. GitHub has a good reference here:
http://help.github.com/remotes/
-CharlesNice post, Jimmy.

in general, the `:’ separates the “source” from the “destination”, so `git pull origin foo:bar’ will pull the “foo” branch down from your remote, while naming it locally “bar”; whereas `git push origin bar:foo’ will push your local “bar” branch to your remote as “foo”.

You can also delete a remote branch by doing `git push origin :foo’, which will delete the foo branch (it essentially says “push nothing up to my remote origin as ‘foo’” – Yoda speak for “delete foo”).

]]>By: bogardjhttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-2543
bogardjTue, 17 Aug 2010 16:52:35 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-2543@ahjohannessen
Yep, you have to internalize at least a lot of things. Pull down the source and you can see how I got it to work. But I also deploy the non-merged versions, in case folks need a later version of Castle or something
@Alastair
I didn't think that a local branch could be pushed to a remote server branch that doesn't exist yet. Is that possible?@ahjohannessen

Yep, you have to internalize at least a lot of things. Pull down the source and you can see how I got it to work. But I also deploy the non-merged versions, in case folks need a later version of Castle or something

@Alastair

I didn’t think that a local branch could be pushed to a remote server branch that doesn’t exist yet. Is that possible?

]]>By: Alastair Smithhttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-2542
Alastair SmithTue, 17 Aug 2010 15:55:47 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-2542Out of interest, why did you choose not to create the NET35 branch locally and push that out to GitHub?Out of interest, why did you choose not to create the NET35 branch locally and push that out to GitHub?
]]>By: ahjohannessenhttp://lostechies.com/jimmybogard/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010/#comment-2541
ahjohannessenTue, 17 Aug 2010 13:36:53 +0000/blogs/jimmy_bogard/archive/2010/08/17/automapper-upgraded-to-net-4-and-vs-2010.aspx#comment-2541When you merge the dll, do you make external dependencies internal? I had a problem this morning with Castle.* versioning because of Castle.* usage elsewhere in my code.When you merge the dll, do you make external dependencies internal? I had a problem this morning with Castle.* versioning because of Castle.* usage elsewhere in my code.
]]>