I have a WPF Prism application in 6.3 need to upgrade it to Prism 8.1, there are lots of changes on levels of bootstrapper class, Prism Logger being depreciated in 8.1, I'm using PrismApplication class from Prism.WPF in place of bootstrapper, Am I going in right direction?
How do I implement EnterpriseLibrary.Logging.NetCore for logging in Prism 8.1, I don't want to use any 3rd party loggers like serilog, log4net or logn as there is a dependency wrt other application?
Can anyone suggest any sample code or link for Migration of Prism from 6.3 to Prism 7.0 or above.
Thanks!
I tried implementing PrismApplication class instead of Bootstrapper as it is depreciated.
Wrt to logging in prism I tried Registering Serilog in Prism Container but I want to use EnterpriseLibrary.Logging.NetCore due to some dependency.
Related
I'd like to use Prism in a WinUI 3 app, and I saw the Prism v8.1 release.
Additionally Prism 8.1 offers a new Prism.Uno.WInUI platform target for those wishing to build either native WinUI3, or Cross Platform WinUI 3 apps with Uno Platform.
I'm confused about Uno. I'm not using Uno, can I still use Prism in a WinUI 3 app without using Uno?
If yes, which packages do I need to install and in which projects? (I'd like to use DryIoc)
I guess Prism.DryIoc.Uno.WinUI must be added to the WinUI 3 app project.
But what about the other packages for using Prism?
There is a question about an error while using Prism.Uno with WinUI 3: How to use Prism MVVM in WinUI 3 Desktop
In the comments section, there is a link to a GitHub discussion that is held in Prism GitHub repository. Here is the link: https://github.com/PrismLibrary/Prism/issues/2632
In this discussion, on Dec 7, 2021, it is stated that there is not any support for WinUI 3 other than Prism.Uno.
If you specifically want to use 'Dryloc', you could try to use one of these Nuget packages:
Prism.Container.Extensions
Prism.DryIoc.Extensions
They should both be of general use and not target a specific UI technology.
If you install 'Prism.DryIoc.Extensions' using the Nuget-Package manager, dependent packages should be installed automatically.
See Github - Prism.Container.Extensions
Note there is also a package 'Prism.Core' that does not target a specific UI framework either. If contains features like an event aggregator.
I am currently upgrading the Prism library of an application, going from version 7.0 to 8.1. We use MEF to extend the application, and the older version of Prism had built-in support for MEF. Going to 8.1 we need do some implementation to adapt Prism to MEF, and that is fine. However, the default region adapters that Prism provides are not being registered with the Prism container extension, unless I do that by myself. Later during the bootstrapping Prism tries to resolve them, but that fails, since they are not registered. How come they are not registered at any time, or have I missed something else?
Hi I want to use TravelPort API Sample Application(C# Console Application) in my Xamarin Forms Project but I am not able to use namespaces like System.Configuration and System.Service Model in my PCL project.
Later I came to know that I should use DI(Dependency Injection) in my PCL project to use these namespaces. Then I started learning DI.
My question is that I am targeting Android Platform only in my Xamarin Forms project.And I just want to use Flight Search and Flight Booking features from TravelPort Sample App.
So is it convenient to use Shared Application Project rather than a Portable Class Library Project? And Will I be able to use System.Configuration and System.ServiceModel namespaces easily in SAP ?
Recently Xamarin announced support for NetStandard (see https://releases.xamarin.com/stable-release-cycle-7-service-release-1/) and the recently shipped Entity Framework Core supports NetStandard. There was a recent issue with the SQLite.Native package that has been resolved (see https://github.com/aspnet/EntityFramework/issues/4269) but when I build the Android version of a Xamarin Forms application it appears it does not include all the assemblies in the output that are needed by the Entity Framework and therefore the application will not run and crashes on the first line of EF code to retrieve data. The UWP version appears to work just fine so this seems like an issue with Android (possibly iOS too).
Has anyone run into this and know a way around it so that the compiled Xamarin Forms Android application will run using Entity Framework Core to access a SQLite database?
Thank you in advance.
Here are the steps you can follow.
Create a Xamarin.Forms project.
Convert the PCL project's properties to .NET Standard 1.3
Install Entity Framework Core and other EF Core stuffs
I have prepared a small hello world project at Github Here.
need to use -linkskip to inform compiler not to remove references.
I am creating a simple application with Xamarin for Mac.
I need to provide a decouple architectural elements into solution, but haven't found any information on dependency injection in Xamarin for Mac.
Xamarin.Forms seems to have an IoC NuGet packages, but it is not possible to add Xamarin.Forms into a Xamarin.Mac project, since the current version of Xamarin.Forms (1.2.2) isn't compatible with .Net 4 targeting projects (Xamarin for Mac by default targets .net 4)
Please point me to some information on IoC in Xamarin for Mac.
There's a pretty good article by Rob Gibbens, a Xamarin University instructor, on using IoC containers in Xamarin projects.
IoC Containers with Xamarin
The examples are using Xamarin.iOS for illustrative purposes but I have to imagine that it could work with any of the Xamarin platform projects.
Personally I am a fan of Autofac in general and have played around with it in Xamarin before and it seems to work fine.