DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 7 of 7

Thread: VB.Net Install

  1. #1
    Nex Guest

    VB.Net Install


    Hi there,

    I've decided to start toying with VB.Net in an effort to prepare for the
    movement from VB6.0 I've tried installing the Studio package on both Whistler
    Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no success.
    The win2k version keeps bombing out with the frontpage server extensions
    (says install failed for the extensions). Has anyone else had this issue
    and if so do you know how to fix it?

    Thanks,
    Nex


  2. #2
    Patrick Ireland Guest

    Re: VB.Net Install


    Nex,

    I've installed it successfully on Win2K Pro (don't know the SP level).
    However, the installation required the Windows Updater CD. You did
    not mention that you used it. Can't help beyond that.

    Pat


    "Nex" <Nex@nex.com> wrote:
    >
    >Hi there,
    >
    >I've decided to start toying with VB.Net in an effort to prepare for the
    >movement from VB6.0 I've tried installing the Studio package on both Whistler
    >Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no success.
    > The win2k version keeps bombing out with the frontpage server extensions
    >(says install failed for the extensions). Has anyone else had this issue
    >and if so do you know how to fix it?
    >
    >Thanks,
    >Nex
    >



  3. #3
    Nex Guest

    Re: VB.Net Install


    Pat,

    Thanks for the reply. I have used the windows updater CD - in fact that
    was where the install was stalling - it kept failing on the frontpage 2000
    server ext setup. I managed to bypass it by simply running the studio install
    from within one of the subfolders on the CD - of course I'm not sure what
    problems I have created doing it this way

    Thanks,
    Ian


    "Patrick Ireland" <ireland@airmail.net> wrote:
    >
    >Nex,
    >
    >I've installed it successfully on Win2K Pro (don't know the SP level).
    >However, the installation required the Windows Updater CD. You did
    >not mention that you used it. Can't help beyond that.
    >
    >Pat
    >
    >
    >"Nex" <Nex@nex.com> wrote:
    >>
    >>Hi there,
    >>
    >>I've decided to start toying with VB.Net in an effort to prepare for the
    >>movement from VB6.0 I've tried installing the Studio package on both Whistler
    >>Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no success.
    >> The win2k version keeps bombing out with the frontpage server extensions
    >>(says install failed for the extensions). Has anyone else had this issue
    >>and if so do you know how to fix it?
    >>
    >>Thanks,
    >>Nex
    >>

    >



  4. #4
    AJ Armstrong Guest

    Re: VB.Net Install

    Hi, Nex

    I've seen both your issues before.

    (1) .Net Beta 1 is not supported on XP Beta 1 or 2 (in fact, even odds you
    end up FDISKing if you try). I've been hearing that .NET Beta 2 will be
    supported on XP.

    (2) The .Net installer looks for a FrontPage Server Extensions hotfix before
    it permits install. Unfortunately, if you install WIN2KSP2 before running
    the Windows Component Update, it will detect that you do not need the hotfix
    (as it is included in SP2) and not install it. The end result - .Net will
    not install.

    Workaround - uninstall SP2, run the Windows Component Update, Install .Net,
    Reapply SP2. Worked for me. I've also seen notes here from people that
    skipped the wizard installers in .Net by going directly to subdirectories
    who claim that they were able to get .Net directly onto SP2. Haven't seen it
    myself.

    If you didn't check the "Backup files so I can uninstall" on the SP2
    installer, I'm not sure what you can do (others might be able to help).
    BTW - if that is the case, shame on you - ALWAYS keep an escape route when
    installing MS service packs.

    "Nex" <Nex@nex.com> wrote in message news:<3b0a8af4$1@news.devx.com>...

    >


    > Hi there,


    >


    > I've decided to start toying with VB.Net in an effort to prepare for the


    > movement from VB6.0 I've tried installing the Studio package on both

    Whistler

    > Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no

    success.

    > The win2k version keeps bombing out with the frontpage server extensions


    > (says install failed for the extensions). Has anyone else had this issue


    > and if so do you know how to fix it?


    >


    > Thanks,


    > Nex


    >





  5. #5
    Nex Guest

    Re: VB.Net Install


    Thanks everyone - its all working now. btw AJ I should be beaten with a big
    stick and hang my head in shame

    I just bypassed the autorun features and went straight for the VS Installer
    - that worked great.

    Thanks
    Nex

    ----i know i know i should have known better----

    "AJ Armstrong" <nospamfor_ajarmstrong@ttg-inc.com> wrote:
    >Hi, Nex
    >
    >I've seen both your issues before.
    >
    >(1) .Net Beta 1 is not supported on XP Beta 1 or 2 (in fact, even odds you
    >end up FDISKing if you try). I've been hearing that .NET Beta 2 will be
    >supported on XP.
    >
    >(2) The .Net installer looks for a FrontPage Server Extensions hotfix before
    >it permits install. Unfortunately, if you install WIN2KSP2 before running
    >the Windows Component Update, it will detect that you do not need the hotfix
    >(as it is included in SP2) and not install it. The end result - .Net will
    >not install.
    >
    >Workaround - uninstall SP2, run the Windows Component Update, Install .Net,
    >Reapply SP2. Worked for me. I've also seen notes here from people that
    >skipped the wizard installers in .Net by going directly to subdirectories
    >who claim that they were able to get .Net directly onto SP2. Haven't seen

    it
    >myself.
    >
    >If you didn't check the "Backup files so I can uninstall" on the SP2
    >installer, I'm not sure what you can do (others might be able to help).
    >BTW - if that is the case, shame on you - ALWAYS keep an escape route when
    >installing MS service packs.
    >
    >"Nex" <Nex@nex.com> wrote in message news:<3b0a8af4$1@news.devx.com>...
    >
    >>

    >
    >> Hi there,

    >
    >>

    >
    >> I've decided to start toying with VB.Net in an effort to prepare for the

    >
    >> movement from VB6.0 I've tried installing the Studio package on both

    >Whistler
    >
    >> Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no

    >success.
    >
    >> The win2k version keeps bombing out with the frontpage server extensions

    >
    >> (says install failed for the extensions). Has anyone else had this issue

    >
    >> and if so do you know how to fix it?

    >
    >>

    >
    >> Thanks,

    >
    >> Nex

    >
    >>

    >
    >
    >



  6. #6
    AJ Armstrong Guest

    Re: VB.Net Install

    Don't pull on Superman's cape, don't spit into the wind, don't pull the mask
    off the old Lone Ranger and don't ever, EVER install a Microsoft service
    pack without a full system backup and all the uninstall adn recovery options
    selected...;-)

    Glad you got it working.


    "Nex" <nex@nex.com> wrote in message news:3b17d769$1@news.devx.com...
    >
    > Thanks everyone - its all working now. btw AJ I should be beaten with a

    big
    > stick and hang my head in shame
    >
    > I just bypassed the autorun features and went straight for the VS

    Installer
    > - that worked great.
    >
    > Thanks
    > Nex
    >
    > ----i know i know i should have known better----
    >
    > "AJ Armstrong" <nospamfor_ajarmstrong@ttg-inc.com> wrote:
    > >Hi, Nex
    > >
    > >I've seen both your issues before.
    > >
    > >(1) .Net Beta 1 is not supported on XP Beta 1 or 2 (in fact, even odds

    you
    > >end up FDISKing if you try). I've been hearing that .NET Beta 2 will be
    > >supported on XP.
    > >
    > >(2) The .Net installer looks for a FrontPage Server Extensions hotfix

    before
    > >it permits install. Unfortunately, if you install WIN2KSP2 before running
    > >the Windows Component Update, it will detect that you do not need the

    hotfix
    > >(as it is included in SP2) and not install it. The end result - .Net will
    > >not install.
    > >
    > >Workaround - uninstall SP2, run the Windows Component Update, Install

    ..Net,
    > >Reapply SP2. Worked for me. I've also seen notes here from people that
    > >skipped the wizard installers in .Net by going directly to subdirectories
    > >who claim that they were able to get .Net directly onto SP2. Haven't seen

    > it
    > >myself.
    > >
    > >If you didn't check the "Backup files so I can uninstall" on the SP2
    > >installer, I'm not sure what you can do (others might be able to help).
    > >BTW - if that is the case, shame on you - ALWAYS keep an escape route

    when
    > >installing MS service packs.
    > >
    > >"Nex" <Nex@nex.com> wrote in message news:<3b0a8af4$1@news.devx.com>...
    > >
    > >>

    > >
    > >> Hi there,

    > >
    > >>

    > >
    > >> I've decided to start toying with VB.Net in an effort to prepare for

    the
    > >
    > >> movement from VB6.0 I've tried installing the Studio package on both

    > >Whistler
    > >
    > >> Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no

    > >success.
    > >
    > >> The win2k version keeps bombing out with the frontpage server

    extensions
    > >
    > >> (says install failed for the extensions). Has anyone else had this

    issue
    > >
    > >> and if so do you know how to fix it?

    > >
    > >>

    > >
    > >> Thanks,

    > >
    > >> Nex

    > >
    > >>

    > >
    > >
    > >

    >




  7. #7
    sabba Guest

    Re: VB.Net Install


    my option was a better one: make an image of the disk before installing .net
    b1, anyway i got the same problem and going directly to the vs installer
    seems having no side effects, not yet at least

    "AJ Armstrong" <nospamfor_ajarmstrong@ttg-inc.com> wrote:
    >Don't pull on Superman's cape, don't spit into the wind, don't pull the

    mask
    >off the old Lone Ranger and don't ever, EVER install a Microsoft service
    >pack without a full system backup and all the uninstall adn recovery options
    >selected...;-)
    >
    >Glad you got it working.
    >
    >
    >"Nex" <nex@nex.com> wrote in message news:3b17d769$1@news.devx.com...
    >>
    >> Thanks everyone - its all working now. btw AJ I should be beaten with

    a
    >big
    >> stick and hang my head in shame
    >>
    >> I just bypassed the autorun features and went straight for the VS

    >Installer
    >> - that worked great.
    >>
    >> Thanks
    >> Nex
    >>
    >> ----i know i know i should have known better----
    >>
    >> "AJ Armstrong" <nospamfor_ajarmstrong@ttg-inc.com> wrote:
    >> >Hi, Nex
    >> >
    >> >I've seen both your issues before.
    >> >
    >> >(1) .Net Beta 1 is not supported on XP Beta 1 or 2 (in fact, even odds

    >you
    >> >end up FDISKing if you try). I've been hearing that .NET Beta 2 will

    be
    >> >supported on XP.
    >> >
    >> >(2) The .Net installer looks for a FrontPage Server Extensions hotfix

    >before
    >> >it permits install. Unfortunately, if you install WIN2KSP2 before running
    >> >the Windows Component Update, it will detect that you do not need the

    >hotfix
    >> >(as it is included in SP2) and not install it. The end result - .Net

    will
    >> >not install.
    >> >
    >> >Workaround - uninstall SP2, run the Windows Component Update, Install

    >..Net,
    >> >Reapply SP2. Worked for me. I've also seen notes here from people that
    >> >skipped the wizard installers in .Net by going directly to subdirectories
    >> >who claim that they were able to get .Net directly onto SP2. Haven't

    seen
    >> it
    >> >myself.
    >> >
    >> >If you didn't check the "Backup files so I can uninstall" on the SP2
    >> >installer, I'm not sure what you can do (others might be able to help).
    >> >BTW - if that is the case, shame on you - ALWAYS keep an escape route

    >when
    >> >installing MS service packs.
    >> >
    >> >"Nex" <Nex@nex.com> wrote in message news:<3b0a8af4$1@news.devx.com>...
    >> >
    >> >>
    >> >
    >> >> Hi there,
    >> >
    >> >>
    >> >
    >> >> I've decided to start toying with VB.Net in an effort to prepare for

    >the
    >> >
    >> >> movement from VB6.0 I've tried installing the Studio package on both
    >> >Whistler
    >> >
    >> >> Beta 2 (Wishful thinking I know) and Win2kPro service pack 2 with no
    >> >success.
    >> >
    >> >> The win2k version keeps bombing out with the frontpage server

    >extensions
    >> >
    >> >> (says install failed for the extensions). Has anyone else had this

    >issue
    >> >
    >> >> and if so do you know how to fix it?
    >> >
    >> >>
    >> >
    >> >> Thanks,
    >> >
    >> >> Nex
    >> >
    >> >>
    >> >
    >> >
    >> >

    >>

    >
    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center