VS.NET 2005 Vb Compiler Errors

[Russ]

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.EndIn itialization()
at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(I VbcHostObject
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

[Brian Henry]

I've found that almost all those errors are caused by bad code from the user
from .net 2003 source upgraded... if you start a project from scratch you
see basicly nothing like that because it prevents you from writing bad code
that would cause that now...
"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:5C**********************************@microsof t.com...

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.EndIn itialization()
at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(I VbcHostObject
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

[Russ]

So you're suggesting that Beta 2, three CTPs and a Release Candidate were
happy with my "bad code" but the developers decided to add a "let's bomb out
if we encounter a problem" feature in the final release?

"Brian Henry" wrote:

I've found that almost all those errors are caused by bad code from the user
from .net 2003 source upgraded... if you start a project from scratch you
see basicly nothing like that because it prevents you from writing bad code
that would cause that now...
"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:5C**********************************@microsof t.com...

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.EndIn itialization()
at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(I VbcHostObject
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

[Brian Henry]

ive had the same thing happen too... but when i dug into the code pretty far
i always traced it back to code the RTM see's as "inpropper" now... they
really made the compiler strict on a lot of things and the design
environment really strict on others...

"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:A8**********************************@microsof t.com...

So you're suggesting that Beta 2, three CTPs and a Release Candidate were
happy with my "bad code" but the developers decided to add a "let's bomb
out
if we encounter a problem" feature in the final release?

"Brian Henry" wrote:

I've found that almost all those errors are caused by bad code from the
user
from .net 2003 source upgraded... if you start a project from scratch you
see basicly nothing like that because it prevents you from writing bad
code
that would cause that now...
"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:5C**********************************@microsof t.com...

> 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.EndIn itialization()
> at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(I VbcHostObject
> 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
>
>
>
>
>
>
>

[Russ]

But this is happening when I'm editing code - and only sometimes - It works
fine for a few hours then bombs when I do something like press the Save
button. I'm very strict with my coding (I've even got rid of all the
warnings) and I'm not doing anything unusual. My colleague is getting the
same problem on an entirely different project! My guess is when other VB
developers start creating large projects, this will become a major issue with
this release. I'm going to call MSDN support and use one of my incidents -
this is losing me hours.

"Brian Henry" wrote:

ive had the same thing happen too... but when i dug into the code pretty far
i always traced it back to code the RTM see's as "inpropper" now... they
really made the compiler strict on a lot of things and the design
environment really strict on others...

"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:A8**********************************@microsof t.com...

So you're suggesting that Beta 2, three CTPs and a Release Candidate were
happy with my "bad code" but the developers decided to add a "let's bomb
out
if we encounter a problem" feature in the final release?

"Brian Henry" wrote:

I've found that almost all those errors are caused by bad code from the
user
from .net 2003 source upgraded... if you start a project from scratch you
see basicly nothing like that because it prevents you from writing bad
code
that would cause that now...
"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:5C**********************************@microsof t.com...
> 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.EndIn itialization()
> at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(I VbcHostObject
> 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
>
>
>
>
>
>
>

[Brian Henry]

yeah I have had forms one day work perfectly, and the next day they will not
load and show a white page with a pinkish read box for a title basicly
saying i cant load this there is an error... get that a lot randomly...

"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:FC**********************************@microsof t.com...

But this is happening when I'm editing code - and only sometimes - It
works
fine for a few hours then bombs when I do something like press the Save
button. I'm very strict with my coding (I've even got rid of all the
warnings) and I'm not doing anything unusual. My colleague is getting
the
same problem on an entirely different project! My guess is when other VB
developers start creating large projects, this will become a major issue
with
this release. I'm going to call MSDN support and use one of my
incidents -
this is losing me hours.

"Brian Henry" wrote:

ive had the same thing happen too... but when i dug into the code pretty
far
i always traced it back to code the RTM see's as "inpropper" now... they
really made the compiler strict on a lot of things and the design
environment really strict on others...

"Russ" <Ru**@discussions.microsoft.com> wrote in message
news:A8**********************************@microsof t.com...

> So you're suggesting that Beta 2, three CTPs and a Release Candidate
> were
> happy with my "bad code" but the developers decided to add a "let's
> bomb
> out
> if we encounter a problem" feature in the final release?
>
> "Brian Henry" wrote:
>
>> I've found that almost all those errors are caused by bad code from
>> the
>> user
>> from .net 2003 source upgraded... if you start a project from scratch
>> you
>> see basicly nothing like that because it prevents you from writing bad
>> code
>> that would cause that now...
>>
>>
>> "Russ" <Ru**@discussions.microsoft.com> wrote in message
>> news:5C**********************************@microsof t.com...
>> > 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.EndIn itialization()
>> > at Microsoft.Build.Tasks.Vbc.InitializeHostCompiler(I VbcHostObject
>> > 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
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>>

[Aaron Smith]

We experianced a problem with forms no longer loading in the new version
after creating a project from scratch with Beta 2. We loaded the release
version and all of the sudden the forms would no longer load... As we
investigated, there were two problems and both were programmer error.
They were there in Beta 2 but they never stopped us from loading forms
and editing them. Don't rule anything out.

Russ wrote:

But this is happening when I'm editing code - and only sometimes - It works
fine for a few hours then bombs when I do something like press the Save
button. I'm very strict with my coding (I've even got rid of all the
warnings) and I'm not doing anything unusual. My colleague is getting the
same problem on an entirely different project! My guess is when other VB
developers start creating large projects, this will become a major issue with
this release. I'm going to call MSDN support and use one of my incidents -
this is losing me hours.

--
---
Aaron Smith
Remove -1- to E-Mail me. Spam Sucks.