"When a dream comes true" aka NuGetized Business Central

Having all the dependencies for your development project "at arm's length" is no longer just a dream. Moving from C/AL to AL was like the rescue of Robinson Crusoe from an isolated island. Now we live on the mainland with all other developers and we should use all the tools they have beenn using for years. One of them is NuGet packages. How? We will show you!!!

I have a dream about nugetized Business Central

Getting dependencies for your application is sometime complicated, mainly when another partner is involved. Different processes for different partners doesn't help with this too much.
When using CI/CD, you need to be able to automatically download different dependency apps needed by the solution. As ISV partner, you need to deliver your apps to your partners.

There are existing ways how to solve this. We will look at nuget packages, which allow us to deploy the apps with all dependencies as needed. I will show you how you can use Paket manager to manage the dependencies in better way.

Attendees after the session should be able to understand how nuget packages and sources/feeds works, how they could use them in their CI/CD solution to solve dependency download problems and manage the "dependency hell".

Level: 200 (basic development process knowledge needed)

Version - 4 numbers which can help you

There are different ways how to work with version number on your application. I will go through different approaches, their impact, pros and cons. We will look at why to work with lowest and highest versions of your dependencies in your CI/CD pipelines to prevent different issues.

After the session, attendees should be able to choose versioning system for their apps suiting their needs and know the impact to the processes.

Level 200 (basic development process knowledge needed)

Multi-application architecture in Business Central

Everyone is producting their Extensions/Apps and we are mostly driven by our intuition when to create new app or use existing one. It is time to bring some rules into this process.

SaLi Architecture for Business Central

Based on our (my and my colleague Jakub Linhart) experience from different customer's implementation of Business Central, we collected few rules and patterns, which helps us to organize our applications. Besides using SOLID principles in the architecture, these additional rules could be applied to make the structure of applications organized and lays ground for architectonical decisions.

Our target is to give simple rules to architects/consultants/developers when to create new application or extend existing and if creating new dependency is good or bad in given situations.

Attendees should after the session understand to possible way how to manage architecture for multi-app solutions.

Level: 100

"When dream comes true" aka NuGetized Business Central

When developing for Business Central, every time we want to do something, we need to answer first the question "Where are the symbols?" or "Where are the dependencies I need to download and install into my environment?". Using solutions from different partners can add complexity to this problem. Same problem you are solving in your automatized pipelines. And do not forget, that every dependency could exists in many versions. Are you sure you are using the latest one? Or "best" one?
Let us show you the NuGet way how to handle the dependencies, how to share apps with others, how to consume apps from others.

Indirect NuGet packages - solution for Runtime Packages

If we are talking about NuGet and Business Central, we need to think about Runtime Packages. What are the caveats and how we can solve them? I will try to answer this question for you...

Should be planned after the session "I have a dream..."