.net - VS 2013 remote debugging attaches as v2.0 instead of v4.0 -


in visual studio 2013, i've got .net 4.5 project configured remote debugging. when hit f5, debugger attaches remote debug monitor on remote machine (windows 7 x64) , launches application (also x64). however, no output in debug window , breakpoints aren't hit. if launch application manually , attach remote process, debug output , can hit breakpoints.

looking more carefully, discovered when hit f5 , go attach process dialog, process attached debugging managed code 2.0, 3.0, , 3.5. should attached debugging managed code 4.0 , 4.5, that's why i'm not getting output or hitting break points. when manually run launch process , attach, correctly attaches 4.0/4.5. question is, how vs 2013 attach correctly (for debugging managed 4.0 , 4.5 code) when hitting f5?

also of interest, don't have problem when running application 32-bit on 32-bit windows 7, nor or 32-bit or 64-bit app on 64-bit windows 8.

my development machine in windows 7 x64 visual studio premium 2013 update 1. application outlook add-in. in c# project properties debug tab, "use remote machine" checked name of remote machine. "start action" set "start external program" path outlook set (as exists on remote machine).


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -