> On 7/14/06, Shawn Wildermuth <[EMAIL PROTECTED]> wrote:
> > Stoyan,
> >
> > This is off-topic a bit, but I have to say I use VS 2005
> 5-6 hours a
> > day since release (and before), and I have not seen what you are
> > seeing. Do you have WinFX (.NET 3.0) installed or did you have the
> > Beta installed before it? I am just curious...also, any
> chance any add-ins are doing it?
>
> Lucky you :)
>
> ~4-5 days in a working month VS would crash, but won't even
> bring the crash dialog - it just silently disappears.
> Sometimes it'd crash 3-4 times a day, and sometimes just
> once, more frequently in the win forms designer and rarely in
> the code window. I don't have WinFX installed, no betas at
> all (re-installed Windows and everything a month ago), no
> add-ins. A friend/colleague of mine has WinFX and all kinds
> of betas installed and experiences the same behavior. I can
> live with that because I press Ctrl-S often, but if I
> remember correctly, Microsoft
> *did* promise SP for Q1 this year (I think it was scheduled
> for February). So where the fuck is the service pack? :)
Yeah they promissed a lot. What I still find shocking is that we,
developers, aren't seen as normal customers who NEED a fix
for a problem. We know that software contains bugs, we just want the fix so we
can move on.
It's now said we'll see the SP1 for vs.net 2005 before the end of the
year. However I don't believe it anymore. The SP1 for
vs.net 2003 is said to be in beta for moooooonths now, however no word when it
will be released. IOW: won't be released as well.
Sorry to be sceptical, but frankly Microsoft's trackrecord is not that
great in this area to say the least.
What's so sad is that at vs.net 2005 launch in the netherlands, Soma
was here and asked me what they should do different (he
wanted to talk to me because I found an IDE crash bug 2 days before the launch
in the code editor). I said that MS should make
patches public, should work hard to give patches early as we NEED patches early
not after a year or 2 years. He promissed me they
would look into it.
Nothing has changed of course. It's business as usual: want a fix? Call
PSS and hope that what you experience is a bug.
Personally I'm rather sick and tired about this attitude and I can
fully understand you Stoyan. Last year I reported a bug
in the design time behavior of the datagridview. over 6 months later I
complained on my blog why no-one responded from MS. MS didn't
like that blogpost, but I'm beyond the point that I really care. The sad thing
is: they suddenly did respond... with a remark that
the bug was postponed BEYOND orcas. _beyond_. While it's a stupid bug my
customers run into and ask me if MY code is broken, which
isn't, it's MS code which is broken and I'm getting really tired explaining to
my customers it's someone else's fault, I just want
MS to fix what they broke and we all can move on.
And nothing helps: talking to the VP of development doesn't help,
talking to my mvp lead doesn't help (not his fault),
ranting in public doesn't help (on the contrary), discussing this with MS
employees doesn't help. I'm out of ideas what WILL help.
FB
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
