G
Guest
This really is the worst Microsoft product I have ever had the misfortune to
work with. After the excellent feattures and stability of VS.NET 2002 and
2003, I was confident enough to start a major project in beta 2 of VS 2005.
But as I began to use the Beta I had major concerns about the product and
every subsequent CTP and the RC did nothing to put ease my concerns.
I even took out an MSDN universal subscription so I could begin using the
final release as soon as possible. I really wish I hadn't. I'm just
wondering if anyone ever bothered to test this product?
On several machines, most of which are clean builds, I am spending about 25%
of my development time dismissing VB Compiler Error Message boxes. If I
want to save before closing down VS.NET, I am subjected to at least another
20 VB Compiler Error Message boxes. When I am finally able to close my
solution I have to dismiss several more VB Compiler Error Message boxes
before I get a feeble apology.
This happens randomly on several machines. It's not a particularly complex
solution but occasionally (when I can get there) I can see the errors in the
error list. For each of the nine projects in the solution I get:-
Error 73 The "Vbc" task failed unexpectedly.
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT
E_FAIL has been returned from a call to a COM component.
at Microsoft.Build.Tasks.Hosting.IVbcHostObject.EndInitialization()
at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(IVbcHostObject
vbcHostObject)
at Microsoft.Build.Tasks.Vbc.InitializeHostObject()
at Microsoft.Build.Utilities.ToolTask.Execute()
at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode
howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup
projectPropertiesAvailableToTask, Boolean& taskClassWasFound) CommonObjects
So it's some COM component (at a rough guess). There are a couple of COM
components in there but only two of the projects reference them. I'm
getting this error for every single project. VS 2003 had no trouble with them
by the way.
There are some great additions to VS.NET 2005 which I really wanted/needed
to use. But if the basics (excuse the pun) no longer work, the new
additions and the entire product is nothing more than pointless.
Russ
work with. After the excellent feattures and stability of VS.NET 2002 and
2003, I was confident enough to start a major project in beta 2 of VS 2005.
But as I began to use the Beta I had major concerns about the product and
every subsequent CTP and the RC did nothing to put ease my concerns.
I even took out an MSDN universal subscription so I could begin using the
final release as soon as possible. I really wish I hadn't. I'm just
wondering if anyone ever bothered to test this product?
On several machines, most of which are clean builds, I am spending about 25%
of my development time dismissing VB Compiler Error Message boxes. If I
want to save before closing down VS.NET, I am subjected to at least another
20 VB Compiler Error Message boxes. When I am finally able to close my
solution I have to dismiss several more VB Compiler Error Message boxes
before I get a feeble apology.
This happens randomly on several machines. It's not a particularly complex
solution but occasionally (when I can get there) I can see the errors in the
error list. For each of the nine projects in the solution I get:-
Error 73 The "Vbc" task failed unexpectedly.
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT
E_FAIL has been returned from a call to a COM component.
at Microsoft.Build.Tasks.Hosting.IVbcHostObject.EndInitialization()
at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(IVbcHostObject
vbcHostObject)
at Microsoft.Build.Tasks.Vbc.InitializeHostObject()
at Microsoft.Build.Utilities.ToolTask.Execute()
at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode
howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup
projectPropertiesAvailableToTask, Boolean& taskClassWasFound) CommonObjects
So it's some COM component (at a rough guess). There are a couple of COM
components in there but only two of the projects reference them. I'm
getting this error for every single project. VS 2003 had no trouble with them
by the way.
There are some great additions to VS.NET 2005 which I really wanted/needed
to use. But if the basics (excuse the pun) no longer work, the new
additions and the entire product is nothing more than pointless.
Russ