Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 270 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
Options
Are there plans for NAV dev to move to .NET and VS?
Charleh
Member Posts: 44
Forgive me if this has been asked before or if the info is out there somewhere, but I'm having a hard time finding it.
I'm a long time .NET developer and I've been working with NAV for a while now - since implementing 2013 at several clients, I'm wondering what Microsoft's plans are for the development environment and the classic NAV code that most NAV devs are familiar with. Are MS moving the whole lot to .NET and MS tech (the same way they have done with the back end, middle tier and now the end user client)?
We have a graduate at my place of work, and the company are looking to train him and move him into the NAV world of dev/consultancy and I'm wondering whether it would be worth him getting a handle on .NET tech. Obviously having a foundation level of knowledge would help as the new stuff is written on top of WPF/WCF and all that goodness, but does he need to look into learning the .NET framework or are we always going to have classic C/AL?
I'm a long time .NET developer and I've been working with NAV for a while now - since implementing 2013 at several clients, I'm wondering what Microsoft's plans are for the development environment and the classic NAV code that most NAV devs are familiar with. Are MS moving the whole lot to .NET and MS tech (the same way they have done with the back end, middle tier and now the end user client)?
We have a graduate at my place of work, and the company are looking to train him and move him into the NAV world of dev/consultancy and I'm wondering whether it would be worth him getting a handle on .NET tech. Obviously having a foundation level of knowledge would help as the new stuff is written on top of WPF/WCF and all that goodness, but does he need to look into learning the .NET framework or are we always going to have classic C/AL?
Charleh
0
Comments
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
http://www.epimatic.com
We are already using Visual Studio for Development (Reporting). And as you mentioned add-ins.
They can improve CAL by allowing us to use LINQ or anything else that will improve our RAD development.
The way I see it right now, since the debugger is in RTC, we will be using it for dev as well
I totally agree with you! This is the way to go, VS has to come, CC/Dev Env. has to go. But C/AL has to stay. I don't think writing business logic in c# would make sense, you always need the right language for the task, and c# is not the right one. Some sort of switching would be nice, if we could write c# code directly and expose these methods to the C/AL (without writing assemblies that must be deployed etc, i mean directly integrated and exported to the fob (if they stay...).
But most of all we need a proper IDE which VS can provide us. Well we need it anyway for reporting, addins, assemblies.
So killing the classic client would make sense, so we can stop from hopping around between CC, VS and RTC...