IntroductionBefore we jump in and start looking at all the Open Source tools and components that are useful to any .NET developer (Chapters 3-8 if you want to skip ahead), and before we write ASP.NET and ADO.NET code that works on both Windows and Linux (Chapters 10 and 11), it is important that you understand exactly what Open Source is. "Is it really OK to use this code in your product?" "Does using the tools violate your company's procedures?" What are you going to say to a manager or other team member who asks these kinds of questions? Well, first you must have a clear understanding of Open Source. The term Open Source has drawn a lot of attention lately. Open Source has been all over the press as both success stories and failures. I have found that this term stirs great emotion in a person and makes for a great conversation piece at a meeting. I have seen development teams divided and management up in arms over Open Source software. However, in my experience very few Microsoft developers fully understand what Open Source is and base arguments and important design decisions on hearsay and half-truths about Open Source. This chapter could have been titled "How To Use Open Source with Microsoft Products." I assume that since you are reading this book, you have some interest in Open Source, and this chapter will help you get started. Since this book is about Microsoft .NET and about Open Source, this chapter helps you understand how to use them together. .NET is unique for Microsoft. Previously, Microsoft development tools were proprietary, but the .NET SoftwareChapter 2). The Common Language Infrastructure allows for many programming platforms to work with the .NET framework, resulting in multiple programming language implementations. http://www.lahey.com/netwtpr1 | |
Cobol.NET | http://www.fsw.fujitsu.com/ |
J#, C#, C++.NET, VB.NET, Jscript.NET | NET Framework |