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
- 302 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Problem getting VS Code to attach to correct service
Sunset
Member Posts: 201
On a local machine I have installed BC140 straight out of the box. So I have BC140 service, I have the webserverinstance and development client. I can connect through the client and browser, everything is good.
For customer development purposes I have created a secondary service CUST-BC140 specified different portnumbers to avoid portsharing, and used New-NAVWebServerInstance to create a second webserver that connects to my CUST-BC140 nav service. Everything looks fine, I can connect to the customer database using the old client, and I can connect to http://localhost:8080/DynamicsNAV140-CUST/ on the browser.
But when I create a new AL:GO project in VSCode and point it to my customer service it still locks onto the old/original BC140 installation when trying to debug.
What am I doing wrong, or where should I search for the problem?
launch.json snip
{
"server": "http://localhost",
"serverInstance": "CUST-BC140",
"port": 8049
}
For customer development purposes I have created a secondary service CUST-BC140 specified different portnumbers to avoid portsharing, and used New-NAVWebServerInstance to create a second webserver that connects to my CUST-BC140 nav service. Everything looks fine, I can connect to the customer database using the old client, and I can connect to http://localhost:8080/DynamicsNAV140-CUST/ on the browser.
But when I create a new AL:GO project in VSCode and point it to my customer service it still locks onto the old/original BC140 installation when trying to debug.
What am I doing wrong, or where should I search for the problem?
launch.json snip
{
"server": "http://localhost",
"serverInstance": "CUST-BC140",
"port": 8049
}
Don't just take my word for it, test it yourself
0
Answers