Re: Changing Namspace name causes VS2008 to be useless

Tech-Archive recommends: Speed Up your PC by fixing your registry



Hello Schneider,

Thank you for the information. The very large number of code lines in the
solution may be a reason for the crash. I suggest submitting a ticket in our
Visual Studio feedback site and talking to the Visual Studio product team
directly.
http://connect.microsoft.com/VisualStudio/
Below are some relevant crash reports of VS2008. I list them to assure you
that the product team will take your feedback seriously as always.
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=331020
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=291430
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=344235

Again, sorry for the inconveniences caused by our product. If there¡¯s
anything else I can do for you, please don¡¯t hesitate to tell me.

Regards,
Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

"eschneider" <eschneider@xxxxxxxxxxxxxxxx> wrote in message
news:%235ACifLxIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx

It's a .NET 2.0 project.
In VB.NET. All are class library projects except one which is a Windows
Form client.

This a multi project solution with about 250,000 lines of code.

Most of the problems seem to be with the background compiler.


"Jialiang Ge [MSFT]" <jialge@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:KXn04rHxIHA.4564@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Schneider,

I am very sorry to see that our product has caused you a lot of
inconvenience. The "crash" problem indeed looks an issue of Visual
Studio.
In order to fix it, I must first reproduce the issue on my side. In my
tests, I failed to "crash" Visual Studio 2008 by changing namespace in a
simple multi-project solution. Schneider, would you mind providing me
with
a more detailed step list to reproduce it? Would you please tell me the
project types, the .NET version and the error message when VS crashes?
Thank you very much for your time in helping us improve the product.
Other
community members will definitely benefit from your efforts. As soon as
the
issue can be reproduced, I will report it to the product team.

Thanks
Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
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.





.



Relevant Pages

  • Re: Changing Namspace name causes VS2008 to be useless
    ... The "crash" problem indeed looks an issue of Visual Studio. ... I must first reproduce the issue on my side. ... community members will definitely benefit from your efforts. ...
    (microsoft.public.vsnet.ide)
  • Re: Changing Namspace name causes VS2008 to be useless
    ... our Visual Studio feedback site and talking to the Visual Studio product ... Below are some relevant crash reports of VS2008. ... Microsoft Online Community Support ... I must first reproduce the issue on my side. ...
    (microsoft.public.vsnet.ide)
  • Re: The infamous R6025 runtime error
    ... the team could not find the reason why Visual Studio crashed. ... The crash itself ... > temporary solution, compile the code and run the executable? ... and add then use 'Open' to open the lone ...
    (microsoft.public.dotnet.languages.vc)
  • Re: The infamous R6025 runtime error
    ... thus causing the error report you ... the team could not find the reason why Visual Studio crashed. ... > crash itself occurs after VA has already closed. ... >> temporary solution, compile the code and run the executable? ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Crash in CAsyncSocket::Create
    ... There is no such thing as "a crash". ... I am compiling using MFC under Visual Studio 2005. ... with Windows XP Home, one with XP Professional and one with Windows ... structure is generated entirely by CAsyncSocket. ...
    (microsoft.public.vc.mfc)