Memory Profiling with WinDBG
Create memory dump file Open WinDBG and go to File/Settings Add path to DLLs/PDBs Load DMP file In command type: .loadby sos clr In command type: !dumpheap -stat
The wonderful world of technology
Create memory dump file Open WinDBG and go to File/Settings Add path to DLLs/PDBs Load DMP file In command type: .loadby sos clr In command type: !dumpheap -stat
Search expression: ([0-9]+)\t([0-9]+)(\s)(.+) Replace with: $1\t$2\t$4 This builds new text by using match groups from expression above. Plain and simple
Lost my DisplayPort monitors. Thought video card died, but this trick fixed my problem: Press Windows key + Ctrl + Shift + B
curl -X POST -H “Content-Type: application/json” –data-binary “{‘delete’:{‘query’:’:’ }}” https://local.terminix.com:8983/solr/XP0_web_index/update?commit=true -k Note double quotes. Most of the CURL samples are for Linux. Windows likes it the way it is written above.
For some strange reason, what helps is clicking on one of the “invalid” references in each project and going to properties. That somehow re-triggers reference resolution.
Obscure, but quite easy fix: https://developercommunity2.visualstudio.com/t/find-does-not-show-results/954875 HKEY_CLASSES_ROOTWow6432NodeCLSID{73B7DC00-F498-4ABD-AB79-D07AFD52F395}InProcServer32 After removing the extra backslash in the path, Visual Studio Enterprise 2019 Version 16.8.3 suddenly started showing search results in the Find window.
Original workflow chart was a bit fuzzy, so I redesigned it from scratch: https://doc.sitecore.com/developers/90/sitecore-experience-manager/en/versioned-layouts.html