Hello Mike. I read great advices, I have nothing to add. I generally use Bash shell on Windows, and I'm fine. When I feel I need a GUI, I use SourceTree by Atlassian, the best one IMHO. I use even VS2013 integration (generally only for quick committing), and I used TortoiseGit due its facility when migrating repositories from SVN. Anyway, I'm writing a book about Git for beginner, Git Essentials. If you like, I can send you an invite to get it for free when available :) Please follow me on my blog (JesusWasRasta.com) or Twitter @jesuswasrasta to get in touch. :) Bye! :) Nando

See things I like at jesuswasrasta.com

Yes, but why VS2008 did not make this a problem on compiling? I agree with you when you say you can't use upper framework form a 2.0 assembly, 'cause, for example it can be deployed on a win2000 or on a machine without .NET 3.0. But as I say in my previous post, I'll deploy this solution on .NET 3.5 ready machines; only a bug/limit of Cobol<->.NET bridge force me to compile only this Cobol-.NET-interface-assembly in 2.0. However, I found the trick: reference System.Core.dll (or other dll needed by your referenced assemblies) by hand. Thanks! Nando

Jesus

Good afternoon! :) Yesterday for me was the "Great day": new pc, new VS. I installed VS2010, and ported my solutions to it. In a solution of mine, I need to create a .NET 2.0 assembly (compatibility issues with ACU Cobol) that uses some other assemblies compiled with .NET 3.5 Warning messages apart, in VS2008 all works fine; in VS 2010 I cannot compile: my 2.0 project reference against other 3.5 appears with the warning yellow mark. I can comnpile only if I reference by hand System.Core.dll from .NET 3.5 framework in my 2.0 targeted assembly. Anybody can give me an explanation about this new/strange VS2010 behaviour? :(( Thanks! Nando ;)

Jesus

Free: http://ankhsvn.open.collab.net/[^] Commercial: http://www.visualsvn.com/[^] For a 2-minutes-win-svn-server, you can use free Visual SVN Server http://www.visualsvn.com/server/[^] Nando

Jesus