Develop and debug extensions
You can easily develop and debug your extension for the installed Spotfire client, and also deploy packages to a server to test your new functionality in a web client.
Note: This documentation
does not cover developing C# code for the extension, or the specifics of
working with the Visual Studio debugger. Rather, it is specific to configuring
the debugger to perform debugging tasks on the developed extension and adding
it using
Spotfire
Package Builder. For more information about developing in C#, or about
operating the Visual Studio debugger, see the Visual Studio help.
The development procedures for the installed Spotfire client and Spotfire web clients differ slightly. The code must be signed in both cases, as the packages must be created by Spotfire Package Builder. Spotfire web client extensions require additional steps for debugging.
- Configuring and running the debugger for Spotfire Windows application extensions
To be able to debug an extension with the installed Windows client, the extension must be packaged as a Spotfire Module, that is, placed in a separate folder with a file called module.xml that contains metadata for the module. - Configuring the debugger for Spotfire web client extensions
You can test the extension that you have developed in web clients.
- Configuring and running the debugger for Spotfire Windows application extensions
To be able to debug an extension with the installed Windows client, the extension must be packaged as a Spotfire Module, that is, placed in a separate folder with a file called module.xml that contains metadata for the module. - Configuring the debugger for Spotfire web client extensions
You can test the extension that you have developed in web clients.
Parent topic: Extensions