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?
Related
I have created a C# web application project and added one new project "Class Library. In the class library, I am trying to add "ADO.NET Entity Data Model" but I am getting below snap error.
What is reason behind it. I am using visual studio 2019.
On which .Net Version did you create your web application project?
You need to create your project on a .Net version that is compatible to your added lib.
I'm trying to migrate a project from .Net Framework 4.8 to .Net Core 3, said projects contains also a MathParser based on Antlr3.
I used the nuget package Antlr3.Runtime (3.5.1) and it seems to correctly create the files needed under MyProject\obj\x64\Debug\netcoreapp3.1 but then those files seems to be unreachable by the application.
To be more specific the created file MathParser.cs contains a piece of the partial class MathParser, the other part of which is in MathParser.g3.cs, but that is not considered.
In the starting project the files are created in the same way (and are identical) and the only exception is that they are in the subdir MyProject\obj\x64\Debug, without the additional folder "netcoreapp3.1".
I really don't get how the .Net Framework 4.8 can seemlessly load MathParser.cs after compiling (and creating it) but .Net Core can.
Any help? Thanks
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
I have a Visual Studio 2008 project in C# with .NET Framework 3.5 and I would like to use SSH.NET library but I see no binaries there for last stable release 2016.0.0.
Also in home page says it has been moved to here. Once I go to this page, I see three branches, develop, master and sftpfilestream, so which one I have to take which is compatible with .NET Framework 3.5 (My project uses .NET Framework 3.5 on Visual Studio 2008)?
Also If I downloaded any of them, once unzipped I do not see any DLL, only projects. Well, in fact, I prefer to reference a project within mine in order to use it, but by curiosity, where are the binaries (DLLs)? and which project is the correct I have to add to mine for .NET Framework 3.5?
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.