Tuesday, January 31, 2006 11:36 AM
I'm dead in the water with VB now. I've installed VS2005 on several VMs using out of the box XP Pros (SP2)- no AV, no patches etc. 100% pure + VS2005.
All of my solutions use multiple projects which seems to be something in common with this issue.
Is this specific to VB or does it also involve C#? I do NOT want to dump VB & move to C#, BUT I have to meet deadlines and this simply is not going to cut it.
MS saying "no release until it's ready" may be OK, however, "no release until it's ready and we're not going to provide an ETA" really isn't fair.
I am questioning what I've really gained by moving to 2005.... I had hoped the return of edit & continue would've wound up saving me time. Now I wind up spending more time focusing on saving the solution so I don't lose data.
Tuesday, January 31, 2006 1:16 PMModeratorWhat's the problem, exactly?!
Tuesday, January 31, 2006 6:25 PMModerator
Hi, James and Daniel,
I believe this is in reference to the 8013141e error (please correct me if I'm wrong), which is being tracked in the "Relase the Fix for Visual Basic Compiler Error &H8013141e&" thread elsewhere on this forum. This is a VB compiler error timing issue which mostly affects multiproject solutions on certain machines (please see the thread for more information) -- there are two other ways to encounter the bug but they are less likely to arise. Temporarily disabling Edit & Continue from Tools\Options, "Show All Options," Debugger tab may cause the problem to be hidden on your machine. We are testing a fix which covers all three ways to encounter this bug, and so far the prognosis is good -- we are running it through scenario testing and additionally are working with a set of customers to verify the fix. Until we verify the fix, though, it's just impossible to commit to releasing a fix, ETA, etc. My apologies for that -- I'm giving periodic updates on the aforementioned forum thread to pass along information as it becomes available.