Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
VSC with strange error message
gtrennert2
Member Posts: 23
Hello
I'm on BC16 VSC 1.45.1
Have some code in my workspace - no error
And suddenly VSC finds an error on this line (that was in the workspace since a long time without error) :
{
"resource": "xxx",
"owner": "_generated_diagnostic_collection_name_#0",
"code": "AL0151",
"severity": 8,
"message": "Expression must be an Option",
"source": "AL",
"startLineNumber": 48,
"startColumn": 54,
"endLineNumber": 48,
"endColumn": 60
}
Its not the first time that there are strange behaviours of VSC
Does anyone have any Idea how I can get rid of this ?
Thanks
I'm on BC16 VSC 1.45.1
Have some code in my workspace - no error
And suddenly VSC finds an error on this line (that was in the workspace since a long time without error) :
if ProjTrace_FolderList.RunModal() = Action::LookupOK then beginThe error is :
{
"resource": "xxx",
"owner": "_generated_diagnostic_collection_name_#0",
"code": "AL0151",
"severity": 8,
"message": "Expression must be an Option",
"source": "AL",
"startLineNumber": 48,
"startColumn": 54,
"endLineNumber": 48,
"endColumn": 60
}
Its not the first time that there are strange behaviours of VSC
Does anyone have any Idea how I can get rid of this ?
Thanks
0
Answers
BC16 CU1 came out a day or two ago - might be worth trying. And I think they have also updated the AL compiler VSIX, which might also help.
Worst case, you can always use the appcop json settings to flip it to a warning or even make the message hidden.
RIS Plus, LLC
MVP - Business Apps