One thing that I can note with all of that stuff is : vs folder solved the attachment issue and the breakpoint reaching issue.Īttachment freeze totally unity for 1min maybe more cause he stops the VS attachment and unity continued instantly after this. Huge amount of time to reach the first breakpoint but seems ok to attach.ĭelete. Often use them in specific case with a lot of breakpoints but remove them doesn't change linking time. vs and attachment takes less than 10sec and breakpoint something like one second.
VISUAL STUDIO DEBUG NOT WORKING CONNECT TO PROCESS UPDATE
Project 2 (Unity 2018) : VS update without cleaning. vs cleaning) Visual Studio generation issue is gone and breakpoint are ok. Project 3 (Unity 2017) => No particular issue Project 2 (Unity 2018) => Could take something like a minute to attach/or debug but nothing montrous Project 1 (Unity 2018) => Visual Studio generation issue with assemblies whereas it's ok within Unity. vs hidden folder he stops using it due to huge amount of time. Often use VS with breakpoints, works on the same project than me, linking time rarely exceeds 1 min when it goes wrong. vs folder solved the 1st breakpoint reaching issue. vs hidden folder it tooks something like 3-5 minutes to reach the breakpoint not to attach.ĭelete. Often use them in specific case with a lot of breakpoints but remove them doesn't change linking time.īefore removing. On the older project with Unity 2017.4.X we don't use them. On the projects with 2018.3.0f2 we use the asmdef
We use Unity 2018.3.0f2 except for an older project where we stay in 2017.4.X (X currently 16). We use Visual Studio 2017 but on multiple version indicates in front of each dev right below with parenthesis.
0 kommentar(er)
