Home/ Questions/Q 804185
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T23:52:38+00:00

I noticed that if I leave off the terminating double quote for a string

  • 0

I noticed that if I leave off the terminating double quote for a string constant in Visual Studio 2010, there is no error or even a warning, i.e.

Dim foo as String = "hi

However, the continuous integration tool we are using flags an error:

error BC30648: String constants must end with a double quote.

What’s going on here? Is there some language rule in VB.Net that makes a terminating double quote optional “sometimes”? Is there some setting in Visual Studio that will make it flag this as an error, so I can avoid “breaking the build” in this way?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Actually, historically, the BASIC language never REQUIRED a closing quote. This dates back to the 70’s. GW-Basic, BasicA, QBASIC, QuickBasic, even older Tandy and TRS-80 computers NEVER required a closing quote. This is nothing new. The reason for this is because BASIC is not a free flow language, like C or C#. This means that whenever a newline is found, BASIC knows that your string must end, quoted or not. Microsoft has purposely not enforced this rule in order to be compatible with older code.

    • 0