I'll be watching this space to see what other useful information shows up (for real, like, man.).
In any case, its unclear if Wizard's orgiginal issue arose in release
mode or in debugging
mode. Inquiring minds need
to know, you know? Given that its been established that Wizard's code snippet - as Wizard provided - can not
be stand-alone, ChrisF
's post (why-does-f10-step-over-in-visual-studio-not-work
) seems particularly salient:
"Without knowing more about your application it's difficult to say, but usually this sort of thing happens when the process starts a thread or otherwise goes into code where there isn't any debug information."
Its worth noting - can-i-debug-a-compiled-assembly
- there are potentially three issues at play:
Wizard needs to disable default IDE debugging settings - Tools -> Options -> Debugging -> general section -> "Enable Just My Code" - and then load the PDB (symbol set) for the compiled assembly he's debugging.
OR attach to the assembly process already running using Debug -> "Attach to Process" in the VS IDE. As long as a copy of the running source code (along with the associated .pdb in Visual Studio, you can debug normally.
Wizard made reference to using IDE hotkey - F10 - step over
. Per R. Bemrose
comment at the first link cited:
"F10 is Step Over.
This means that any methods called by your current method will not be shown in the debugger. If these throw an uncaught exception or somehow end execution, debugging will just end..."
ALL of that notwithstanding, nevertheless, and what not, I originally indicated that I block LocalSecurityAuthority.Shutdown
in the 'Protected COM Interfaces' access right for %VS_install_dir%\Common\IDE\devenv.exe
= path to VS install folder)FWIW:
Given that I've seen apps ask for DNS access rights - the log shows RPC to be intimated as the target - and the app makes no
attempt whatsoever to access the internet (based on lack of any firewall alert), makes me lean towards the idea that shutdown
be unilaterally be blocked; doing so will probably break
some arcane VS IDE functionality that will be virtually impossible to debug if shutdown
privilege is blocked; I believe that this is CIS' mechanism to address 'God' access-rights / privileges; leave it alone and grant such privilege on case-by-case
OBTW: the proper format to the Ancient Egyptian Get-CIS-to-work-with-Arcane-Visual-Studio-Functionality Dance
Just, you know, throwin' that out there (got burned by that once). Its all too easy for the inexperienced to be going off on very similiar (although vastly different affect) rituals, e.g., Ancient Egyptian Laser-Printer-repair
OR Ancient Phoenecian Snowfall-to-Grimace-Proportions