Can the people at Imazen tell us that although the ImageResizing library does not support .NET core, if we add the System.Drawing part of .NET in our MVC Core application, will it then work for now. We know that they are working on ImageFlow - but till that comes out would this be an option?
P.S. Any idea when ImageFlow will be released?
Thanks
Imageflow bindings for .NET Core have been out for 8 months. I would suggest this as better option.
https://github.com/imazen/imageflow-dotnet
Related
I'm trying to change ASP.NET Core web application with .NET Framework as a target framework to use .NET Core 3.1.X
I try changing the target framework in the project file (.csproj), I encounter dependency issues, dependency conflict....
Is there any straightforward method to solve this issue?
Before you start your migration, you should know there’s several difference between .net framework and .net core, so please follow the official document to do some Pre-Migration steps.
Then you can follow this official document to migrate your application from framework to .net core 3.1.
Since your ideal .net core version is 3.1, still I suggest you can try to use .net 6. Also, you can use this upgrade tool to reach your goal. In fact, using this upgrade assistant is a batter choice than you doing it by yourself. Even if you are insisting using .net core 3.1, you can use this assistant to upgrade your version to 6 first then change it to 3.1.
Note:
Before you start your migration, please make a backup of your original project. That's because some packages in .net framework may be no longer available in .net core. So if there're some errors occur, you can go back to the original one.
I am getting a little confused by all the naming and versioning of .NET. I think I understand the whole .NET Framework / Standard / Core thing, but I am now moving into ASP.NET Core territory (I want to give my console application a web interface with Kestrel).
When using the NuGET package manager, I can see the Microsoft.AspNetCore.Hosting package, needed to run the webserver. But the highest available version is 2.2.7.
Question now, is that 2.2.7 part of ASP.NET Core 5.0, or do I have some configuration incorrect that I do not get the latest version for my application?
And if it is indeed part of ASP.NET Core 5.0, where can I find that reference? This table helped me a lot with understanding the core libraries.
I assume you wanna this document which tells about your package :
https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.hosting?view=aspnetcore-5.0
And I think you can focus on those classes or interfaces you'll use and take a look if those are supporting .net 5 by click and refer to the details page. You'll see Applies to at the bottom of each page such as this one.
If I misunderstood in some place which made my post isn't suitable to display here, pls point it out and I'll delete it.
I have a task to save a ticket in Apple Wallet. for this I found dotnet-passbook
does this for us. Is it compatible with .net core as well?
No. At the bottom of the project Github page the developer clearly states:
.Net Core
I've had several people ask whether this library will
support .Net Core. If I get the time, I'll try and make this a .Net
Standard library, but I'm dependant on Crypto libs etc., so I'll need
to evaluate them to ensure they will work .Net Core also.
I want to create report(e.g. PDF,Excel,Word) in ASP.NET Core 1.0,
but NPOI and OpenXML is not support ASP.NET Core.
There is an issue for .NET Core support for OpenXML (https://github.com/OfficeDev/Open-XML-SDK/issues/65). Some work has to be done before it is ready. Someone who had your demand as well ported it to .NET Core and published his project on GitHub (https://github.com/xrkolovos/Open-XML-SDK-for-NET-Platform-Standard). I have not tried it myself, but it may be worthwile to try.
UPDATE:
Current releases of OpenXML support .NET Core. Therefore the second GitHub project is obsolete now.
For PDF PdfReport.Core could be a solution. I can confirm that it works under netcoreapp1.1. It also should be able to export to Excel, XML and CSV (NOT tested by me).
Please check my answer here:
https://stackoverflow.com/a/42023039/1719087
There is a CI build that works with .Net Core 1.1 at
https://github.com/OfficeDev/Open-XML-SDK
the specific nuget package is at this feed:
https://dotnet.myget.org/F/open-xml-sdk/api/v3/index.json
If your application is fine to run on windows only, then using ASP.NET Core with the full .net framework let you use NPOI and OpenXML. With this approach you can start now with the new Microsoft web framework in the hope that NPOI or OpenXML will support .NET Core in the near future.
I'm trying to convert quite big project from .net 3.5 to .net 4.0 and we have wwf 3.5 in it. Googling this question i realized that i would need to rewrite workflow almost from scratch. so my question is , if i can use .net 3.5 workflow in .net 4.0 project ?
Yes, you can. WF4 doesn't replace WF3. They are in different namespaces. The blog post isn't on topic, but the blogger is and he states this fact.
As Will said, the WF3 stack is still present and supported in .NET 4 so you don't have to migrate your workflows to WF4. That said all future efforts will go towards WF4 so sooner or later you will probably have to bite the bullet. For now you don't have to though.