Re: Feedback ID 115267

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ok, in that case, product feedback is the wrong mechanism. That's more for
improving future products.

These groups might help, but it's hit or miss. For instance I don't have a
Windows 2000 instance with .NET 2.0 running anywhere, so I can't help.

For analyzing and resolving issues in shipping software, Microsoft support
is the way to go: http://support.microsoft.com/.

David


"AndrewEames" <AndrewEames@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8176792B-D4CC-4D24-B893-4F80E2098BE7@xxxxxxxxxxxxxxxx
Well yes... I posted a reproducible code sample and it crashes in the
CLR -
hence my request for some help from someone in MS - they seem to have
acknowledged it is a bug without actually describing what the bug is
Andrew

"David Browne" wrote:

So you don't want a workaround? You just want to know why it crashes on
Windows 2000?

To find out why it crashes would require reproducing and debugging it on
Windwos 2000.


David

"AndrewEames" <AndrewEames@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AB8FD220-057B-457F-A970-12D1EE6FDF67@xxxxxxxxxxxxxxxx
There is a code sample in the bug report - (its actually a stripped
down
version of code for a splash screen but that's irrelevant - I'd like to
know
why it crashes)
Andrew

"David Browne" wrote:


"AndrewEames" <AndrewEames@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2150CF58-A0C8-4E1B-AAA0-7E4047245556@xxxxxxxxxxxxxxxx
I filed a bug report and got the very unhelpful response that I
should
ask
here in the newsgroups for a workaround so here I am. If someone
from
Microsoft could explain the cause of the bug I filed and offer a
workaround,
I would be most grateful
Thanks
Andrew Eames

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=115267

For a workaround, you would need to describe what you are trying to
acomplish.

David








.

Relevant Pages

  • Re: Impossibly Slow Load-Time for Cross-Reference Window Items
    ... > fixed in SP1. ... > Clive's Word 2001 Workaround: ... > with MacWord than the reload bug itself. ... >> to go through before I can clear an update for installation on the ...
    (microsoft.public.mac.office.word)
  • Re: [Full-Disclosure] Microsoft Cries Wolf ( again )
    ... > The ZDNet article hit the point right on the head. ... While I agree, that you should at least provide some kind of workaround, I ... strongly disagree with criminalizing anyone who stands for full disclosure. ... "A bug like this could be triggered via a number of means...through e-mail, ...
    (Full-Disclosure)
  • Re: ~$Normal.dot
    ... An AutoRecovery Save file is named "AutoRecovery save of. ... What I meant to "complain" actually point out is the method in which Microsoft addresses their bugs. ... An explanation of why it sticks around ALWAYS and a workaround would in my opionion be the correct way of addressing this bug. ...
    (microsoft.public.word.application.errors)
  • Re: (another) infuriating IE bug
    ... I think this is a bug in IE, at least in ECMAScript terms it is a bug. ... undefined error - so f1 is not on the scope chain prior to its ... instructions to assign to a Reference with a null "Base" object by using ... French there is no word for "workaround"; ...
    (comp.lang.javascript)
  • Re: OE6 - Default Save Attachments Folder
    ... For a workaround to that problem, ... Unfortunately the> update itself has a bug that prevents the new fix from working. ... The> user-selected path for attachments is indeed written to the registry, but> the final character in the path name is dropped, which means it won't work. ... > Hal Hostetler, CPBE -- hhh@kvoa.com ...
    (microsoft.public.internet.mail)