Re: C# runtime version

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

> > Is there any reason why you prefer v1.1 instead of v2.0?
> > You would think that v2.0 is far more superior compared to v1.1?
>
> I don't know about the OP, but there's such a thing as maintenance. If
> you're working on the maintenance cycle for a product, you really don't
> want to start changing runtime versions...
>
> Even if you're upgrading to a genuinely new version of your product,
> you'd need to do a lot of extra testing to make sure everything still
> works on 2.0.
>
But using the VS 2005 to create v1.1 .NET code will probably introduce more
problems than if you upgrade to v2.0.
If you need maintenance of a v1.1 framework, then you should stick to the VS
2003.


.

Relevant Pages

  • Fw: COBOL/LE runtime changes
    ... You haven't told us FROM what release of LE you are upgrading. ... that you are JUST moving from one maintenance level of LE 1.6 to another ... the same way it did in the past (i.e. referencing non-passed data in a COBOL ...
    (bit.listserv.ibm-main)
  • Re: Comics.com down again (officially - "for maintenance")
    ... "we're down for maintenance" page(specifically: ... we're upgrading the site and adding some cool new features. ... illustrated with a Working Daze panel about server upgrades). ...
    (rec.arts.comics.strips)
  • Re: LW "hobbyist pricing"
    ... * free minor Product Releases, such as upgrading from LispWorks 4.3 ... Maintenance Contracts last for a fixed period of one year and can only ...
    (comp.lang.lisp)
  • Re: Comics.com down again (officially - "for maintenance")
    ... "we're down for maintenance" page(specifically: ... we're upgrading the site and adding some cool new features. ... Business impact? ...
    (rec.arts.comics.strips)
  • Re: C# runtime version
    ... >> I don't know about the OP, but there's such a thing as maintenance. ... >> want to start changing runtime versions... ... >> Even if you're upgrading to a genuinely new version of your product, ... You can end up compiling it with the same ...
    (microsoft.public.dotnet.languages.csharp)