Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 301 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
Create NAVX-Package with AL-Files and Visual Studio Code
wanmat
Member Posts: 2
Hey there,
in early examples of Creating NAV Extensions with Visual Code you could see that you can create Extensions for NAV 2017 with Visual Studio Code, Creating AL Files and create and publish an NAVX-Extensions. When you now install Visual Studio Code and install the AL Language Vsix. the whole configuration is for NAV 2018 and create an APP-Package.
On official Microsoft Docs
NAVX-Packages (ExtensionV1) is descripted the old way, using txt-files and create delta-files. and then use the powershell to create an navx-package.
Only Extensionv2 is descripted using Visual Studio Code and Create APP -Extenstion. Therefore you need the Developer Service Endpoint of the NAV 2018 Service Tier which you don't have in NAV 2017.
So when reading the old Examples i don't get, how to create an navx-extension and how to get the symbol referecence without developer endpoint.
in early examples of Creating NAV Extensions with Visual Code you could see that you can create Extensions for NAV 2017 with Visual Studio Code, Creating AL Files and create and publish an NAVX-Extensions. When you now install Visual Studio Code and install the AL Language Vsix. the whole configuration is for NAV 2018 and create an APP-Package.
On official Microsoft Docs
NAVX-Packages (ExtensionV1) is descripted the old way, using txt-files and create delta-files. and then use the powershell to create an navx-package.
Only Extensionv2 is descripted using Visual Studio Code and Create APP -Extenstion. Therefore you need the Developer Service Endpoint of the NAV 2018 Service Tier which you don't have in NAV 2017.
So when reading the old Examples i don't get, how to create an navx-extension and how to get the symbol referecence without developer endpoint.
0