And it’s also logging the invoked method name, and the file name containing the method!
My Forms.RecurrenceToolkit NuGet package pack is now extended with logging functionality.
You can use the pre-written Console and SQLite logger without writing much code, or you can implement your own logger in a few lines, and use it instantly simultaneous with other loggers.
Install banditoth.Forms.RecurrenceToolkit.Logging.* packages, and enjoy the painless logging, and focus on the great ideas instead of being a copy paste robot. 🙂
In your App.xaml.cs, initalize the logger like:
// If you have installed the console logger:
// If you have installed SQLite Logger:
The logger is including the calling method’s name, and the .cs file name in the logs. You can access the logger from anywhere by calling these methods:
LoggingProvider.LogCritical("It's a critical message");
LoggingProvider.LogDebug("It's a debug message");
LoggingProvider.LogError("It's an error message");
LoggingProvider.LogException(new Exception(), "It's an exception");
LoggingProvider.LogInformation("It's an information message");
LoggingProvider.LogTrace("It's a trace message");
LoggingProvider.LogWarning("It's a warning message");
By default, the console and the SQLite logger logs exceptions in error level.
You can implement your own logger by deriving from BaseLogger class, like:
public class CustomLogger : BaseLogger
public CustomLogger() : base(new LoggerOptions()
IncludeCallerSourceFullFileName = true, // This will print C:/Users/Path/AssemblyFile.cs
IncludeCallerSourceShortFileName = false, // This will print AssemblyFile.cs
ExceptionLevel = Enumerations.LogLevel.Error, // The LogExceptions calls routed to log to the loglevel set.
IncludeCallerMethodName = true // This can print the calling method's name
public override void LogCritical(string criticalMessage, string callerMethod, string filePath)
// Your own method
// .. File continues
I have started implementing my very first AOP like library, which is now available for testing in NuGet.org as a pre-release version.
This package is a part of my Xamarin.Forms Toolkit, and it is a good time to say thank you for using all of the three packages more than 500 times. When I had published them, I thought the only user will be me. 🙂
In the first release of the package (1.0.0-pre-01), you can decorate your methods with attributes, in order to listen for Entering the method, and Exiting the method.
This can be handy for example, when you need to log your method invocations (Firebase analytics, Basic logging) or when you need to measure the elapsed time of the method run.
public void BoringMethod()
For example, the following code above will result the output below:
yaaay on enter!
2021. 05. 25. 16:56:01
yaaaay on exit
This can be achieved implementing IMethodDecorator class like this:
public class ConsoleYaay : Attribute, IMethodDecorator
public void OnEnter()
Console.WriteLine("yaaay on enter!");
public void OnExit()
Console.WriteLine("yaaaay on exit");
If you haven’t seen part 1, click here, and start build up your CI/CD pipeline now.
Part 2 Contains:
Configuring build with creating signed APK, and making artifacts from it
Setting up branch policy to master
Configure some magic
Let’s go back to Pipelines. Edit your previously created pipeline by clicking the three dot on the pipelines row.
CI is based on cloud machines hosted somewhere over the world. This computers called as agents. They are used to follow your instructions, defined in the yml file. The base Xamarin.Android yml is only to build your code. But we will make some additional steps in order to create a signed APK of every build. Follow up, to complete this setup.
Recommended branching strategy for this is to keep a development branch, and pull request your feature branches to it, and finally pull request the development branch to the master, and keep your master is always at your production version. The figure below shows visually this method. Source: https://dzone.com/articles/feature-branching-using-feature-flags-1
Create a signed APK or bundle from every build
First, set up some variables for this pipeline. You will find a Variables button on the right top of the tab. Click on it.
Let’s add a new variable by clicking the “New variable” button. We will need 4 vars.
Remember, that i told you, you will need to remember the alias, password, and the keystore name? You can forget them, after you have declared the variables for them.
keystore_filename - AnAwesomeAppDelivery.keystore
keystore_alias - AnAwesomeAppDelivery
keystore_password - The password of the keystore.
When you create var for keystore_password, tick the “Keep this value secret” checkbox.
Go to the end of the boilerplate YAML file, and on the right top of the text editor, you can see a task wizard button. Click on that.
Search for “Download secure file” task on the search bar. Click on it, and set the “Secure file” to the value below, and click on “Add”.
This will get the variable value defined above. Press some enters to seperate our next task from the download secure file task, and jump into signing the APK.
Search for “Android signing” in tasks.
And set up the task like on the picture below. Please regret me for messing up the “Key password” value in the screenshot, the $(keystore_password) variable goes in that field too.
If everything set up correctly, it will make our APK in the output directory signed. But how we will access it? We need to drop our result to the pipeline artifacts. You can set the build output to the artifact staging directory, but i recommend to only copy the file, that you will need as a result. So make a copy task after Adding the Sign task, and some enters to the end of the YAML file. Follow the configurations in the picture.
Okay, we have copied the files, but the files wont appear in Azure DevOps, until we drop our packages to the Artifacts section of our build. Search for “Publish build artifacts”, select the task, and configure as the image below.
So how our YAML Looks like now? Like this below? Then go and save it. If not, correct your mistakes.
After saving the YAML, it recommends to Run it, so jump right into the fun, click on the “Run” button.
If everything is correct, it will show only green ticks. When you click on “Pipelines/pipelines” in the left menu of the DevOps page, you will see your state of your build. On the detailed view, you can access the created artifacts in order to download them.
Click on the row, and you can access the details of the build. If you have set up the pipeline correctly, it will show “1 published” label. Click on it, and you can access your signed application binary.
Merge the pipeline config branch to master
Set up main branch policies to run CI automatically
Go to Repos/Branches, and select the main branch, click on the three dot in the end of the row, and select “Branch policies”.
In the Build validation option, you can configure the previously created pipeline to run automatically whenever a new pull request gets accepted.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Google Analytics : Used to distinguish users.
Google Analytics : Used to distinguish users.
30 seconds to 1 year
Google Analytics: Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.