Closed septag closed 6 years ago
I have found the problem. before cr_plugin_load, I had to load and unload the dll to execute a function. but visual studio didn't seem to unlock the pdb. The lock was gone with the solution mentioned here
sorry to bother you and thanks for the great lib
Thanks for the link, that is interesting and remembers me that I have some more things to write in the troubleshooting section, I'll take the time and add this info there too.
Hi, I was testing out your library and noticed that on visual studio 2015 (update 3) it still locks the original pdb. I have checked cr_pdb_replace function to see if the pdb name is replaced and it does, but after cr_so_load, the original pdb is locked instead of versioned one. does visual studio gets it's pdb path from somewhere else instead of binary ?