NVAPI Reference Documentation
Release 384: June 27
All legacy APIs will be deprecated if a replacement is available. When an API is deprecated, it still remains in the code. However, any attempts to use it will result in a warning message recommending alternative APIs and stating that the API will be removed in the future - the API will not remain in the code indefinitely.
As the API is not removed immediately, this gives the client time to bring their code into compliance with the new APIs.
Example of Some Warnings
How to Avoid Warnings
There are two courses of action that clients should take to avoid being presented with the warnings. These include a short term phase and a long term phase:
Phase-I (short term):
Phase-II (long term): Clients need to avoid using the deprecated APIs and switch to the replacement APIs.