Announcement

Collapse
No announcement yet.

I said it would happen - Goodby DLL Hell - Hello NET Hell

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • I said it would happen - Goodby DLL Hell - Hello NET Hell

    "Visual Studio 2005 SP1 will run on Vista but will likely have a few
    compatibility issues. We are working with the Vista team to understand
    those, to provide workarounds where possible and also work on
    providing you with a set of fixes beyond SP1."

    "However, we will not support Visual Studio .NET 2002 or Visual Studio
    .NET 2003 as development environments on Windows Vista."
    http://blogs.msdn.com/somasegar/arch...26/772250.aspx

    A lot of things in NET are brilliant but I think it will turn into a
    maintenance monster that even MS can't sustain.

    Every application may need to be recompiled as a version goes out of
    scope, which may break some things.
    (That may also mean that all third-party tools will have to match,
    which also may break things.)

    That also means that all users will have to upgrade their runtime.
    If everything doesn't sync right - broken app.

    Just upgrading a service pack may break add-ons until they are
    upgraded to match.

    If something changes in Vista, the whole NET environment has to change
    to match.

    It took years to finally get Windows basically working right, Windows
    XP, and then they had a brilliant idea.
    It will take many years to get Vista right, if they ever get it out
    the door.
    That means the NET environment will be in a constant state of flux.


    ------------------

  • #2
    I don't understand.
    The entry in the blog only talk about incompatibility of the dev environment (witch I don't find strange, in the MS universe, so to speak), not about problems running .NET apps.
    I mean, nothing really new from that post.

    Bye!

    ------------------
    Try Online TrID file identifier! Recognize over 2.200 filetypes and counting...
    Give a powerfull scriptable Lua interface to your application with PowerBLua
    Leakout - Firewall outbound control tester - BitmapRip Extract/recover bitmaps from any file!

    [This message has been edited by Marco Pontello (edited September 27, 2006).]
    -- The universe tends toward maximum irony. Don't push it.

    File Extension Seeker - Metasearch engine for file extensions / file types
    Online TrID file identifier | TrIDLib - Identify thousands of file formats

    Comment


    • #3
      Along the DLL hell subject.
      The Visual Basic 6 SP6 runtime library may have eliminated
      the problem with VB6 since it will not be changed.
      Have heard VB SP6 is included with XP. Is this true?



      ------------------

      Comment


      • #4
        Can't be as VB SP6 was released later than Win XP. So, an unpatched XP or XP SP1 (don't know for sure) might not include VB SP6 runtimes.

        Knuth

        ------------------
        http://www.softAware.de

        Comment


        • #5
          I miss my Tandy 1000SX... life was so much simpler back then.


          ------------------
          Paul Squires
          FireFly Visual Designer, Cheetah Database System, JellyFish Pro Editor
          www.planetsquires.com
          Paul Squires
          FireFly Visual Designer (for PowerBASIC Windows 10+)
          Version 3 now available.
          http://www.planetsquires.com

          Comment


          • #6
            I might be getting a bad case of the “old fart syndrome” BUT,
            I think the all-in-one runtime is a bad idea.

            If things are kept in the smallest functional components, just replace bad components.

            NET car; have a flat – replace car.


            ------------------

            Comment


            • #7
              XP SP2 and higher include VB6 runtime.
              Run VBRUNSP6.EXE and let Microsoft do the installation.
              Full download below: http://www.microsoft.com/downloads/details.aspx?familyid=7B9BA261- 7A9C-43E7-9117-F673077FFB3C&displaylang=en

              Since this is the final update, I agree, no more DLL hell.




              [This message has been edited by Mike Doty (edited September 27, 2006).]

              Comment

              Working...
              X