This week, CIO Republic features a roundup of Tim Landgrave’s columns on Microsoft.Net. Landgrave’s View returns next week.
Microsoft’s .NET platform is more than just a development environment or a few new servers. Microsoft’s vision is that .NET will shift the Internet’s focus from individual sites or devices to “constellations of computers, devices, and services that work together to deliver broader, richer solutions,” allowing people to “have control over how, when, and what information is delivered to them.”
TechRepublic columnist Tim Landgrave has followed the development of Microsoft’s new strategy since it was first announced last year.
To help you prepare for this new Microsoft strategy, we’ve put together a list of Landgrave’s past columns so that you’ll have all the information you need to implement this new development technology right at your fingertips.
What is .NET? And what will it do for the enterprise? In “The .NET initiative: Microsoft puts the e in NT,” Landgrave explains how .NET evolved and provides examples of how it may affect your company’s use of the Internet.
He also explains what development issues .NET will solve for companies that are writing Windows applications in “How .NET changes your development design.”
Preparing for .NET
.NET will change your enterprise landscape, including the skills your IT staff will need to create and deploy applications. How can you prepare? Here are three articles that deal with readying your staff for .NET:
- “Network engineers can prepare for Microsoft .NET”
- “Three keys to help developers unlock the Microsoft .NET platform”
- “Target training to help developers prepare for Microsoft .NET”
.NET vs. the status quo
Visual Basic developers are worried that VB.NET will be a rehash of the mid-80s OS/2 dilemma, when developers had to hassle with moving applications from Windows application program interface (API) to the OS/2 API.
In “Why .NET will not become Microsoft’s next OS/2,” Landgrave contends that although moving to VB.NET will involve changes, Microsoft has taken steps to ease the transition.
Another related concern is how Microsoft’s settlement with Sun might affect Microsoft’s development environment. In “Microsoft – Java = .NET,” Landgrave contends that Microsoft anticipated this problem and has already created a solution with .NET.
What topics would you like to see columnist Tim Landgrave address? E-mail us your ideas and we’ll pass them along.