VS.2003 IDE Crash

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • harry
    #1

    VS.2003 IDE Crash

    Hi,

    After installing VS.2003, I just upgraded a VS.NET 2002 project to VS.NET
    2003.

    I upgraded because VS.NET 2003 is slow and buggy.

    However, I find VS.NET 2003 is worse in terms of bugs.

    For approx 20 hours everything was fine. Now suddenly I have IDE+Debugger
    (VB.NET) problems. Compilation was fine 20 hours ago, yet now it's not. I
    haven't installed any more software since installing VS.2003, and in fact I
    was just making small code changes when the problems appeared.

    First issue I find is
    Error - Office.com
    http://support.microsoft.com/default.aspx?scid=kb;en-us;831489


    Next issue and one I am still currently unable to resolve is, well I'm not
    sure what the cause is. The symptoms are:
    1) Create a new #Region - IDE crashes
    2) Move cursor to some Procedures and the "Method Name" combo doesn't
    change. If you click the method name combo, a heap of methods do not show
    up. These happen to be in a particular region. I removed the #Region/#End
    Region code, however the missing methods still do not appear in the method
    name combo.

    Well in fact the IDE seems to be completely screwed up now. I attempt to add
    a new procedure and the IDE crashes. I just tried switching from Debug to
    Release and the IDE crashed.

    I've completely uninstalled everything (VS.NET 2003, FrameWork, Office XP
    PIA's), rebooted, then reinstalled from scratch. Problem still exists.

    All that is left is to revert back to VS.2002 even thouigh it has issues at
    least I can work around them so far. How can a newer version be more
    unreliable than the older version. Whats more, there are other issues with
    VS.2003. Why can't we have timely updates, rather than waiting years for a
    large service pack.

    These issues don't appear on all projects. I just converted a very basic
    project and all is fine. So it must be something in the code, even though it
    was fine under VS.2002. But where in the code? Besides, why does code crash
    IDE and compiler? Shouldn't it simply show debug or compile error?

    Anyone have any ideas please?

    Thanks
    Harry




    Tags: None
    • Tom
      #2
      Re: VS.2003 IDE Crash

      I just went through 3 hours with a dude from microsoft on this one and
      believe it or not...the way that we got rid of the errors that were
      arrising was to close down the individual form/code windows within the
      IDE. Closing them all down cleared up all the errors and I was able
      to rebuild and the IDE works fine again. Hope this might help.

      "harry" <harry@nospam > wrote in message news:<OwpFneshE HA.3664@TK2MSFT NGP11.phx.gbl>. ..[color=blue]
      > Hi,
      >
      > After installing VS.2003, I just upgraded a VS.NET 2002 project to VS.NET
      > 2003.
      >
      > I upgraded because VS.NET 2003 is slow and buggy.
      >
      > However, I find VS.NET 2003 is worse in terms of bugs.
      >
      > For approx 20 hours everything was fine. Now suddenly I have IDE+Debugger
      > (VB.NET) problems. Compilation was fine 20 hours ago, yet now it's not. I
      > haven't installed any more software since installing VS.2003, and in fact I
      > was just making small code changes when the problems appeared.
      >
      > First issue I find is
      > http://support.microsoft.com/default...b;en-us;831489
      >
      > Next issue and one I am still currently unable to resolve is, well I'm not
      > sure what the cause is. The symptoms are:
      > 1) Create a new #Region - IDE crashes
      > 2) Move cursor to some Procedures and the "Method Name" combo doesn't
      > change. If you click the method name combo, a heap of methods do not show
      > up. These happen to be in a particular region. I removed the #Region/#End
      > Region code, however the missing methods still do not appear in the method
      > name combo.
      >
      > Well in fact the IDE seems to be completely screwed up now. I attempt to add
      > a new procedure and the IDE crashes. I just tried switching from Debug to
      > Release and the IDE crashed.
      >
      > I've completely uninstalled everything (VS.NET 2003, FrameWork, Office XP
      > PIA's), rebooted, then reinstalled from scratch. Problem still exists.
      >
      > All that is left is to revert back to VS.2002 even thouigh it has issues at
      > least I can work around them so far. How can a newer version be more
      > unreliable than the older version. Whats more, there are other issues with
      > VS.2003. Why can't we have timely updates, rather than waiting years for a
      > large service pack.
      >
      > These issues don't appear on all projects. I just converted a very basic
      > project and all is fine. So it must be something in the code, even though it
      > was fine under VS.2002. But where in the code? Besides, why does code crash
      > IDE and compiler? Shouldn't it simply show debug or compile error?
      >
      > Anyone have any ideas please?
      >
      > Thanks
      > Harry[/color]

        Comment

        • harry
          #3
          Re: VS.2003 IDE Crash

          Thanks for info.

          I already gave up and reverted back to VS.2002, however if I install VS.2003
          again in the future (which I would like to do when I have time) if the
          problem appears again I'll try your solution.


          "Tom" <thomas.Smith@q wedm.com> wrote in message
          news:cbc43754.0 409031458.7b22d e6a@posting.goo gle.com...[color=blue]
          >I just went through 3 hours with a dude from microsoft on this one and
          > believe it or not...the way that we got rid of the errors that were
          > arrising was to close down the individual form/code windows within the
          > IDE. Closing them all down cleared up all the errors and I was able
          > to rebuild and the IDE works fine again. Hope this might help.
          >
          > "harry" <harry@nospam > wrote in message
          > news:<OwpFneshE HA.3664@TK2MSFT NGP11.phx.gbl>. ..[color=green]
          >> Hi,
          >>
          >> After installing VS.2003, I just upgraded a VS.NET 2002 project to VS.NET
          >> 2003.
          >>
          >> I upgraded because VS.NET 2003 is slow and buggy.
          >>
          >> However, I find VS.NET 2003 is worse in terms of bugs.
          >>
          >> For approx 20 hours everything was fine. Now suddenly I have IDE+Debugger
          >> (VB.NET) problems. Compilation was fine 20 hours ago, yet now it's not. I
          >> haven't installed any more software since installing VS.2003, and in fact
          >> I
          >> was just making small code changes when the problems appeared.
          >>
          >> First issue I find is
          >> http://support.microsoft.com/default...b;en-us;831489
          >>
          >> Next issue and one I am still currently unable to resolve is, well I'm
          >> not
          >> sure what the cause is. The symptoms are:
          >> 1) Create a new #Region - IDE crashes
          >> 2) Move cursor to some Procedures and the "Method Name" combo doesn't
          >> change. If you click the method name combo, a heap of methods do not show
          >> up. These happen to be in a particular region. I removed the #Region/#End
          >> Region code, however the missing methods still do not appear in the
          >> method
          >> name combo.
          >>
          >> Well in fact the IDE seems to be completely screwed up now. I attempt to
          >> add
          >> a new procedure and the IDE crashes. I just tried switching from Debug to
          >> Release and the IDE crashed.
          >>
          >> I've completely uninstalled everything (VS.NET 2003, FrameWork, Office XP
          >> PIA's), rebooted, then reinstalled from scratch. Problem still exists.
          >>
          >> All that is left is to revert back to VS.2002 even thouigh it has issues
          >> at
          >> least I can work around them so far. How can a newer version be more
          >> unreliable than the older version. Whats more, there are other issues
          >> with
          >> VS.2003. Why can't we have timely updates, rather than waiting years for
          >> a
          >> large service pack.
          >>
          >> These issues don't appear on all projects. I just converted a very basic
          >> project and all is fine. So it must be something in the code, even though
          >> it
          >> was fine under VS.2002. But where in the code? Besides, why does code
          >> crash
          >> IDE and compiler? Shouldn't it simply show debug or compile error?
          >>
          >> Anyone have any ideas please?
          >>
          >> Thanks
          >> Harry[/color][/color]


            Comment

            Previous template Next
            Working...