Skip to content

BSL177 - Deprecated client application method.

Summary

Deprecated client application method.

Identifiers

Field Value
Rule code BSL177
Compatible alias DeprecatedMethods8310
Severity INFORMATION
Without configuration Yes
BSLLS JSON, ON mode without overrides Yes
Registry flag implemented Yes
Tags deprecated, compatibility

The implemented flag describes the registry; it does not certify verified BSLLS parity.

Behavior

  • The public identifier BSL177 and alias DeprecatedMethods8310 are stable.
  • The rule reports the cases documented on this page.
  • Suppressions and project configuration are applied before publication.
  • The rule requires neither an external analyzer nor network access.

Configuration and suppression

BSL### is the primary stable identifier. The compatible alias is accepted in select, ignore, and compatible block suppression comments.

[tool.onec-hbk-bsl]
select = ["BSL177"]
ignore = ["DeprecatedMethods8310"]

All three suppression families support both a current line and a range. When an opening comment follows code, it affects only that line. Use any one form:

  • noqa:
Value = "example";  // noqa: BSL177
  • bsl-disable:
Value = "example";  // bsl-disable: BSL177
  • compatible BSLLS form:
Value = "example";  // BSLLS:DeprecatedMethods8310-off

When the same opening comment is on a line by itself, it starts a range. Close it with the matching marker from the same family:

// noqa: BSL177
// code without this diagnostic
// noqa-enable: BSL177

// bsl-disable: BSL177
// code without this diagnostic
// bsl-enable: BSL177

// BSLLS:DeprecatedMethods8310-off
// code without this diagnostic
// BSLLS:DeprecatedMethods8310-on

To disable the rule until the end of the file, omit the closing noqa-enable, bsl-enable, or BSLLS:…-on marker.

Opening and closing markers must belong to the same family.

Diagnostic description

The rule checks unqualified calls to SetShortApplicationCaption, GetShortApplicationCaption, SetClientApplicationCaption, GetClientApplicationCaption, ClientApplicationBaseFontCurrentVariant, and ClientApplicationInterfaceCurrentVariant, including their Russian aliases listed above.

The diagnostic highlights the method name. Object-qualified calls, strings, comments, and longer names with the same prefix are skipped. Configuration compatibility mode does not gate this check.

For example, GetShortApplicationCaption() is reported; Object.GetShortApplicationCaption() is skipped.