I am updating .nupkg plugin package, using plugin registration tool. But after updating it the latest code is not get reflected properly. Sometimes even the older version is coming back automatically. Only one developer is working on it so there no chance of overwrite by other developer. Creating the package by rebuilding the solution or clean and then Build.
I found out older code is coming back or new code not updated properly by using traces.
Not sure what is wrong, can anyone please help? If there any best practice to follow while working with .nupkg plugin package, please let me know.
After Microsoft Dataverse instantiates the plug-in class, the platform caches that plug-in instance for performance reasons. Dataverse manages the length of time that a plug-in instance is held in cache. Certain operations, such as changing a plug-in's registration properties, trigger a notification to the platform to refresh the cache. In these scenarios, the plug-in is reinitialized.
Because the platform caches plug-in class instances, the constructor isn't called for every invocation of plug-in execution. For this reason, IPlugin implementations shouldn't depend on the timing of operations in the constructor apart from obtaining static configuration data.
Thanks for your response.
I did it and it worked. But I can't unregister and register the whole package multiple times. I need to re-register all the steps and images as well.
In development phase I am changing the code and deploying it multiple times.
Not a practical solution.
Hi @Ayan28
Try Unregistering Assembly and install it again create a step and try using it.
Please mark as Answer if it is helpful and provide Kudos
Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Follow me on Twitter : @rampprakashd
Blog : https://microsoftcrmtechie.blogspot.com
stampcoin
17
mmbr1606
15
Super User 2025 Season 1
ankit_singhal
11
Super User 2025 Season 1