How I let this sit in my inbox ignored for a week, I'm not sure....

The notion that Microsoft might abandon .NET is especially troubling for vendors who have wrapped their product strategies around the .NET brand. ISVs are confused when they perceive that Microsoft is apparently dropping a brand that they expected Microsoft to champion.
Such an action on Microsoft's part would hit hard because many ISVs have used the Windows .NET Framework to build products that fit into Microsoft's .NET vision, and the development cycle is too long for those ISVs to change their strategy now. With Microsoft appearing to back off from .NET, some ISVs fear that they've bet their own company's future on the wrong horse.
It's one thing for Microsoft to say that it's wagering its own success on a given product, but it's quite another thing for a small ISV to risk its business on the same product. Microsoft is a huge company that markets a plethora of products. If one of Microsoft's products--even a big, important one--fails, the company itself doesn't risk going out of business. However, if a small ISV stakes its success on a Microsoft product that subsequently fails, the ISV could easily fail as well.
I certainly sense the confusion.  There was no doubt that applying .NET to products like Exchange made absolutely no sense... and a quick search of any interview with MS Exchange spokespeople during the last few years proves that out -- they didn't know how to explain it, either.
Link: Windows & .NET Magazine: Is .NET dead? >

Post a Comment