 05 Jan 2006, 11:42 AM UTC
|
|
João Santa Bárbara
Posts 23
|
|
|
|
Hi all
i just want to know when is going to be released the fix for visual basic compiler error &H8013141e& ? this is already reported in the microsoft productfeedback site.
i think this is a very urgent patch that must be released asap
and please do not repond that i should go back to vs.2003 because i have lots of code developed in VS 2005 to framework 2.0 ..
JSB
PS: this error pisses me of, i need to restart VS.IDE every 5 minutes. i think this is too bad for a recent relesase product ( its full of Bugs ).
|
|
|
|
|
Report Abuse
|
|
|
|
|
05 Jan 2006, 10:58 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
Hi, João,
This is a good opportunity (in the interests of total transparency) to give an update on this bug. We’re still having an insanely difficult time reproducing the problem – every time we get a solution on our machines, the problem goes away. Or, if the problem does occur, it only does so once or twice, not enough to actually nail down the problem. We’ve even scheduled customer visits to track this down on user’s machines, only to find that the problem no longer repros. (For example, one person turned off edit and continue and then turned it on again, only to find that the problem didn’t repro, but that doesn’t seem to be a consistent experience.)
I’ve got one developer working full time on this, doing nothing else except investigating this bug, and he’s being assisted by two other developers who’ve been helping on an as-needed basis. So far, we’ve learned that a data structure that Visual Studio uses internally is being inappropriately modified, but we can’t yet determine why. The good news is that we’ve got another repro to play around with right now, and I have high hopes that we’ll get to the bottom of this shortly.
A service pack for Visual Studio 2005 is planned for this summer. For various reasons, I can’t ever guarantee that a given fix will make it into a given release; however, given the scope of the problem (a large number of reports on this bug, although most people seem unaffected, including our own installments, which is also puzzling), we have a huge focus on getting this one fixed and a vested interest in making certain that people experiencing this bug can get that fix – this is the highest-priority code defect that we have currently. Regarding your mention of a “patch,” though, it’s just too premature to speculate on any delivery mechanism until we understand the cause of the problem and what’s required to fix it.
When we do have a solution to the problem, we will make sure to post an update on this forum, and in any event we will continue to keep you updated.
My continued apologies for those of you who are experiencing this problem.
--Matt Gertz--*
VB Compiler Dev Lead
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
05 Jan 2006, 11:35 PM UTC
|
|
João Santa Bárbara
Posts 23
|
|
|
|
Hi Matt.
Thks for the explanation.
I will try to make a dummy solution to see if i can reproduce the problem, but in my current solution this happens when i´m in debug mode and i made a few changes in the code ( i have a few projects ) . and sundently i have to stop the program. when i do this the error happens.
if this could help' i´m doing a few usercontrols, and inside of those controls i have an SQL connection, my own public classes , lots of methods and i´m using infragistics Components for VS 2005, and i´m using a windows xp sp2 English with all current settings in portuguese (portugal ) ( keyboard location etc ) .
and more i have projects depending from other projects and depending from others again ...
this is the best i can explain, as i said i will try to make a solution to try to reproduce the problem if i can reproduce the problem in my dummy solution i will post in this forum.
thks
JSB
PS: this Error is a realy pain in the *** ..
|
|
|
|
|
Report Abuse
|
|
|
|
|
06 Jan 2006, 8:24 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
Well, for a bit of good news: in the wee hours of the morning, the developer working on this figured out what the problem is – as you might suspect from the fact that most people aren’t running into the problem and that it’s hard to repro anyway, it’s a timing issue, and a rather convoluted one at that. We are now determining the best way to fix the problem (one that doesn’t compromise performance, for example).
--Matt--*
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
11 Jan 2006, 3:21 PM UTC
|
|
Garry W
Posts 12
|
|
|
|
I am having the same problem.
Anyword on the solution?
Garry
|
|
|
|
|
Report Abuse
|
|
|
|
|
16 Jan 2006, 9:22 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
Yes – we are in the process of testing a fix (yeah!).
--Matt--*
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
17 Jan 2006, 10:25 AM UTC
|
|
João Santa Bárbara
Posts 23
|
|
|
|
Great ... JOB Guys ...
When is going to be released ???
JSB
|
|
|
|
|
Report Abuse
|
|
|
|
|
17 Jan 2006, 9:47 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
Since we are still investigating – in this case, doing verification – we still cannot discuss such things. The reason is that verification may determine that the fix is incorrect, in which case we’re no better off than we were before, and so setting expectations on delivery or timing would be a bad thing. (That’s a rotten response, I know, but the only one I can give right now.)
--Matt--*
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
18 Jan 2006, 3:01 PM UTC
|
|
JCichocki
Posts 6
|
|
|
That seems to make sense. Another error I get before compiler crash is
one of the COM obejct is busy errors. I can't remember the exact
reworking this project in C# for the time being. I will see if I can
reproduce that tonight, so I can be a little more specific.
Another thing I noticed is it only seems to happen on solutions that
have more then 1 project. I was working on 2 solutions, 1 just a single
exe and the had 6 or so projects. The single project solution never got
this crash until I added another project, in which I got some same
error consistently.
|
|
|
|
|
Report Abuse
|
|
|
|
|
18 Jan 2006, 7:00 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
That’s exactly right. The fundamental problem (or so we believe – I won’t commit on that until the testing is done :-)) is a race condition between two or more projects, which leads to one trying to grab resources (say, in your case, a COM object used internally) that aren’t marked as available yet.
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
19 Jan 2006, 7:21 AM UTC
|
|
BartonFinkle
Posts 6
|
|
|
Can't you just release it anyway? I can't imagine that the damage it
might do would cause my experience with the product to be worse than
having to restart the IDE (and manually close a handful of
Webdev.webserver processes) every time I exit a debug session.
Please. I don't know how much more of this I can take.
|
|
|
|
|
Report Abuse
|
|
|
|
|
19 Jan 2006, 2:44 PM UTC
|
|
JCichocki
Posts 6
|
|
|
|
Cool sounds like you are right on track for 1 of the issues I was running into, but they are probably both related. The COM dialog I was getting was one of the switch-to/retrys. I haven't seen them since my VB6 days.
I have a question with this though, in these projects I have no references to COM at all. The only thing that would be doing anything COM related would be Visual Studio or the framework interenally. Is this a VB only thing (I was not running into the same issues with C#, I know VB had backwards compatilble references to vb 6's COM err objects)?
Sounds like you are having better success duplicating this, if you need anything else though please let me know. I can reached via email at joe.cichocki AT gmail.com.
Looking foward to getting this, then we can finally upgrade to 2005 at work and I could really use generics.
|
|
|
|
|
Report Abuse
|
|
|
|
|
19 Jan 2006, 4:27 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
We use COM internally – the packages which make Visual Studio are either COM objects or work with COM via interop. So when you see that COM message, that’s the likely culprit.
Thanks for the info, BTW!
--Matt--*
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
19 Jan 2006, 4:47 PM UTC
|
Matthew Gertz MS
Moderator
Posts 304
|
|
|
Unfortunately, there’s just no way that we can release any code except via official releases which have been fully vetted by Quality Assurance, have security passes done, etc. There are several reasons for this, but the primary one is that *any* bits that get released need to be supported – not just by us, but by product support teams, third-party vendors who have tools targeting that binary (in our case, that would include the Refactor! guys, among others), and of course Visual Studio itself. Users may not necessarily upgrade when more “official” bits come out (which may include other fixes as well), which means we’re then in a situation where we’re supporting multiple versions of a binary which are all mostly identical but just different enough that subtle problems can manifest. That means worse support for everyone. Accordingly, we cannot release “interim” bits, nor can we guarantee a fix will be made available for an issue until we are fully confident that we have solved a problem. Sometimes, we work with customers to test fixes on their machines, but those bits are reverted after the test.
I can appreciate how frustrating this is – I’ve certainly been on the receiving end myself any number of times – and I’m very sorry for the problems that some folks are running into around this issue. However, the code problem that we’re addressing involves code that is fundamental to both the compiler and the F5-debugging experience– that is, the code changes we’re testing (if those indeed turn out to solve the problem) are right smack dab in the middle of the core of that code. Thus, every single scenario which uses the VB compiler and which debugs code could be affected by any change we make (be they single-project or multiple-project solutions), which is why we need to be so careful. We have automation that covers tens of thousands of those scenarios, but as noted previously, this is a timing issue which is difficult to repro, so absolute diligence is required.
Again, my apologies to those who are running into this. When I have more info that I can share, I will of course follow up with this group.
--Matt--*
Matthew Gertz, Development Manager, Microsoft Visual Basic
|
|
|
|
|
Report Abuse
|
|
|
|
|
21 Jan 2006, 5:39 PM UTC
|
|
steverino_can
Posts 3
|
|
|
I am having the same problem. Happens in both Visual Studio 2005
Express VB and Visual Studio 2005 Professional VB.
This is really impacting programmer productivity.
Microsoft .... you need to get a service release/fix out asap!
|
|
|
|
|
Report Abuse
|
|
|
|
|
MSDN Forums » Visual Basic » Visual Basic IDE » Re: Relase the Fix for Visual Basic Compiler Error &H8013141e&
|
|
|
Subscribe to RSS
|
|