I wanted to know if writing a self hosted WebApi project using async await keyword features would be supported in Mono on Linux..
I found this:
on the Mono website on the compability page:
and then there is some text saying limited ASP.NET 4.5 async stack.
So... i'm confused... what async/await aspect is or isn't supported with Mono 4.5 ?
Mono cloned ASP.NET 2 pipeline a long time ago, to support the classic ASP.NET WebForms based on "System.Web" assembly. That model was a sync one due to Microsoft's initial design.
However, later Microsoft added many async features to the pipeline (System.Web) during .NET 4/4.5 time frame, and that's a new design Mono does not yet fully clone. That's probably the meaning behind the paragraph.
I don't think Mono should move ahead with "System.Web" as even Microsoft gives it up in favor of OWIN a while ago, and now ASP.NET 5/DNX.
Update:
Please switch to ASP.NET Core today, as it is simply the best in this field for cross platform web applications.
Related
3 years ago, I worked on a corebanking project where we used Service Bus and it worked very well, and now we are trying to make a migration From .Net Framework to .Net Standard 2.0 but we still do not have an accurate view on the feasibility of things, I would just like to know if the current version of Service Bus is supported by .Net Standard 2.0 .
Thank you in advance. of great help.
I would just like to know if the current version of Service Bus is supported by .Net Standard 2.0
The question probably should be inverted - what version of .NET Standard the new Azure Service Bus client is compliant with. As of today, it's compliant with .NET Standard 1.3. This means you won't have the features that are associated with .NET Standard 2.0. One of those would be transaction semantics.
Future milestones contain issues for features that are not available yet. You can track specific ones on GitHub if you happened to rely on those.
Note that there were some design changes in the new client such as
Entity clients vs message senders/receivers.
Simplified brokered message, removal of message serialization.
Separation of run-time and configuration planes.
Addition on incoming and going pipelines to support plugins.
etc.
You should analyze those and review how they will affect your migration. The repository is now open-sourced and it is much easier to follow up with the development team to raise issues.
I've being trying to find how to connect a Xamarin or Universal app to Akka.net. I'd like to receive notifications from actors directly to the client like Orleans does. I did not find anything like this in the getakka web page. Is something that is not covered by the framework or it's because there are no .net Core libraries for Xamarin and Universal apps?
Regards.
There's no .Net Core support as yet.
Referring to this post by one of the primary owners of Akka.net, specifically half way down
after yesterday’s announcements I’m wondering if the .NET Core roadmap is even valid anymore. We had talked about starting work on Akka.NET for .NET Core in 2016. As of today, I’m thinking that .NET Core probably won’t be ready until much later than that.
... I can’t have that, and I’m fortunate enough to be in a position where I can and am choosing not to. I’m sticking with .NET 4.5.2 until .NET Core is solid.
Although this was dated May last year, I'm not aware of any changes on this front. I may be wrong, however.
I want to learn how to build websites using the Microsoft ASP.NET framework on a Mac running OS X 10.10.5. I will be following along with an online course that uses ASP.NET MVC 5. All of the tutorials I have read so far say to use Homebrew's aspnet/dnx repo to install ASP.NET. However, according to the GitHub page:
"This repository is obsolete and no longer used or maintained."
A link on the page redirects to .Net Core
So, my question is: how do I install ASP.NET MVC 5 on my Mac, not .NET Core?
Thanks!
If you want to start developing for .NET (including ASP.NET MVC and related technologies) on OSX, you'll need to look towards .NET Core. There are instructions there on how to install it and how to write code for it. There are good examples linked at the bottom of the page.
Please be aware that, as of this time, the related OSX technologies are not full released, so prepare for some hiccups along the way (though...it's getting better!).
You want to use https://www.microsoft.com/net/core#macos
Follow the examples here once you're set up: https://docs.asp.net/en/latest/getting-started.html
dnx is deprecated as mentioned on their GitHub page.
This repository is obsolete and no longer used or maintained.
Also, for what it's worth - dnx/dnvm were CLI tooling used to build/bootstrap .net applications. They were used during the beta/rc versions of what is now known as dotnet core. The new https://github.com/dotnet/cli has replaced dnx.
Nothing is better than using the OS with the full capabilities as Windows to work with ASP.NET or Windows Forms (really beautiful on Windows) as a student I've been trying to get this things on mac but is kind of difficult and as future engineer, if I have to get complex operations to do something, due, something is wrong, engineering solutions is to make the easiest possible solution and that one is using Windows. Less paint in the ass.
I have a web application which runs on Azure which is currently running MVC3/C#, EF6.1, .NET4.5. I would like to upgrade it to MVC5 to be:
a) Current
b) Get benefit of new features
c) Get Performance gains.
This is a part of a performance project, so hopefully there will be performance gains from doing this, especially with the upgrade to Razor 2.
What would be the recommended upgrade approach to MVC5? Should I upgrade to MVC4 to start with, then go from MVC4 to MVC5, or straight to 5?
There's a handy documented guide by Rick Anderson which he wrote to upgrade from MVC4, the same applies to you with the exception of the fact that the "Old version" of DLLs he mentions will be different to the ones that you will have, but the outcome will still be the same.
You can find the guide HERE
in other words, now that we have Mono, has C# become just as OS-agnostic as Java when it comes to server-side web applications? Or are there still big limitations having to do with what Mono can/cannot do or maybe with what libraries can be made available to a C# server-side app on Linux?
The answer to 'can any (or most of) the ASP.NET apps be made to run' is YES. There's a page with some common pitfalls: Mono: Porting ASP.NET Applications (also of interest the Porting WinForms applications page)
The most common problems I've seen in the field[1] are, by number of occurrences:
Code that is not aware of case-sensitive filesystems or careless about file/path handling. These ones require work.
P/Invokes: there are a lot of P/Invokes to Windows native functions. Most of them are not supported in Mono (nor they make sense in a unix environment). However, we have mappings for a few or the most common ones (CloseHandle and such). These ones require redoing the same things using a .NET API.
Bugs: believe or not, there are still bugs in the 3M+ lines of code. We try to be responsive and fix bugs as soon as possible (and we'd love to do more, blame it on the 24h rotation period). The simpler the test case to reproduce the problem, the faster it gets fixed. File a bug report and we'll try to fix it ASAP.
Missing or unimplemented APIs: we still have these and try to focus on the most used ones. Some times we use the Moma Reports (see link below) to prioritize.
Take a look at the Moma Reports page, which contains user-submitted data about applications on which Moma has been run.
[1]: the field ranges from one of the largest ASP.NET deployments in the Western Hemisphere to small open source applicatoins.
Yes and no... yes, you can now run asp.net on Linux via Mono.
However, I think in practice you will find many more platform specific limitations than you would with similar Java applications. I rarely see major platform specific issues even in average quality software written in Java.
With ASP.Net, you'll routinely see apps and third party libraries that barely work on Mono, or just don't work at all. The porting effort may not be high, but its much higher than similar Java applications, in my experience.
Not every application:
The Mono API today is somewhere in
between .NET 2.0 and .NET 3.5 see our
Roadmap for details about what is
implemented.
From Can Mono run binaries produced by Visual Studio? in the Mono Faq General. You can view the detailed state of ASP.NET in Mono in the ASP Tests page.
A lot of useful information here from the Mono Team.
http://www.mono-project.com/ASP.NET