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
- 300 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
Assembly List - Update an Assembly
Lefteyed
Member Posts: 43
Hey Guys
What is the nice and clean way to update an assembly from Visual Studio to Navision?
When I create my DLL file, I need to change the assembly name for Navision to registre that a new assembly is created.
If I just update the assembly number and/or file version, then it doesn't update it on the list of assemblies.
Thanks
/left
What is the nice and clean way to update an assembly from Visual Studio to Navision?
When I create my DLL file, I need to change the assembly name for Navision to registre that a new assembly is created.
If I just update the assembly number and/or file version, then it doesn't update it on the list of assemblies.
Thanks
/left
0
Best Answers
-
Lefteyed
Member Posts: 43
Worked a bit with it today along side with a colleague.
It seems to be working if File version/Assembly version is changed.
Create the new DLL fil.
Stop the tier, and make sure that nothing is connected to the old DLL file. (Close Development Environment as it can have connected to a copy of the DLL file in AppData)
Replace the old DLL file with the new one, start tier and it should now be working without the need to change name of the DotNet component.0
Answers
It seems to be working if File version/Assembly version is changed.
Create the new DLL fil.
Stop the tier, and make sure that nothing is connected to the old DLL file. (Close Development Environment as it can have connected to a copy of the DLL file in AppData)
Replace the old DLL file with the new one, start tier and it should now be working without the need to change name of the DotNet component.