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
- 305 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
SCM for NAV 2009 CC and NAV 2017?
AK
Member Posts: 226
in General Chat
Hi,
the company I'm working for (end user) finally wants to implement source control management, but we use different NAV versions. We use NAV 2009 classic client (SQL, but without service tier) with a couple of dozens databases and will hopefully soon have at least another one with NAV 2017. It will probably take several years until we migrate the old databases, so we need a one size fits all solution.
Additionally, the SCM should handle code from other sources, like SQL scripts, Visual Studio and so on. So a NAV only solution like the Object Manager is not usable.
I've seen a lot of SCM for NAV using GIT, Visual Studio and some Extensions for it, which might be exacly what we need. But those solutions seem to rely on the Powershell which is not available in NAV 2009. Is there a way to handle both our versions and the sources from other systems in one tool?
Thanks!
the company I'm working for (end user) finally wants to implement source control management, but we use different NAV versions. We use NAV 2009 classic client (SQL, but without service tier) with a couple of dozens databases and will hopefully soon have at least another one with NAV 2017. It will probably take several years until we migrate the old databases, so we need a one size fits all solution.
Additionally, the SCM should handle code from other sources, like SQL scripts, Visual Studio and so on. So a NAV only solution like the Object Manager is not usable.
I've seen a lot of SCM for NAV using GIT, Visual Studio and some Extensions for it, which might be exacly what we need. But those solutions seem to rely on the Powershell which is not available in NAV 2009. Is there a way to handle both our versions and the sources from other systems in one tool?
Thanks!
0