Visual studio 2008 IDE application R6034 runtime error - MSDN news group moderator Please Respond.

[blogman]

I am getting a Visual studio 2008 IDE application R6034 runtime error. This
means that the IDE application is raising the error not the application I am
building. This means that Microsoft did not follow its own advice as listed
in http://msdn.microsoft.com/en-us/library/ms235560(VS.80).aspx and "build
with a manifest". The DLL in question seems to be msvcr8.0.dll which is the
VS2005 C runtime DLL. I am not sure why this is an issue in a VS2008 but it
is.

The following is text on the error message window:

Runtime Error!

Program: C:\Progr...

R6034
An application has made an attempt to load the C runtime library
incorrectly,
Please contact the application's support team for information

The error occurrs after trying to back out of VS 2008 SP1, .NET 3.5
Framework SP1, .NET 3.0 Framework SP2, .NET 2.0 Framework SP2 and all the
other releated components that the VS 2008 SP1 and .NET 3.5 Framework SP1 do
not properly clean up.

This means that the " application's support team" is Microsoft . Therefore,
I am hoping that one of the Microsoft moderators that monitor these news
groups will respond.

Forgive me for posting to multiple groups on this one but I posted in
microsoft.public.vstudio.general a few days ago and received no response. I
need an answer on this and so far the moderators have ignored it and
answered the soft balls posted after my original post. This means that this
must be an internal "politcal football" at Microsoft and I am caught in the
middle.

 

[Carl Daniel [VC++ MVP]]

Forgive me for posting to multiple groups on this one but I posted in
microsoft.public.vstudio.general a few days ago and received no
response. I need an answer on this and so far the moderators have
ignored it and answered the soft balls posted after my original post.
This means that this must be an internal "politcal football" at
Microsoft and I am caught in the middle.

There are no moderators on these newsgroups, nor are the newsgroups an
appropriate way to report a product problem to Microsoft.

If you require a response, your only sure bet is to call Microsoft Product
Support and open a support case.

In general, the preferred way to report bugs in the product is through
Connect: http://connect.microsoft.com/VisualStudio.

-cd

 

[Ben Voigt [C++ MVP]]

There are no moderators on these newsgroups, nor are the newsgroups an
appropriate way to report a product problem to Microsoft.

IF you are an MSDN subscriber AND you are using your registered posting
alias, then many of these groups guarantee a response from Microsoft within
the week (I think it's 3 working days). I think that Jeffrey Tan is the
Microsoft employee assigned to do so, but he's more of a liason than a
technology expert.

 

[blogman]

In other words, I pay a support fee for the honor of QAing their software.
Not exactly what I had in mind... We ended up re-imaging a development
environment because of this error. I should be paid for finding it - not the
other way around.

Also, to the MVPs who responded with procedural suggestions rather than
solutions or information about the problem at hand - I'll take that as an
indication that no-one has a clue about how this error could happen or how
to fix. This is indicative of the general malaise of sloth, incompetence and
mediocrity that seems to have permeated the inner core of the Microsoft
development community over the past several years, not surprisingly,
coincident with the Vista debacle. One can only hope that Windows 7.0 will
usher in better things such as a more workman-like pride in the quality of
the product line and less of a "whatever - chill out dude - have another
latte" attitude.

 

[Ben Voigt [C++ MVP]]

In other words, I pay a support fee for the honor of QAing their software.

Since MS hasn't jumped in to connect you with a product expert I can only
assume you aren't using a posting alias connected to your paid support.
Unless you're referring to the per-incident fee rather than the MSDN
subscription cost.

Not exactly what I had in mind... We ended up re-imaging a development
environment because of this error. I should be paid for finding it - not
the other way around.

Also, to the MVPs who responded with procedural suggestions rather than
solutions or information about the problem at hand - I'll take that as an
indication that no-one has a clue about how this error could happen or how
to fix. This is indicative of the general malaise of sloth, incompetence
and

Well, you didn't provide very much information.

And even if you did, we wouldn't likely have a shot at isolating it, much
less fixing it. MVPs don't have access to the Visual Studio source code (we
can get Windows source code if we feel like braving the licensing terms).

mediocrity that seems to have permeated the inner core of the Microsoft
development community over the past several years, not surprisingly,

MVPs are not Microsoft employees. We are a big part of the Microsoft
development community if that means the community who develop products using
Microsoft tools. But we don't have any bigger part in developing Visual
Studio than you do (i.e. sending in bug reports).

We are support from the community, not support for the community. And
calling us names isn't going to help you. Maybe next time we hear about
this error I can write back that blogman saw this before, but what a jerk,
he didn't fix it, he just left it for some unsuspecting user to run into and
waste their time with. But I won't because I know you haven't any control
over it.

coincident with the Vista debacle. One can only hope that Windows 7.0 will
usher in better things such as a more workman-like pride in the quality of
the product line and less of a "whatever - chill out dude - have another
latte" attitude.

I think the issue isn't the workman pride but the difficulty in getting in
touch with the workmen. Which we aren't.