4

I am a seasoned .Net developer and have a good grasp of OOP concepts. I will be working on a Java project in the near future and was interested in knowing if someone could point me to a good migration guide for moving from C# 4.0 to Java.

Java equivalent for :

  1. LINQ to Objects (I understand Java does not support anonymous types like C# does, but a good collections library would be helful)
  2. ASP.Net MVC 3 (what are the cool kids using for building Java web applications these days)
  3. Castle Windsor (something which supports a fluent registration api)
  4. WCF 4.0, SOAP for the most part, REST some scenarios
  5. Build - nant (something no xml?)
  6. A language nuances guide (no lambdas, anonymous methods, etc.)

Thanks

linuxbuild
  • 15,843
  • 6
  • 60
  • 87
SharePoint Newbie
  • 5,974
  • 12
  • 62
  • 103
  • 4
    the bit about nant sort of made me chuckle, take the n off and you will have the java build tool that started the whole dumb move to xml for build scripts in the first place. – Matt Briggs Jan 21 '11 at 13:54
  • 1
    @Matt Briggs: what, you miss *make* 's CR/LF issues between Un*ces and Windows? And makefiles encoding issues? (when stupid developers used non-ASCII in files/directories names needed to be referenced from *make*) Common... At least XML solved the nasty CR/LF and character encoding issues ;) Agreed it's verbose, but I don't ever want to hear about CR/LF nor about character encoding issue again ;) – SyntaxT3rr0r Jan 21 '11 at 16:21
  • @SyntaxT3rr0r: Granted, but stuff that has come out of the ruby, javascript, python, and clojure communities (and probably more, I just have experience with those tools) are all vastly superior to the xml thing. holding make up as the only alternative is a bit of a straw man argument – Matt Briggs Jan 21 '11 at 19:48