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.
Related
I stumbled across the entire Microsoft Localization Extensions section the other day. IStringLocalizer/ILocalizedString, all that.
I've already got a hand-rolled approach to localization in my current app (.NET 6, WPF, Prism), but I would gladly convert over to this if appropriate; Because it's much easier for a new developer coming on a project to understand something when there are reams of standard MS documentation about it rather than trying to guess what I had in mind.
But virtually every discussion or example of IStringLocalizer that I can find seems to relates to ASP.NET or at least web apps. The docs all seem to assume you're writing ASP.NET.
So are these extensions meant just for ASP.NET and web apps? Is anyone using this approach outside of web apps? And if so can anyone point me to any examples?
-Joe
No, as by docs (2021):
In this article, you will learn how to use the IStringLocalizer and IStringLocalizerFactory implementations. All of the example source code in this article relies on the Microsoft.Extensions.Localization and Microsoft.Extensions.Hosting NuGet packages. For more information on hosting, see .NET Generic Host.
There is no mention of being asp.net specific, although, asp.net applications obviously tend to make use of it as well.
The examples do not use asp.net.
I've used the resx file approach in the early days a lot in WPF applications - although slightly different, I see no reason why it wouldn't work in any regular application.
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 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.
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 the Windows Features control panel applet, under Internet Information Services → World Wide Web Services → Application Development Features, there are two options: ".NET Extensibility" and "ASP.NET".
What is the difference between these two options? If I'm developing simple ASP.NET web applications / services, is there any need for the .NET Extensibility option?
I Google'd the terms, and came up with this link:
http://forums.iis.net/t/1146942.aspx
This link confuses me, because the response (from a supposed Microsoft employee) says that to test for .NET Extensibility, you create a simple ASPX page, and try to load it. That seems (to ME) more like a test for the ASP.NET option.
Any clues?
In versions of IIS prior to 7.0, the ASP.NET pipeline was separate from the web server's request processing pipeline. The web server's functionality was usually extended via ISAPI filters and extensions.
However, in IIS 7.x they are more tightly integrated, which allows for the server to be extended using managed code, via the ASP.NET extensibility APIs. Two primary ways this can be done are via modules and handlers, which are quite similar to ISAPI filters and extensions respectively.
The APIs of interests are:
System.Web.IHttpModule
System.Web.IHttpHandler
System.Web.IHttpAsyncHandler.
You can read more about how to extend the server in the articles below.
http://learn.iis.net/page.aspx/243/aspnet-integration-with-iis-7/
http://learn.iis.net/page.aspx/170/developing-a-module-using-net/
http://msdn.microsoft.com/en-us/magazine/cc164128.aspx#S4
This site talks about .Net extensibility in relation to IronPython: http://www.asp.net/learn/whitepapers/ironpython
You might want to review more info at this site: http://aspnetextensibility.com/
Assuming your developing asp.net sites in c# or vb.net then you will need the ASP.Net support. To sum up, it's probably one of those things you'll be able to define when you actually need the .Net Extensibility option installed.
However, if you really want to know: .Net Extensibility is an IIS 7 feature which brings the ability to extend IIS 7 via the runtime extensibility model into the core server product.
Building "regular" sites (whatever those are), don't worry about it. Needing to get down and dirty by modifying the pipeline through modules or handlers? Install it. Either way, you are still going to need the regular ASP.Net support installed.
With regards to what the MS guy said about the Hello World file.. Ignore that, he didn't read the full question...