I have prepared a small console app that demonstrates the difference in behavior of the patched and unpatched assembly.
Please open the attached zip, extract it and open the solution in Visual Studio.
Then Restore NuGet packages and build the solution.
If you run it immediately you should see the problem with getting the value of an Auto-increment Id in the console together with a message that you are using an un-patched version.
Now copy the Telerik.OpenAccess.Runtime.dll.hotfix
file that sits next to the solution file to the bin/Debug
folder and rename if to remove the .hotfix
suffix. Run the console app through command prompt
again (if you hit F5 the patched assembly will be overwritten by Visual Studio).
You should see that the patch is applied and you are able to insert and get the Auto-increment Id value back.
So far this proves that the patch works with your specific version (just as it does in our test environment).
Next you have to make sure that the patched assembly has replaced all occurrences of the original one all over your product. This is a step where I can only give you hints where to look:
- Program Files (x86)
- GAC (x86, x64, MSIL)
- /packages folder under your solution if you are using NuGet packages
- /bin/Debug and /bin/Release or any other build output directory in your projects
- folders that collect all deployment artifacts
Given that most work is done in team a test similar to the one in the console application can greatly reduce the likelihood of regression issues caused by a teammate with unpatched version.
Telerik by Progress
Telerik Data Access is no longer being developed. For more information please refer to this page