This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am a student finishing up my master's degree in Computer Science and I have a couple of years experience with J2SE and J2ME. I am just beginning to get into J2EE. In fact, I have just started reading Head First EJB. I have have not used .NET at this point. My question is, when you talk about interoperability between the two which language are you using on the .NET platform? It is my understanding that the .NET platform consists of C, C++, C#, Basic, etc. Thanks, Frank Malinowski
.NET language refers to any .NET language components. Such as VB.NET, ASP.NET, C#, etc. Since Web Services is language independent, and thus, which language is not important. This is one of the beauty of Web Services. Nick
You obviously know that Java code is compiled to Java bytecode. All .NET languages are compiled to IL, Intermediate Language. You need the .NET Framework to run the IL applications, just like you need the JVM to run Java bytecode. At least this is what it was meant to be. I've been working with Reporting Service for MS SQL Server. The code you write must be Visual Basic .NET, I think that's rather strange, because everything is compiled to IL. Web Services can be build in every .NET language including J#. Yours, Mark Monster
It may be helpful to think about .NET as a platform/framework, which it is, instead of language. Like J2EE, .NET provides the user with an enviorment to run your code, this environment comes with infrastructure build in so you can spend less time on the low services and more time on the business logic. .NET and J2EE are more alike (at least conceptually) than most people realize and than Sun and Microsoft would like to admit. I've worked with both and have far less objection than I did when Microsoft was not pure OO. The changes they have made have been impressive. Anyone competent with Java will have no problem working in C#. The biggest hassle is working through the platforms. While there are direct parallels between J2EE and .NET as platforms, it can take some time to draw match up the parts in the enterprise stack. The fact that Microsoft still likes to use it's own language of patterns that doesn't match up to most other environments doesn't help, but it is a huge improvement over what it once was. You might want to take a look at a related article I wrote which was published in Computerworld last year... J2EE vs .Net: The choice depends on your needs http://www.computerworld.com/developmenttopics/development/story/0,10801,84155,00.html [ March 26, 2004: Message edited by: Byron Estes ] [ March 26, 2004: Message edited by: Byron Estes ]