Peristiwa
17 Mac, 11 PTG - 21 Mac, 11 PTG
Sertai siri perjumpaan untuk membina penyelesaian AI berskala berdasarkan kes penggunaan dunia sebenar dengan rakan pembangun dan pakar.
Daftar sekarangPelayar ini tidak lagi disokong.
Naik taraf kepada Microsoft Edge untuk memanfaatkan ciri, kemas kini keselamatan dan sokongan teknikal yang terkini.
When you name an element in your Visual Basic application, the first character of that name must be an alphabetic character or an underscore. Note, however, that names beginning with an underscore are not compliant with the Language Independence and Language-Independent Components (CLS).
The following suggestions apply to naming.
Begin each separate word in a name with a capital letter, as in FindLastRecord
and RedrawMyForm
.
Begin function and method names with a verb, as in InitNameArray
or CloseDialog
.
Begin class, structure, module, and property names with a noun, as in EmployeeName
or CarAccessory
.
Begin interface names with the prefix "I", followed by a noun or a noun phrase, like IComponent
, or with an adjective describing the interface's behavior, like IPersistable
. Do not use the underscore, and use abbreviations sparingly, because abbreviations can cause confusion.
Begin event handler names with a noun describing the type of event followed by the "EventHandler
" suffix, as in "MouseEventHandler
".
In names of event argument classes, include the "EventArgs
" suffix.
If an event has a concept of "before" or "after," use a suffix in present or past tense, as in "ControlAdd
" or "ControlAdded
".
For long or frequently used terms, use abbreviations to keep name lengths reasonable, for example, "HTML", instead of "Hypertext Markup Language". In general, variable names greater than 32 characters are difficult to read on a monitor set to a low resolution. Also, make sure your abbreviations are consistent throughout the entire application. Randomly switching in a project between "HTML" and "Hypertext Markup Language" can lead to confusion.
Avoid using names in an inner scope that are the same as names in an outer scope. Errors can result if the wrong variable is accessed. If a conflict occurs between a variable and the keyword of the same name, you must identify the keyword by preceding it with the appropriate type library. For example, if you have a variable called Date
, you can use the intrinsic Date
function only by calling DateTime.Date.
.NET maklum balas
.NET ialah projek sumber terbuka. Pilih pautan untuk memberikan maklum balas:
Peristiwa
17 Mac, 11 PTG - 21 Mac, 11 PTG
Sertai siri perjumpaan untuk membina penyelesaian AI berskala berdasarkan kes penggunaan dunia sebenar dengan rakan pembangun dan pakar.
Daftar sekarangLatihan
Modul
Create readable code with conventions, whitespace, and comments in C# - Training
Write code that is easier to read, update and support using naming conventions, comments and whitespace.
Dokumentasi
Coding Conventions - Visual Basic
Learn more about: Visual Basic Coding Conventions
Keywords as Element Names in Code - Visual Basic
Learn more about: Keywords as Element Names in Code (Visual Basic)
Learn more about: Visual Basic Limitations