1. Getting started
2. Calling methods
3. Working with .NET Objects
4. Fields and Properties
5. Methods Arguments
6. Nested Types
7. Enums
8. Arrays and Collections
9. Embeding UI controls
10. Referencing libraries
11. Off-line activation
12. Events and Delegates
13. Disposing and Garabage Collection
14. .NET Configuration Files (AppConfig, WebConfig)
15. Exceptions, Debugging and Testing
16. Strongly-Typed Wrappers
    17. Advanced Activation and Licensing
    18 Other usage scenarios

      Debugging Javonet Enabled Application

      Using Javonet both the Java and .NET code could be debugged and measured in very easy and convenient way. First you must understand the concept that Javonet loads the .NET process within the java process. Weather your application is hosted as standalone Java application, applet or web application both .NET and Java worlds will be combined either in javaw.exe, jUnit test runner process, Apache, jBoss or other host process.

      Of course the Java part could be debugged with attached IDE debugger like Eclipse. To debug .NET code all you have to do is attach .NET debugger to your Java process. If you Java process lives very shortly you can set a break point just after the call to Javonet activate method and when your Java debugger hits that point then attach your .NET debugger. For example you can use Visual Studio environment by opening your .NET code project and choosing menu “Debug > Attach to process” and selecting the Java process to start debugging.

      Using this approach both debuggers will allow you to go step by step through Java or .NET part of your code. The same solution might be applied for performance or memory measurements using any .NET and Java profiler of your choice.

      This possibility gives you and your team very effective way of tracing the issues in your code and improves the quality of your solution.