Choosing Your .NET Language

Earlier in this chapter in the "Get Started" section, I discussed the New Project button. After you click that button, the New Project dialog box appears, allowing you to choose project types. I have emphasized (more than once, I think) that the choices you make during your VS .NET installation influence the project types that appear in this dialog box. The upper portion of the New Project dialog box shows an example of the project types (see Figure 5-13) that are language specific. (Your display may differ .)

Figure 5-13: The upper portion of the New Project dialog box

When I installed VS .NET, I chose to include VB .NET and C# (pronounced "C sharp"). Later, I acquired NetCOBOL for .NET from Fujitsu and installed it. In this section, I discuss these languages.

Cross-Reference  

In addition to the .NET languages provided by Microsoft, ISVs such as Fujitsu are providing .NET languages. At this time, 15 ISVs are developing .NET languages. Visit the Microsoft .NET Language Partners Web site ( http://msdn.microsoft.com/vstudio/partners/language/default.asp ) for more information.

VB .NET

The first language I learned after venturing into my own reformation was Visual Basic. As I mentioned in the book's Introduction, my involvement with Visual Basic started with version 5.0. As we (I and the rest of the Visual Basic community) pull ourselves away from Visual Basic 6.0 and gravitate toward VB .NET, I still remember my initial reaction to Visual Basic several years ago: "Wow, so they have created another Common Business Oriented Language!"

Because I had an extensive background in COBOL, learning Visual Basic seemed easy to me (it was all of the prerequisites covered in Chapters 3 and 4 that took more time). After all, Visual Basic was rather English-like and verbose (some-thing that I liked about COBOL). Another deciding factor for me was Visual Basic's market share in the business application world. Coming from the mainframe, I was always comfortable with my marketability (even before Y2K). Naturally, I wanted to maintain or enhance my marketability . Having Visual Basic in my skill set has certainly fulfilled (and continues to fulfill) that requirement. Now, with .NET, I have the opportunity to learn another new language: VB .NET. ^[4]

Although not everyone will choose to use VB .NET as his or her main .NET programming language, I definitely consider it a wise move to include VB .NET as part of your retraining effort. Having said that, I can now disclose that (everywhere possible) the code samples in this book will be presented in both languages: VB .NET and NetCOBOL for .NET. Not that you need to be convinced, but as you comb through the generous amount of tutorial information that is available on MSDN, you will notice that the sample code is written in either C# or VB .NET. Learning VB .NET (and/or C#) will make these tutorial and sample code offerings that much more valuable to you.

Cross-Reference  

By the way, language interoperability and COM Interoperability (COM Interop) are features of .NET that I further discuss in Chapter 19.

As many will tell you, and as you'll soon develop an understanding for, learning to program .NET involves many things. It's much more than just learning the syntax rules of one language or another. I'll strive to keep emphasizing that your language choice is a lesser issue. I demonstrate this idea later in the section "Developing Your First .NET Program."

COBOL for .NET

As you know, COBOL has come a long way. And now, COBOL has headed into the future with an entry onto the .NET landscape made possible through the partnering of Fujitsu and Microsoft via the Visual Studio .NET Integration Program (VSIP, which I discussed earlier in section "VS .NET Customization Through Integration"). Fujitsu has named this COBOL edition NetCOBOL for .NET. Going forward, I refer to Fujitsu's NetCOBOL for .NET product unofficially as "COBOL .NET".

Cross-Reference  

You can download a free trial version of Fujitsu's NetCOBOL for .NET from Fujitsu Software's Web site ( http://www.netcobol.com/products/ windows /netcobol.html ).

Given the affection that we mainframe programmers have for the COBOL language, ^[5] COBOL .NET just has to be the coolest thing since the invention of sliced bread. Just think, you can leverage the full power of the .NET Framework using COBOL. Granted, using COBOL .NET still requires that you learn how to use the other portions of .NET. Also, it is still advisable to clear the retraining prerequisites discussed in Chapters 3 and 4. Nevertheless, we have arrived.

As of this book's writing, Fujitsu has included support for several project templates. Therefore, with COBOL .NET, you can create .NET Windows applications. That's not all: Fujitsu has also included support for ASP.NET in their COBOL product. In other words, you can also create Web applications. Now, is that great or what? Obviously, I'm excited about this and you should be too.

What an Opportunity!

I am sure there are those who will say, "But I can already create Windows applications with COBOL." On top of that, some of you may already be using one of various flavors of object-oriented COBOL. My response is this: Try .NET, try VS .NET, and then tell me if you think this whole thing is worth getting excited about. I am betting (and hoping) that the mainframe community realizes what a great opportunity .NET is. I am hoping that we can lay down our gauntlets and join forces with the Web and Windows developers and not waste time criticizing the implementation that Fujitsu (and Microsoft) have made available. Seize the opportunity!

 

By the way, there are also business reasons to justify being excited about COBOL .NET. COBOL's availability on .NET means that the dream for companies to leverage several investments can now be made a reality. The investments in people as well as the investments in business rule logic can now be leveraged. Not only can the developers get excited, but the managers and executives can get excited as well. As I mentioned in the previous section, I attempt to present all code samples in this book using both COBOL .NET and VB .NET. You will be amazed at the opportunities that you will create for yourself (and your employer) by becoming "bilingual."

What About C#?

Appendix B is a brief primer covering the basics of two additional languages provided by Microsoft: C# (pronounced "C sharp") and J# (pronounced "J sharp"). Otherwise, as mentioned in Chapter 2, many other language choices are available to you ”about 20 of them, to be exact. Discussing all of those choices is beyond the scope of this retraining effort.

 

Regardless of which .NET language (or languages) you end up spending more time with, ultimately you will want to actually develop applications. After all, that is what you do, right? Taking a bilingual approach, the following section provides you with an opportunity to develop simple .NET applications.

^[4] Generally, the industry refers to VB .NET as a new language rather than just a new version of Visual Basic. Perhaps this is due to a little influence from the Microsoft marketing department, yet the changes are significant enough to justify the new language label.

^[5] You have got to admit, COBOL is a great language ”there is a reason why it has survived for so long. So please pardon my inclusive reference. I believe that I am speaking correctly on behalf of the average reformed mainframe programmer.