I had suggested in another thread, but they could just release the service tier for web service.
A lot of solution can be built around web service. It's multi threaded and solution centers that have web stores will move all their code overnight to a webservice, instead of NAS solution.
Ahmed Rashed Amini
Independent Consultant/Developer
I would like to see this happen as well, but there is no statement whatsoever about plans like this.
Next week, at Convergence, this is definitally going to be part of the discussions.
I had suggested in another thread, but they could just release the service tier for web service.
A lot of solution can be built around web service. It's multi threaded and solution centers that have web stores will move all their code overnight to a webservice, instead of NAS solution.
This is also my opinion. Why not release 5.1 as planned but without the new client. I think we all would love the new service-tier and still keep the two-tier client for a while.
It's the new client that i'm worried about. It's a huge change. All that is exposed to the user is changed. New reporting based on Reporting Services (in version 1.x, Crystal Reports is on 9.x now), no matrix forms, etc etc. It's a really big challenge for MS, ISV's and partners (and not to forget the users..).
I think it's a wise decision to postpone the new client and call it 6.0. But I would really like to see a 5.1 that is just the web service tier and the MOSS Display Target.
I had suggested in another thread, but they could just release the service tier for web service.
A lot of solution can be built around web service. It's multi threaded and solution centers that have web stores will move all their code overnight to a webservice, instead of NAS solution.
Rashed,
Today, at Convergence, it was stated quite clear: they will NOT release webservices before 6.0 . Simply by the fact that the webservices need the service tier for this.
When you call a language ".NET", it means (for me) that it should use the .NET framework in full. That's the same for C#, VB and would be for C/AL as well.
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
A lot of solution can be built around web service. It's multi threaded and solution centers that have web stores will move all their code overnight to a webservice, instead of NAS solution.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Next week, at Convergence, this is definitally going to be part of the discussions.
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
This is also my opinion. Why not release 5.1 as planned but without the new client. I think we all would love the new service-tier and still keep the two-tier client for a while.
It's the new client that i'm worried about. It's a huge change. All that is exposed to the user is changed. New reporting based on Reporting Services (in version 1.x, Crystal Reports is on 9.x now), no matrix forms, etc etc. It's a really big challenge for MS, ISV's and partners (and not to forget the users..).
I think it's a wise decision to postpone the new client and call it 6.0. But I would really like to see a 5.1 that is just the web service tier and the MOSS Display Target.
http://www.linkedin.com/in/larswestman
This posting is provided "AS IS" with no warranties, and confers no rights.
Rashed,
Today, at Convergence, it was stated quite clear: they will NOT release webservices before 6.0 . Simply by the fact that the webservices need the service tier for this.
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
Or it could be compiling of the objects?
One thing that is good news is commenting of localization.
I've done many merging of different countries and this will help alot.
I saw this interview about languages in general and it was very interesting.
It explains why current .NET languages are not ready as an ERP language and we might see a new language down the line. Or maybe CAL.NET
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
When you call a language ".NET", it means (for me) that it should use the .NET framework in full. That's the same for C#, VB and would be for C/AL as well.
Doesn't seem feasable to me, actually...
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog