VS crash after debug

Very often my VS2005 pro crashes after a debug.
I run ASP.NET debug, and all works well. Then I stop it, and all it's also
ok. Then, when I try to edit some code, it crashes and I need to kill it,
restart, reload project, etc.
it seems that the problem is with vb compiler integration, but I'm not sure.
Is this a known problem? Is there some solution? I cannot spend all my time
to reload VS and projects!Hi Trapulo,
I don't know if this will be of any help, but I used to have this problem
with VS 2003 and .Net 1.1
my solution in the end, was to rebuild the machine, re-install VS and then
create a Norton Ghost partition so that I'd never have to do it again
as I say maybe you thought of all this, but it helped in my case, as I never
got the problem again.
Regards
Thanks for Charles's input.
Hi Trapulo,
Is this the first time you encountered the error or did the IDE used to
work well and just broke after applied some certain changes? Based on my
research, there's no such known issue, so if it's the behavior ever since,
there may has something incorrect with the installation.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:HmnZi4mUGHA.4716@.TK2MSFTNGXA01.phx.gbl...
> Thanks for Charles's input.
> Hi Trapulo,
> Is this the first time you encountered the error or did the IDE used to
> work well and just broke after applied some certain changes? Based on my
> research, there's no such known issue, so if it's the behavior ever since,
> there may has something incorrect with the installation.
Hi,
Charles's solution is not very confortable :(
However, I had this problem since first projects with VS 2005. Recently the
problem has grow, I think as projects that I'm working on (some solutions
with some asp/dll related projects and a lot of code).
If this can help, I've this problem either with a project started with
Vs2005, than an other createn on VS2003 and now upgraded. I'm working on a
Windows Server 2003 english, with VS 2005 pro english.
I'm debugging using VS's ASP NET development integrated service.
thank you
Thanks for your response Trapulo,
Charles' suggestion is specific to VS 2003/.NET 1.1. Also, since you
mentioned that the problems start from the begining and you haven't applied
any changes on it, I think it is likely a installation problem. Have you
any other dev machines encountering the same problem with similiar
environment?
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:9QQEb8xUGHA.4332@.TK2MSFTNGXA01.phx.gbl...
> Thanks for your response Trapulo,
> Charles' suggestion is specific to VS 2003/.NET 1.1. Also, since you
> mentioned that the problems start from the begining and you haven't
> applied
> any changes on it, I think it is likely a installation problem. Have you
> any other dev machines encountering the same problem with similiar
> environment?
No, I've only this dev machine with VS 2005 :(
Thanks for your response Trapulo,
That'll be a bit hard to isolate the problem. Anyway, you can try start
from the repair install, if still no lucky, we may have to consider
reinstalling it.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
I noticed that this happens always when I try to edit some row on my DAL
layer. Can this help?
All layers are in same solutions, and asp.net project references them.
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:0NsishKVGHA.2428@.TK2MSFTNGXA01.phx.gbl...
> Thanks for your response Trapulo,
> That'll be a bit hard to isolate the problem. Anyway, you can try start
> from the repair install, if still no lucky, we may have to consider
> reinstalling it.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
Thanks for the further followup Trapulo,
I think this can help make the reproduce process much clearer and
simplified , however, this still indicate that there is something incorrect
with the IDE's debugging component. So far we haven't any other definite
means to get the root cause from the appearance.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Can this say something?
"Unable to recover from the following error: System Error &Hc0000005&
(Visual Basic internal compiler error). Save your work and restart visual
studio."
Then I may kill it becasuse it continue to request if it can send a report
to MS. Either if I click ok or not, the request is showed an other time and
so on
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:wmzrWauVGHA.2428@.TK2MSFTNGXA01.phx.gbl...
> Thanks for the further followup Trapulo,
> I think this can help make the reproduce process much clearer and
> simplified , however, this still indicate that there is something
> incorrect
> with the IDE's debugging component. So far we haven't any other definite
> means to get the root cause from the appearance.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>