when I searched in google, it is saying that it's possible, but when I searched it in chatgpt, it is saying it's not possible.
I'm little confused now, if it is possible can you guide me the right version of this package Microsoft.ML?
I don't have much experience with Microsoft.ML, but by simply looking at NuGet, it shows that it supports .NET Framework, .NET Standard and .NET as seen here:
https://www.nuget.org/packages/Microsoft.ML/#supportedframeworks-body-tab
Microsoft is targeting .NET Standard 2.0 which is a formal specification of the .NET APIs implemented by nearly all versions of .NET. You can find more details here:
https://learn.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0
Related
I try to run my Avalonia app on .net framework. However, when I downgrade targetframework to netstandard2.0, AppBuilder becomes unavailable and I just couldn't figure out, how to fix that problem.
I couldn't find any template, that targets .net framework or netstandard. Documentation contains nothing regarding this issue. The only thing I could find is this Github issue. As I understood, AppBuilder is not supposed to be used in netstandard. Then, what is proper replacement for following code?
public static AppBuilder BuildAvaloniaApp()
=> AppBuilder.Configure<App>()
.UsePlatformDetect()
.LogToTrace()
.UseReactiveUI();
Edit:
As it was pointed out, netstandard can't be used as a target for Avalonia apps, but we can specify multiple targets. So I replaced
<TargetFramework>net7.0</TargetFramework>
with
<TargetFrameworks>net7.0;net48</TargetFrameworks>
And it worked on .NET core and .NET Framework
netstandard2.0 isn't an actual .NET framework version: it's a specification of the common API beteen .NET framework 4.6.1 and .NET core 2.0 (among others). As such netstandard2.0 only makes sense as the target framework for libraries, not applications.
If you want your app to target .NET framework then you need to use a .NET framework version as the target framework, for example net48 for .NET Framework 4.8.
With .Net Core 2.0 not supporting Report Viewer, is there any other alternative way of doing this?
I found alanjuden's solution (https://alanjuden.com/2016/11/10/mvc-net-core-report-viewer/), but actually looking for official references.
We have migrated our project from .Net Framework 4.5.2 to .Net Core 2.0. However, stuck up with these reporting files as core 2.0 doesn't support.
Any suggestions?
Thanks in advance.
Look at this answer, it might help you.
RDLC Local report viewer for ASP.NET Core and Angular(>2.0)
It looks like Microsoft is working on it (or better spending on it, but no official packages seems to be available just yet).
Other references can be found here:
https://github.com/aspnet/AspNetCore/issues/1528
Where they mention PDF libraries and export functionalities
Another library that might help you: https://www.nuget.org/packages/AspNetCore.Reporting
Commercial solution: https://help.syncfusion.com/aspnet-core/reportviewer/getting-started
Other possible duplicates:
Rendering .rdlc reports with ASP .NET Core
Microsoft LocalReport (rdl) in ASP.NET Core MVC App
I found this package useful. I have successfully created a pdf using the RDLC using this library. I'm hoping to write a blog post on that soon. https://www.nuget.org/packages/AspNetCore.Reporting
However there's a major issue in this library where when you have multiple files it doesn't work properly. It uses some internal caching so whatever the first requested rdlc file only will work.
Update:
I have written an article on how you can integrate this library to generate a pdf. Please check this link.
http://blog.geveo.com/IntegratingRDLCReportsToNetCoreProjects
I want to use Mvvmcross to make application for several platforms.
I use Profile 104 for PCL library like Mvvmcross, but this profile target .NET 4.5.
I want to target .NET 4.0 to use my application on Windows XP.
To do that, I add the xml files
MonoAndroid, Version = v1.6 +. Xml
and
VSMonoTouch, Version = v1.0 +. Xml
in the profile 143 which allows me to target. NET framework 4.0.3.
However, I have a compilation error because it can not find the ICommand interface.
This interface is not in the same library between version 4.0 and 4.5, is it why it doesn't work ?
Or should I recompile all Mvvmcross libraries with profile 143?
thanks,
This is a Portable Class Library limitation.
See the table on: http://msdn.microsoft.com/en-us/library/gg597391.aspx
Model-View-View Model (MVVM)
Only 4.5
This means that if anyone wants to use MvvmCross on earlier .Net platforms then someone has to build and maintain a non-PCL version.
Since the maintainer of Mvx (me!) has decided to only maintain PCL versions of MvvmCross, then any non-PCL support will have to be created by the community.
For WPF this shouldn't be too large or difficult a job - but it might be...
Alternatively, somebody might be able to do something funky to get the ICommand working... I've retagged this question with portable-class-library to try to lure in some of the MS experts.
I probably suck as Googling stuff, but I couldn't find any link that mentioned whether its possible to integrate Spring.net with Oracle's coherance product.
Does anyone know if Spring.net has wrapper libraries for the same ?
Thanks in advance.
The spring integration project for .net is still listed as a spring.net extension project, it's status is "incubator" and it hasn't had any commits since March 2010.
From the project homepage:
The Spring Integration for .NET project will use the design and code
base of the Spring Integration project as a basis, adapting the code
as need to support .NET idioms and move in the direction to take
advantage of .NET only features such as Lambda expressions and
extension methods.
I'd suggest you first find out if Spring Integration for Java supports Oracle's Coherance and if so, you might have a slight chance to get this working in .NET too.
Oracle Coherence provides a native .NET client that you can use to access it from any .NET application, including Spring.NET-based apps.
Here is a link to docs:
http://docs.oracle.com/cd/E24290_01/index.htm
What you are interested in is covered in the Client Guide (Parts I and IV) and .NET API Reference.
My book, Oracle Coherence 3.5, also has two chapters on .NET and POF (Portable Object Format), as well as a full blown WPF sample application talking to a Coherence Java backend.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
When is using mono a good choice over using .net for developing a production system?
The upfront cost of the tooling is zero, but how does the total cost of development using mono compare to using .net?
What is the sweetspot for adopting mono.?
Mono is .NET running on non-Microsoft platforms.
Use Mono if you're looking to build a .NET application on a non-Microsoft platform. Currently, I'm working on an ASP.NET MVC application running on OS X via Mono (want to target a Linux based server and all my development is being done in OS X). Good stuff.
If you're targeting Windows ONLY, then the free Microsoft tools (Express Editions) are usually the better option.
...where's Miguel when you need him.
Mono can do a few things the MS's .Net can't or won't:
Run on linux, mac, and others (including iPhone now)
Static link the framework dlls, for a zero-dependency deployment scenario.
On the other hand, .Net does some things that mono does not do or does yet not do easily:
Latest version of the framework
Out of the box visual studio support
WPF, WCF, WF, etc
There are a few things in mono that work, but the performance isn't quite at the same level as .Net
Mono let's you run .NET applications on Linux and Mac OS X, while Microsoft main implementation is tied to Windows.
So in the case of:
"What is better for writing cross platform applications?"
The answer is Mono, and I don't think that's even a subjective answer.
Mono supports a surprising breath of .NET all the way up to 3.5. Virtually all the BCL is in, and you can do ASP.NET MVC, Linq, and WinForms. The trunk version of Mono supports .NET 4.0 features as well, so they aren't really far behind. :)
Notable stuff that is behind is the various W* technologies. WPF is basically nonexistent. WF, is pre-alpha quality. WCF is beta quality and still incomplete, but probably the most developed of the W* technologies.
The upfront cost of tooling for a .NET app is zero as well. Checkout SharpDevelop.
The sweetspot for Mono is developing apps for Linux using C# and a familiar .NET-esque Framework.
It's interesting if you need to develop software that runs in a lot of plataforms (Linux, Mac, Windows) using .net ecosystem.
According to their official website:
Mono is a software platform designed
to allow developers to easily create
cross platform applications. It is an
open source implementation of
Microsoft's .Net Framework based on
the ECMA standards for C# and the
Common Language Runtime. We feel that
by embracing a successful,
standardized software platform, we can
lower the barriers to producing great
applications for Linux.
Their official website has a lot of information about IDE's and other helpful information about the project.