I'm building a new Fluent service and trying to use semantic versioning, but get errors at the type-check.
If I set the version = 1.0.0, (as a number) there is a JSON fault that the JSON standard does not allow such tokens.
If I set the verision = "1.0.0" (as a string) the type-check says there is an error in the build file due to NumberFormatException.
I can leave the version at 1, and deploy to TM, then change the version in TM, but that seems clumsy when the IDE does all the build and deploy tasks.
Is there a workaround for this?
which version of TM and the SDK are you using.
thanks for the prompt.
We are on TM 17.10, and I just checked the SDK and found that I'm still using 5.1.7. When we updated TM it seems we overlooked the SDK update.
I'll get my SDK up to the latest version and see if that helps.
I've just downloaded the Transact-SDK-17.10.0.
However, I notice this is different from the previous structure which had a fluent-api and a project-template.
I'm trying to follow the instructions to upgrade a project, but there are some inconsistencies because of the single sdk vs the sdk plus project.
Are there some specific instructions for scaffolding the latest sdk?
The Transact SDK is quite different from the previous Fluent SDK. I would recommend setting up a new Workspace in your IDE, scaffolding a new service or application package and then migrating your existing service code into it.
Are you building an individual service or an application package with forms and services?
I have just set up a new project using the Transact SDK; it is quite different, so I understand why you made that suggestion.
I created a service as a test to get to know the new features and noticed that the service-def.json file does not include "version" as a default parameter. Is that an oversight, or do I need to explicitly add it each time I create a new service?
Is there a migration tool or pattern/instructions for migrating a service from Fluent SDK to Transact SDK?
In a Fluent project a service would be 'prefill service' and not have a package. In Transact the service has a package and usees Logger (as an example of a difference). So, I'm wondering what's the easiest or best practice approach to get our services into the new project structure. I'm not keen on creating them all from scratch so I expect there is a straight forward way to handle the migration.
I found the svc-clone task in Ant build.xml and tested that out.
It draws in the full script from TM, which has the 'included' files as well as the base script, but I think I can work around that. That fits with the package structure and the use of 'common' files.
I still need to sort out the best practice for package use/strucutre, but making some progress.
thanks for the information.
I'll set up a new Workspace and go from there. All my IDE work is focused on services.