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
- 309 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
Adding DotNet3.5 to NAV2016 Docker Image
rsaritzky
Member Posts: 469
Hi all,
Is anyone using Docker containers to do development for NAV2016? We are building individual docker containers for each developer/enhancement. We have an addon from an ISV that uses an addin dll that needs DotNet3.5 in order to compile and run. The standard NAV2016 container images/artificacts use the Windows Server Core 2019 based image, which includes only DotNet 4.x support, not DotNet3.5. I've tried adding DotNet3.5 via the DISM command after the container is built (DISM.EXE /Online /Add-Capability /CapabilityName:NetFx3~~~~), and it shows as installed using "DISM.EXE /Online /Get-Capabilities", but when going into the Development Environment, the Addin doesn't show any Types available
If I load the addins to a regular non-docker development environment, the Addin's types display and work properly:
The Addin dll's appear in the list, so they are correctly added to the "Addins" folder within the container.
Any Docker experts out there who can help? Our Docker containers are built via pre-configured scripts, so ideally we'd like to add the dotnet 3.5 feature after the container has been built, but will consider all options.
The error when compiling or running is "Could not load file or assembly 'EasyPost.Net35,Version=1.0.0.0. Culture=neutral, PublicKeytoken=null' or one of its dependencies. The system cannot find the file specified."
Thanks
Is anyone using Docker containers to do development for NAV2016? We are building individual docker containers for each developer/enhancement. We have an addon from an ISV that uses an addin dll that needs DotNet3.5 in order to compile and run. The standard NAV2016 container images/artificacts use the Windows Server Core 2019 based image, which includes only DotNet 4.x support, not DotNet3.5. I've tried adding DotNet3.5 via the DISM command after the container is built (DISM.EXE /Online /Add-Capability /CapabilityName:NetFx3~~~~), and it shows as installed using "DISM.EXE /Online /Get-Capabilities", but when going into the Development Environment, the Addin doesn't show any Types available
If I load the addins to a regular non-docker development environment, the Addin's types display and work properly:
The Addin dll's appear in the list, so they are correctly added to the "Addins" folder within the container.
Any Docker experts out there who can help? Our Docker containers are built via pre-configured scripts, so ideally we'd like to add the dotnet 3.5 feature after the container has been built, but will consider all options.
The error when compiling or running is "Could not load file or assembly 'EasyPost.Net35,Version=1.0.0.0. Culture=neutral, PublicKeytoken=null' or one of its dependencies. The system cannot find the file specified."
Thanks
Ron
0