Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
b3b343777yIf you set a breakpoint the window should be minimized automatically lol.
I can debug fine -
@b3b3 You think? Yeah, but in this case there is child window that obviously doesn't "understand" that it should get out of my sight when hitting a break point. Well, I got around this particular problem by just "debugging inside my head" and fixing whatever needed be fixed to get past the point in the program where the child window lingered.
-
@CristCD It doesn't help. I have two screens, and place the application in the second screen. Yet the stubborn child window places itself in the same screen as VS. Dunno why.
-
CristCD2977y@TerriToniAX If it's a modal window that pops up, they tend to go to the primary screen. You could put visual studio in the secondary
-
Made my secondary screen the primary screen, moved Windows taskbar to my now secondary screen and running VS in the now secondary screen making it look as primary screen, with this "tiny" difference that now I can debug normally without application modal windows getting in the way. Problem solved! :) The only drawback is that windows login and desktop icons appear in the other screen that is now primary, but this I can live with :)
Related Rants
It's freaking impossible to debug when the application window places itself on top of Visual Studio and can't be moved :(
undefined
vs
debugging
wpf