If it's a property editor you are facing the challenge of 2 different technologies.
In v6 property editors were built using .NET user controls.
In v7 this is done using angular and rest api.
Personally I wouldn't focus on v6 anymore. The last release (6.2.6) was from march this year because of a bugfix for a gold parnter. The release before that (6.2.5) is from february 2015.
I think nobody will be starting new projects on v6
Creating Package Compatible with v7 and v6
Hi All,
Looking for some advice on creating a package for v7 which will also be backwards compatible with v6.
Looking for some general approaches and maybe some gotchas you guys have come across in doing the same.
Any help would be much appreciated.
Cheers, Adam
Hi Adam,
Depends on what your package does.
If it's a property editor you are facing the challenge of 2 different technologies.
In v6 property editors were built using .NET user controls. In v7 this is done using angular and rest api.
Personally I wouldn't focus on v6 anymore. The last release (6.2.6) was from march this year because of a bugfix for a gold parnter. The release before that (6.2.5) is from february 2015.
I think nobody will be starting new projects on v6
Dave
is working on a reply...