I have .Net DLL it's containing Crystal report functionality it's working fine in my all .net project with some modifications. Now, I want to use the same DLL in my .Net Core Project for reporting purpose
I am not sure but it should work. You can add reference .Net framework DLL into .Net Core project. So try doing some POC on generating reports.
Try to generate static report which will does not have any database connectivity or dynamic datasource.
Try to generate simple report with database connectivity with ODBC. I am sure ODBC should work on .Net Core as well.
~Nilesh
Related
We have Crystal Reports on a old Web API, we are moving to .Net Core 6 wherever we can, i understand that Crystal Reports is not compatible with .Net Core and no immediate possibility of Crystal Reports being updated to do so.
I understand this, however in my research I found some users were able to create a ReverseProxy in a Seperate project that holds the Crystal Reports on a .Net 4.8 framework and the WebAPI being on .Net core 6. I however have not found any examples of doing so and how to accomplish this, and I personally have never created a proxy so not sure how to go about this and getting this to work for us(maybe). Does anyone have any examples of setting up a reverse proxy for crystal reports? or something that could help point me in the right direction to creating my own?
Please refer to the below blog, it will inspire you.
Crystal Report to PDF Viewing with Angular and Asp.Net WebAPI
If you want use reverse proxy, please setup IIS with URL Rewrite as a reverse proxy for real world apps.
I am trying to migrate my existing WCF service to .Net5.0 Web API. Currently we have Excel Interop dependency to implement excel cells update, running macro inside excel & then capturing the screenshot of specific cell range.
When I am trying to add Microsoft Interop with .Net5.0 using nuget package, seeing warning like it is not compatible other than .Net Frameworks.
Can anyone help me is it possible to add nuget package to .Net5.0 Web API project?
As #Alexey Rumyantsev says, the Microsoft Interop wouldn't be possible to port to .Net core because it relies on the Office interops. The Office interops is windows ony feature. More details ,you could refer to this github issue.
If you still want to use Microsoft Interop Excel in asp.net core, I suggest you could try to create a new .NET Framework 4.X project. Add the relevant COM references to the project. Edit the .csproj of your .NET Core 5.0 project and add the generated references from the .NET Framework project to the tag.
Notice: We don't suggest you use this way, we suggest you use other EXCEL library.
More details, you could refer to this answer.
I'm converting a .NET Framework 4.6.1 Library to .NET Core 2.1.2. The old data access library contains a DataSet. I've created a new Visual Studio project from the Class Library (.NET Core) template and added a DataSet. The Project does not group the DataSet.xsc and DataSet.xss files under the DataSet.xsd. Also, the Custom Tool MSDataSetGenerator does not generate the DataSet.Designer.cs file.
I found the problem posted on the Developer Community Site, see DataSet designer error in .net standard 2.0 library.
Does anyone know of a work around?
I've created a MTDLL COM object in Foxpro and want to use it in ASP.NET Core, so far I've been unable to find a solution and packaging it with Nuget didn't work either whereas I can use this same dll easily in standard ASP.NET. Is there any way to use a Foxpro DLL COM object in ASP.NET Core? or Is there any difference between ASP.NET Core and ASP.NET in using COM objects?
Thanks
I am currently trying to develop a small web application for a business. I started development using .NET Core 1.1 version. And when I tried to study how to add Crystal Reports into the project, it is said that they are not supporting it yet.
Is it possible to add Crystal Reports if I change my target framework to 4.6 in the .NET Core app? Or do I have to start a new web application targeting .NET Framework project 4.6.2 from scratch again?
This should absolutely work. When targeting the full framework like 4.6 with Asp.Net Core you have access to any dlls that are based on 4.6 that you create project references to.
If the makers of Crystal Reports said they are not supporting it yet, perhaps they mean they are not supporting it via direct reference from a project json file but even that seems suspect. But now with VS 2017 the project json is no longer used and .Net Core projects use a regular cs proj file fairly similar to what non .Net Core projects have always uses. So again, use VS2017 you should absolutely be able to reference Crystal Reports Dlls directly and you should be able to reference a full framework class library that references a Crystal Reports DLL.
Another possibility is that maybe their designer support tooling needs updated in some way for .Net Core Projects. But even if that's the case, running an existing report should work.