exe upgrade to 2009 to use webservices.

generic

Hello.

A client has a lot of mods and a vertical solution 4.0 sp3. They are planning to do an web integration and want to use webservice. The vertical solution is not ready for 2009. And it is going to be expensive to do full upgrade.

Based on my experience there is nothing prevents doing an exe upgrade to 2009 and use the webservice and use classic 2009 client with 4.0 sp3 db.
I wanted to know if anybody has done and and what has been their experience and what kind of issues did they run into?

Thanks.

freddy.dk

Web Services runs on the service tier - meaning that all you AL code needs to be able to compile into C# (which is a large part of the changes we have done). If you want to have page based Web Service access you also need to have forms transformed to pages.

So it probably isn't as easy as you have hoped for.

generic

I understand that service tier runs c#. It's a matter of compiling all the objects. Granted there are some objects that use automations and they need to be registered, but there are just a few and majority of them are not used.
Compiling all the objects isn't an issue, unless you are saying that certain CAL code could not be translated to C# so you had to change CAL code?
Could you give examples if this is the case.

They don't need to transform any forms. Even if they transform them, they don't need to look good, since they won't use the Role Tailored client. They just want to use web service.

freddy.dk

The problem with transformation is not to make it look good, the Role Tailored Client is responsible for the layout of the pages - you just specify content and behavior (code). So when you have pages functional for WebServices - then you are not far from having these pages for RTC as well.
(Difference is of course that you can decide to do only some forms for Web Services).

All AL code should be able to compile to C# - but here are constructs that are not supported or supported differently (Environment variables, Temporary files, OCX'es) and in some cases this can generate C# that doesn't compile or run. You might not run into any of that of course, but if you do, the event log is your freind.

generic

I would have to see actual examples of code that was changed from 5.0 sp1 to 2009 to understand it.

(Environment variables, Temporary files, OCX'es)

I understand that they've created the 3 tier CU to handle file transfers, but I'm just trying to use web service.

ara3n

Hello

I saw this blog on this subject.

http://blogs.msdn.com/nav_developer/arc ... ntime.aspx


It looks you can do exe upgrade using older databases.
There is one mentioned example that needs to be changed.

generic

wow =D> .

That is great news.