Skip to content

Latest commit

 

History

History
36 lines (21 loc) · 2.07 KB

TROUBLESHOOTING.md

File metadata and controls

36 lines (21 loc) · 2.07 KB
Raw

What to do when VBA code in .bas files is detected as VB6 on GitHub?

Sometimes, VBA code can be detected as a Visual Basic 6.0 (VB6).

image

The reason for it is that a some code modules in the project don't have any VBA specific syntax and Github-Linguist (the GitHub service that calculates the language statistics) looks only at the content and extension of a file to determine the language used for that file.

To solve this issue and make sure that files in this repo are correctly identified as VBA, there are a mainly 3 options:

A. Add the language information as a comment at the top of the file.

(This is the best option in my opinion.) ie.:

Attribute VB_Name = "ComponentName"
'@Lang VBA

You can automate this process by using the VBA-Language-Annotation action.

B. Add the following in the .gitattributes file:

*.bas linguist-language=vba

The advantage of this method is that you only have to make the change in one place. The disadvantage is that this won't solve the problem for GitHub searches because the linguist-language attribute is not supported for searches 1. This means that if the VBA language filter is used in a search query, files that are currently labelled as VB6 still won't show up.

C. Change the file extension from .bas to .vba

That second extension avoids any ambiguity between VBA and VB6, but you won't be able to use the simple Export feature of the VBE since you'll need to perform the renaming on every export.

Footnotes

  1. This is due to the fact that Github Search relies on Go-Enry and Go-Enry doesn't support overrides at the moment. ↩