This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 3%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
I'm building a C++ app in VS2022. I'm remote debugging a (in-house) dll that is loaded by the app. However, the symbols for the dll do not get loaded, as the symbol file does not match the source code. The issue seems to be the time and date stamp in the PE header; this does not get updated when I rebuild the dll. How can I "force" the time and date stamp to get updated? Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 86%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
What happens if you first delete the DLL that you're presumably copying to the remote machine?
Is that the DLL that's actually rebuilt when you rebuild the solution?
Thanks David for your suggestion. You are correct, it is the DLL that I am copying to the remote machine. I have tried deleting the DLL before copying I have done a rebuild of the DLL and also a Clean before build. Neither of the above work. Oddly, when I first built the DLL this morning, and copied, I could remote debug it. Then after adding a couple of lines of code, the remoted debugging does not work. The modules view in the VS debug window shows the DLL having a time and date stamp of the first build this morning.
Turn's out it was not VS2022 after all. Some obscure FTP issue.