Question/Request: Multiple Projects in Dotnet SLN

[kjarmie]

Super awesome projects, really excited to use this. I started a project and went about my normal splitting of solution into projects. When I tried to access the controllers, I got the 'no controllers found' error. Do you have a way to get around this?

[kjarmie]

I also tried using ILRepack to combine all the projects, but this causes the backend to hang when loading the dll

Above is the console output when calling a controller defined in the helloworld plugin. No more output after that and further commands are not processed

[RubenPX]

This happens because DotNetBridge is searching for dll files and ILRepack will join all dlls in one.

I recomend to not use ILRepck as temporal solution

TauriDotNetBridge/src/TauriDotNetBridge/Composer.cs

Lines 20 to 53 in b08c8e6

	public void LoadPlugIns()
	{
	var serviceProvider = Services.BuildServiceProvider();
	var logger = serviceProvider.GetRequiredService<ILogger>();
	var assemblies = Directory.GetFiles(DotNetHome, "*.TauriPlugIn.dll");
	// we need the AssemblyResolve event handler registered forever because
	// dependencies are loaded by CLR on-demand and we need to resolve them
	AppDomain.CurrentDomain.AssemblyResolve += OnAssemblyResolve;
	foreach (var path in assemblies)
	{
	Load(logger, path);
	}
	Assembly? OnAssemblyResolve(object? _, ResolveEventArgs args)
	{
	if (args.Name.StartsWith("System")) return null;
	logger.Debug($" Resolving assembly: '{args.Name}'");
	var asm = AppDomain.CurrentDomain.GetAssemblies().FirstOrDefault(asm => asm.FullName == args.Name);
	if (asm != null)
	{
	return asm;
	}
	var name = new AssemblyName(args.Name).Name + ".dll";
	var dependencyPath = Path.Combine(DotNetHome, name);
	logger.Debug($" Loading: '{dependencyPath}'");
	return Assembly.LoadFile(dependencyPath);
	}
	}

[kjarmie]

Okay, so the solution is to make all assemblies end in '.TauriPlugIn'?

[RubenPX]

Yes, only if your assembly is a plugin

[kjarmie]

My structure mostly follows the Clean Arch:
Solution
|--Domain
|--Application
|--Infrastructure
|--Host

All controllers and services are registered in Host, but all business logic is in the Application, and DI is in Infrastructure. Will each of these DLL's need the '.TauriPlugIn' or just the Host (which references the other projects)?

Sorry for all the questions, but I appreciate the help

[RubenPX]

Try to ILRepack your 4 layers and the result change dll name to end with tauriplugin.dll.

I think dependency injection are diferent from tauri project

[plainionist]

@kjarmie did you try with just renaming the host project to "TauriPlugIn"? this should be found by the composer and loaded and then "regular CLR" mechanisms should take care to load the other DLLs. would be interested in the outcome of your experiment!