VB in VS 2005: Solution fails to Build but no Error Reported

[Charles Law]

In the build output appears

========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========

However, the compiler does not generate any errors, and the Errors list is
empty.

This is an almost trivial program, but the compiler will not compile it and
will not tell me where the error is.

Has anyone else seen this?

Charles

[Bob Butler]

"Charles Law" <bl***@nowhere. comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

There is no "VB" in VS 2005, only "VB.Net" and that's not the same language
--
You need to ask in a newsgroup with "dotnet" in the name. This group id for
VB 6.0 and earlier and does not include VB.Net or VB 200x.

[Michael D. Ober]

Crap answer.
"Bob Butler" <no***@nospam.e verwrote in message
news:uV******** ******@TK2MSFTN GP03.phx.gbl...

"Charles Law" <bl***@nowhere. comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

There is no "VB" in VS 2005, only "VB.Net" and that's not the same
language
--
You need to ask in a newsgroup with "dotnet" in the name. This group id
for VB 6.0 and earlier and does not include VB.Net or VB 200x.

[Michael D. Ober]

Charles,

Create a new project of the type you want and then copy/paste your code to
the new project. If that doesn't work, please provide more details, such as
the code and project settings.

Mike Ober.

"Charles Law" <bl***@nowhere. comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

In the build output appears

========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ==========

However, the compiler does not generate any errors, and the Errors list is
empty.

This is an almost trivial program, but the compiler will not compile it
and will not tell me where the error is.

Has anyone else seen this?

Charles

[Bob Butler]

"Michael D. Ober" <obermd.@.alum. mit.edu.nospamw rote in message
news:et******** *********@newsr ead3.news.pas.e arthlink.net...

Charles,

Create a new project of the type you want and then copy/paste your code to
the new project. If that doesn't work, please provide more details, such
as the code and project settings.

But not here; this group is for VB 6.0 and earlier. VB.Net belongs in a
VB.Net newsgroup.

[Bob Butler]

"Michael D. Ober" <obermd.@.alum. mit.edu.nospamw rote in message
news:Or******** **********@news read3.news.pas. earthlink.net.. .

Crap answer.

LOL

Pot, Kettle.

[Robert Morley]

For those who hadn't noticed, it's being cross-posted to both a VB and a
VB.NET group. The regular m.p.vb.bugs should be removed in further
responses, as that group is reserved for "classic" VB (VB6 and earlier).
Rob

"Bob Butler" <no***@nospam.e verwrote in message
news:Oy******** ******@TK2MSFTN GP05.phx.gbl...

"Michael D. Ober" <obermd.@.alum. mit.edu.nospamw rote in message
news:et******** *********@newsr ead3.news.pas.e arthlink.net...

>Charles,

Create a new project of the type you want and then copy/paste your code
to the new project. If that doesn't work, please provide more details,
such as the code and project settings.

But not here; this group is for VB 6.0 and earlier. VB.Net belongs in a
VB.Net newsgroup.

[Michael D. Ober]

In that case, you should have put that in your original answer - not the
generic "VB doesn't exist in VS 2005" that the VB 6 fanatics spew. The
reality is that VC++ doesn't exist in VS 2005 in the same manner as it
existed in VS 6. I know because I have programs in both VB 6 and VC++ 6.
The VB 6 code has ported to VB 2005 a lot easier than the VC++ code did to
VC 2005. At some point, VB 6, with its mixed 16/32-bit COM model, will not
even be able to run on Windows. The end to VB 6 is definitely on the
horizon given that Longhorn (Windows 2008) will be the last version of
windows running 32-bit processors.

Mike.

"Bob Butler" <no***@nospam.e verwrote in message
news:Oy******** ******@TK2MSFTN GP05.phx.gbl...

"Michael D. Ober" <obermd.@.alum. mit.edu.nospamw rote in message
news:et******** *********@newsr ead3.news.pas.e arthlink.net...

>Charles,

Create a new project of the type you want and then copy/paste your code
to the new project. If that doesn't work, please provide more details,
such as the code and project settings.

But not here; this group is for VB 6.0 and earlier. VB.Net belongs in a
VB.Net newsgroup.

[Bob Butler]

"Robert Morley" <rm*****@magma. ca.N0.Freak1n.s parnwrote in message
news:un******** ******@TK2MSFTN GP02.phx.gbl...

For those who hadn't noticed, it's being cross-posted to both a VB and a
VB.NET group. The regular m.p.vb.bugs should be removed in further
responses, as that group is reserved for "classic" VB (VB6 and earlier).

Ahh, I had not seen that. Apologies for any confusion.

[Ralph]

"Michael D. Ober" <obermd.@.alum. mit.edu.nospamw rote in message
news:Xy******** ***********@new sread1.news.pas .earthlink.net. ..

In that case, you should have put that in your original answer - not the
generic "VB doesn't exist in VS 2005" that the VB 6 fanatics spew. The
reality is that VC++ doesn't exist in VS 2005 in the same manner as it
existed in VS 6. I know because I have programs in both VB 6 and VC++ 6.
The VB 6 code has ported to VB 2005 a lot easier than the VC++ code did to
VC 2005. At some point, VB 6, with its mixed 16/32-bit COM model, will

not

even be able to run on Windows. The end to VB 6 is definitely on the
horizon given that Longhorn (Windows 2008) will be the last version of
windows running 32-bit processors.

Mike.

Your enthusiasm for the future can be appreciated but your observations and
prophesies are a bit exaggerated.

The VC++ compiler included with VS2005 is quite capable of generating C++
sans any managed environment. The "reality" is while the IDE has changed
(features have different names, colors, placements, &etc.) there is no
substantial differences between VS6 and VS2005 when it comes to VC++. While
with VB the language itself has changed, VC++/CLI is an option.

The statement that VB6 code ports to VS2005 easier than VC++ code can not
possibly be based on any concrete personal experience. Pure fantasy.

That VB6 uses a 'mixed 16/32 bit COM model' is an extraordinary observation
and definitely would come as a surprise to any VB6 programmer.

As for the demise of VB6 - I think everyone is well aware that the VB
development platform is already over the horizon as far as MS is concerned.
However, the VB IDE and applications are supported on Vista, and according
to MS, apps will be supported on Windows Server 2008. Considering a support
life-time of 5 to 7 years, that means it will be at least 2013 before
current VB6 programmers need to be concerned.

[Which by the way, makes VB6 support almost 5x longer than "VB.Net - VS2003"
was supported. <g>]

It is true that MS has announced that "Windows Server 2008" is the last OS
to support 32-bit *processors*, BUT that doesn't mean 16-bit or 32-bit
*processes* won't be supported, or that 16/32-bit processors/processes won't
be supported with newer workstation OSs.

-ralph