Re: VS 2005 questions

Ken wrote:
It is a shame that that there is no switch or configuration setting in VS 2005 that allows developers to write backwards compatible code for the 1.1 Framework, because then developers could adopt VS 2005 more quickly. By the time we are able to adopt it, you'll be up to VS 2007 (or whatever).

There is no legitimate reason (outside of marketing and/or totalitarian control) that the development environment can only target .Net 2.

Microsoft needs to take into account that there are consumers who legitimately cannot update software as critical as the .NET Framework without at least a year of internal testing. The way Microsoft has this set up, the tool is linked to the framework, so we cannot adopt VS 2005 until our client adopts .NET 2.0. It isn't wise for Microsoft to set the upgrade path as an all-or-nothing deal like this. If VS 2005 were not linked to .NET 2.0, you'd get half an update. Now you get none.

Microsoft's answer will be pure and simple: your customer needs to upgrade; we don't care and it shows.

This was not a good plan.

By linking the tools to the deployment environment you have gummed up the whole update process and you have lost business.

The problem is that they only lose business to themselves, there is no realistic alternative.

Our only realistic solution to the MS mess is for some mega-wealthy individual to purchase as much MS stock as possible so that they have a major voice on the board of directors, then seek a vote to break the company up into smaller, separate, and autonomous companies. I'll be waiting in my pumpkin patch for the Great Pumpkin to show up as well...
.

Relevant Pages

  • Re: OO programming - illumination? - whoopsie
    ... there is no enlightenment at all. ... project starts out with a framework ... -> use a straight implementation for the real problem (business ... > This does not negate the fact however, that developers only work on stuff ...
    (comp.lang.java.programmer)
  • Re: Cost of developing a device driver?
    ... you assume I was talking about kernel developers. ... I personally think DriverWorks is a poor framework. ... It left the underlying driver model in tact for the most ... >> community uses some type of framework, toolkit, class library or similar ...
    (microsoft.public.development.device.drivers)
  • Re: In need of .NET advocacy
    ... >> finds a different reason for the productivity gains of .Net. ... > I am not familar with the intricacies of the framework. ... >> average developers on them, if not now, then later during maintenance. ... programmer helping programmers. ...
    (microsoft.public.dotnet.general)
  • Re: Thinking Clearly
    ... WCF = "Indigo" Windows Communication Framework ... WCF and WF will require some IDE integration to help create ... to require some special design-time support to consume. ... developers will adopt the new tools. ...
    (borland.public.delphi.non-technical)
  • Re: Silly bug
    ... Prerequisites: Experience with Delphi. ... 3042 Complete ALM for the Microsoft .NET Framework ... technology that is designed to encourage developers to create easily ...
    (borland.public.delphi.non-technical)