![]() ![]() Performed Unit Testing, Regression Testing, Integration Testing, Defect Tracking Systems.Proficient in developing Use Case Model, Analysis Model, Design Model, Behavior Diagrams (sequence diagrams, communication diagrams, state diagrams, activity diagrams), Class Diagrams with UML methodology using Rational Rose, Visio.Passionate and experience in Mobile Development.Worked extensively in front-end web development and Web 2.0 technologies using ASP.NET, MVC, Web Services, JavaScript, jQuery, Ajax, HTML, XSLT, XML, and CSS.In-depth knowledge and hands-on in Patterns and Practices, Software Design and Methodologies, MVC, Agile, Waterfall, Paired Programming.Expert in OOAD, UML, SOA, and N - Tier Architectures.Extensive full life cycle development experience using technologies like Java, J2EE, EJB 3.0, JavaScript, JSP, jQuery, AngularJS, AJAX, Oracle Technology Stack.Over 9 years of application design and development experience using the Industry Standard Technology stack.Interestingly, while debugging on the real Android device, netstat -an shows an established connection: Then run the built AP$$anonymous$$ in Android, and VS Debug->Attach Unity Debugger list shows:Īnnoyingly, at the moment, VS debug breakpoints & stepping are only working for me with a real device, not with the AVD emulated device. On starting your Unity AP$$anonymous$$ in Android (built with Development Build+Enable Scripting), you should see an extra entry in the VS Debug->Attach Unity Debugger list: e.g.Įven with Android running the Unity AP$$anonymous$$, netstat did not detect that port # as listening or otherwise: E:\dev\android-sdk\platform-tools>netstat -an | findstr "56014"Į:\dev\android-sdk\platform-tools>adb connect 192.168.0.5 ![]() running an AVD emulated device, (which uses localhost as the ip address)Į:\dev\android-sdk\platform-tools>adb devicesĮ:\dev\android-sdk\platform-tools>adb tcpip 5555Į:\dev\android-sdk\platform-tools>adb connect localhost Ins$$anonymous$$d, you should be able to see your Android device in the debugger if you try an adb tcpip & connect. Proto Local Address Foreign Address StateĪnd in VS: (Debug->Attach Unity Debugger) E:\dev\android-sdk\platform-tools>netstat -an In my case, the only 56xxx port listening was the Unity Editor, on port 56544: e.g. Be careful that you don't just pick any 56xxx port thinking it will be for your connected Android device. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |