Visual Studio Device Debugging

5 posts, 0 answers
  1. CETAS
    CETAS avatar
    3 posts
    Member since:
    Jan 2016

    Posted 04 Nov Link to this post

    Hi,

        I am using Telerik App Builder on the Visual Studio. From the Current Version of AppBuilder for Visual Studio. I am not able to debug the app on the Visual Studio. In this i am able to get the Debug Attach but it is not going to debug and my app is build and deploy on device in Debug mode. 

       On Previous i am able to do such, but not able to Debug my app. Please help ASAP. I have attached the image also

     

  2. Garo
    Admin
    Garo avatar
    46 posts

    Posted 08 Nov Link to this post

    Hello,

    As I am unable to reproduce this faulty behavior on my end, I would ask you to provide me with additional information so I could investigate this issue further:
    • Are you developing a Cordova or a NativeScript app?
    • What version of Visual Studio are you using?
    • What is the OS (Android or iOS) version of your testing device?

    I look forward to your reply.

    Regards,
    Garo
    Telerik by Progress
     

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

     
  3. CETAS
    CETAS avatar
    3 posts
    Member since:
    Jan 2016

    Posted 11 Nov in reply to Garo Link to this post

    Hi,

        Sorry for the Delay on Reply, I am developing a Cordova App using Visual Studio 2015 Professional. I have tested on the Android OS. I have tried many times but still now the issue is not yet solved. Please help me ASAP.

     

  4. CETAS
    CETAS avatar
    3 posts
    Member since:
    Jan 2016

    Posted 11 Nov in reply to CETAS Link to this post

    Hi Admin,

          One More Information, When I Check On Console I am Getting This Error  as below :

    [2016-11-11 15:38:57.884] Log (Exception,High): System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
       at System.IO.PathHelper.GetFullPathName()
       at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
       at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
       at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
       at SharpCompress.Reader.IReaderExtensions.WriteEntryToFile(IReader reader, String destinationFileName, ExtractOptions options)
       at SharpCompress.Reader.IReaderExtensions.WriteEntryToDirectory(IReader reader, String destinationDirectory, ExtractOptions options)
       at Telerik.BlackDragon.Common.Helpers.PackageHelper.ExtractPackage(String packageLocation, String targetLocation, IFileSystemHelper fileSystemHelper)
       at Telerik.BlackDragon.Client.Mobile.DebugOnDevice.DebugOnDevicesBootstrapper.ExtractPackage(String devToolsPath)
       at Telerik.BlackDragon.Client.Mobile.DebugOnDevice.DebugOnDevicesBootstrapper.<BootstrapCoreAsync>d__18.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Telerik.BlackDragon.Client.Mobile.DebugOnDevice.DebugOnDevicesBootstrapper.<BootstrapAsync>d__17.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Telerik.BlackDragon.Client.Mobile.DebugOnDevice.DebugOnDeviceService.<ShowAsync>d__13.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Telerik.BlackDragon.Common.Tasks.TaskHelpers.<ExecuteTryFinallyOperation>d__4.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

     

       Please Check Rectify the Issue.

     

    Regards,

    Lakshman.S

    CETAS Information Technology Pvt. Ltd.

  5. Garo
    Admin
    Garo avatar
    46 posts

    Posted 14 Nov Link to this post

    Hello,

    To fix the PathTooLong exception you should follow the steps from this KB article. Please, let me know if this resolves the original issue as well or I should continue with my investigation.

    Regards,
    Garo
    Telerik by Progress
     

    Visit the Telerik Verified Plugins Marketplace and get the custom Cordova plugin you need, already tweaked to work seamlessly with AppBuilder.

     
Back to Top