Closed KHerron closed 7 years ago
I have started this process. Users will need to understand that not only am I correcting the Case I am also changing the names to correspond correctly with .Net naming convention guidelines also.
For example, the GetRemoteCommandList property of the ActionList will be changed to just RemoteCommandListUrl to represent a more accurate description and to not confuse users with the GetRemoteCommandList() function.
So, this will make the next release 5.3, not compatible with 5.2 applications. User will need to change their code to the new naming.
All Example applications will be updated!
This issue has been resolved. Closing issue.
Please align API with the naming guidelines for .NET. E.g. upper camel-case for method names and no all-caps acronyms.