dotnet / dotnet/project-system
VB: .NET Standard class library project should honour defaults specified in Options window.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 415
- PR merge metrics
- No merged PRs in 30d
Description
**Version Used**:
Visual Studio Community 2017 v15.4.4
**Current Behavior**:
Create a new .NET Standard 2.0 class library in VB and open the project settings page, you will see the following:
The various compile options (e.g. `Option Strict`) are actually set as follows on my machine under `Tools > Options > Project and Solutions > VB Defaults` :
**Expected Behavior**:
The values for `Option Strict` and `Option Compare` in a newly created .net standard class library should match those in the options window (in my case the options set `Option Strict On` but the library was created with it set to `Off`, and `Option Compare Text` but the library was created with it set to `Binary`).
The discrepancy could lead to very subtle bugs in VB (e.g. `Option Compare` affects case sensitivity of string comparisons) that would be hard to debug unless one knew the project settings were incorrectly initialized relative to the defaults they set in the Options window.
CC: @davkean
Contributor guide
Assessment
This issue has not been assessed yet.