AppDynamics.Agent.Forms 2022.1.0-beta1

• .NETStandard 2.0

  • AppDynamics.Agent (>= 2022.1.0-beta1)
  • Xamarin.Forms (>= 4.1.0.555618)

• MonoAndroid 8.1

  • AppDynamics.Agent (>= 2022.1.0-beta1)
  • Xamarin.Android.Support.Compat (>= 28.0.0.1)
  • Xamarin.Forms (>= 4.1.0.555618)

• Xamarin.iOS 1.0

  • AppDynamics.Agent (>= 2022.1.0-beta1)
  • Xamarin.Forms (>= 4.1.0.555618)

Version: 2022.1.0-beta1

Native Agents: com.appdynamics.eum.android:mobile-android:21.6.0.2076, com.appdynamics.eum:mobile-ios:2021.8.1.2573

Changes:

Version 2022.1.0 brings Automatic Network Instrumentation for Xamarin applications. This is handled via a separate library, called AppDynamics.Agent.AutoInstrument.Fody, so to use it, make sure the new library is included alongside the existing AppDynamics.Agent / AppDynamics.Agent.Forms library. In order for it to properly work, do not forget to update the AppDynamics.Agent version to the latest version as well, 2022.1.0.

Automatic Instrumentation will work for these two scenarios:
- Requests sent using the HttpClient. We will automatically inject the instrumentation code for you, targeting the HttpClient constructor.
- Requests sent using the Refit library. We will automatically inject the instrumentation code for you when you are sending requests using the Refit RestService.

> How to use

1. Make sure you already have the AppDynamics.Agent / AppDynamics.Agent.Forms package set up and initialised.
2. Add the new AppDynamics.Agent.AutoInstrument.Fody package.
3. Build the solution.

Normally, after you build the solution, two files will be generated automatically:
1. FodyWeavers.xml
2. FodyWeavers.xsd

These files should be checked into source control!  

Note1: If the above files are not generated automatically, a new file called FodyWeavers.xml should be created manually having the content as below:
- - -
<Weavers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FodyWeavers.xsd">
 <AppDynamics.Agent.AutoInstrument />
</Weavers>
- - -

Note2: If the project is already using Fody, these files will already be there and only the FodyWeavers.xml file has to be updated to include the AppDynamics.Agent.AutoInstrument weaver.  Example:
- - -
<Weavers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FodyWeavers.xsd">
 ... Existing weavers ...
 <AppDynamics.Agent.AutoInstrument />
</Weavers>
- - -


> Customize automatic instrumentation

There are two ways of enabling or disabling Automatic Http instrumentation:

1. Global Switch

You can enable or disable HttpInstrumentation using the FodyWeavers.xml file, via the NetworkInstrumentationEnabled flag. Example:
- - -
<Weavers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FodyWeavers.xsd">
 ... Existing weavers ...
 <AppDynamics.Agent.AutoInstrument NetworkInstrumentationEnabled="true"/>
</Weavers

2. Per class switch

You can enable or disable network instrumentation per class using two different attributes: EnableNetworkInstrumentation or DisableNetworkInstrumentation.

- - -
[EnableNetworkInstrumentation]
public class MyClass
{
   ...
}
- - -

- - -
[DisableNetworkInstrumentation]
public class MyClass
{
   ...
}
- - -

This means that you can either:
1. Enable the automatic instrumentation at a project level from the FodyWeavers.xml file, but exclude some files using the DisableNetworkInstrumentation attribute.
2. Disable the automatic instrumentation at a project level from the FodyWeavers.xml file, but include some files using the EnableNetworkInstrumentation attribute.