Porting Prism WPF Framework Apps to .NET 5
-
Hi All, I was just wondering if anyone here had done much in this space yet? I've just come off the back of attempting to port my Prism/WPF app and had to basically walk away from the port for now. So many issues. I managed to get things compiling but deployment turned into a nightmare. It gets a little grating when all the tutorials and guides always bang on about how simple this is due to them using some noddy application knocked up in 5 mins for a demo. Since it's a WPF app none of the projects reference each other which means a hell of a lot of the migration tooling just cannot figure out what to do with the projects. I couldn't get the original exe project to behave at all so ended up rebuilding it from the ground up as a .NET5 exe. That being said this project started life in VS2008 and I think it's high time I rebuilt ALL the projects from the ground up. There is surely noise in some of them from previous migrations. One of the main deployment issues came from all the baggage some 3rd party libraries bring with them. I couldn't find a solid workaround for directory probing at runtime for instance. There is talk about hacking this with deps json files to kid the runtime into thinking the directories are NuGet repos. Also manually handling Assembly loading using Resolve events but my god that got hairy and feels like an utter hack. Add in the mix some of these libraries are doing lots of P/Invoke and integrating external C++ DLLs and I just couldn't get the deployment structure right. All in all an incredibly frustrating experience. I've hived off the progress into a branch to revisit. I honest think I need to wait a few versions.