Forum› Workbooks & Inspector
We are excited to announce that the Xamarin Forums are moving to the new Microsoft Q&A experience. Q&A is the home for technical questions and answers at across all products at Microsoft now including Xamarin!

We encourage you to head over to Microsoft Q&A for .NET for posting new questions and get involved today.

Integration development and debugging pipeline

AntaoAlmadaAntaoAlmada PTMember ✭✭
in Workbooks & Inspector

I'm developing my first Workbooks integration and I'd like to know what's the easiest pipeline to develop and debug. Publishing every package version to NuGet is prohibitive and a local package source is still cumbersome.
I'm currently having problems and the log only shows that the package was successfully loaded.
Is it possible to use breakpoints while debugging?
Suggestions are welcome...

Tagged:

Posts

  • SandyArmstrongSandyArmstrong USXamarin Team, Insider Xamurai
    edited October 2017

    I believe that as of Workbooks 1.3 you can just #r /path/to/your/integration.dll, and each time you rerun the #r cell it will be reloaded. So you could point directly to your build output.

    I'll ask somebody more familiar with the SDK stuff to take a look tomorrow.

  • SandyArmstrongSandyArmstrong USXamarin Team, Insider Xamurai

    (This was mentioned briefly in https://developer.xamarin.com/releases/interactive/interactive-1.3/#SDK_and_Integrations)

  • brajkovicbrajkovic USXamarin Team, University Xamurai

    Sandy is correct! As of 1.3, you can reference your integration via #r and have it be loaded, though it will not reload every time you run the cell, unfortunately--you'll have to close and reopen your workbook.

    My recommendation for debugging right now would be the following:

    1. Write a workbook that references your integration via an absolute path (the absolute path is useful because it will prevent the .dll being packed into the workbook archive).
    2. Use the logging built into the client to print useful information. Take a look at the agent-side and client-side debugging notes on https://developer.xamarin.com/guides/cross-platform/workbooks/sdk/debugging/ about using our logging APIs and the Javascript-side logging. Note that in released builds, you won't see the Debug and Verbose levels.
    3. Run the workbook when you want to test. Using the absolute path means you won't need to build and publish a NuGet package every time.

    Unfortunately, using breakpoints is not possible at this point. We'll definitely be looking at improving this experience in the future--some sort of debugger integration is definitely on our radar.

  • AntaoAlmadaAntaoAlmada PTMember ✭✭

    Thanks for the tips. These are very helpful.

Sign In or Register to comment.