> >>To Stano: Memory is very cheap these days, so get 2 GB and VS won't
> >>look like a memory hog. It works for me :)
> >>
> >>
> >
> > I don't think that solves his problem, as he uses
> 1.5GB of swap
> >with a project that shouldn't eat more than 200MB of ram tops.
> >
> >
> >
>
> I also don't believe more RAM will solve this problem. I will
> just be able to work couple of minutes longer.
>
>
> > Apparently no VB.NET users on this list. Perhaps
> Stano can post
> >on vb.net forums and ask there again to see if other vb.net
> users have the same problem.
> >
>
> Well. I reported this as a bug on http://labs.msdn.microsoft.com
> (http://lab.msdn.microsoft.com/productfeedback/viewfeedback.as
> px?feedbackid=422a870f-c7e0-4517-8055-4fec368a97b9)
> It seems it is a bug with parsing XML comments and has been
> reported long time ago with Beta products.
> (http://lab.msdn.microsoft.com/productfeedback/viewfeedback.as
> px?feedbackid=114c17a2-08ea-41ac-8cfd-9c86a53612df)
>
> People from Microsoft say, they already fixed it (last
> month), but only in theirs internal branch. Still they are
> not able to release some hot fix for it for users. (one would
> cry :'( ). I think this is so critical bug, that the fix
> should be released immediately, because people can't restart
> VS every hour (one user said he needs to restart it every 20 minutes).
As a customer of VS.NET you are entitled to call PSS and demand a fix.
As it's a bug, you won't have to give one of your
support calls either, and they'll give you the fix, at least that's what they
have to do. A support engineer will then work with you
to get you the hotfix.
Don't get me started on this process however. MS sits on hotfixes for
ages as if it will hurt us when we use these fixes,
yeah the bugs the fixes fix aren't harmfull :/
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
