There is an application .NET Core, which is hosted on IIS in production and uses Negotiate Windows authorization (intranet). I'm trying to run it locally on Mac OS, but I can't get any local account data. Are there any alternative ways to do this on a Mac?
Related
We are migrating a Webforms application based on .NET framework to .NET Core 5. As a part of the process we have decided to break down the single big app into multiple smaller application. As a first step we want to move the Login feature into a separate .NET Core app. This login app will authenticate users and will issue auth-cookie which will be used by the other apps and the old webforms application as well.
For this auth-cookie sharing to work and for other reasons, I need to get all the web apps running on same port but under different virtual directories. For example
http://localhost:5000/ -> This will be the old webforms app
http://localhost:5000/login -> This will be .NET Core login app
http://localhost:5000/admin -> This will be say .NET core admin app
I know we can set this up easily in production environment using IIS virtual applications or with azure front door etc. But we want to enable an all local (no internet needed) development setup which is also very easy to get up and running.
Is it possible to configure .NET core and IIS Express to behave like this on a single machine? All our developers use Windows 10 Home/Pro. Nobody has IIS installed on their dev boxes and we prefer to keep it that way.
I want to run a ASP.Net Core webapplication on a Windows 7 machine without having to install Visual Studio.
Can I just install .Net Core on the production environment or are there some preconditions that have to be met prior to installing .Net Core?
I tried out some scenarios and I found out the following:
For running .Net Core you only need the .Net Core runtime (or the SDK) installed on the production environment. You can find the downloads here: https://github.com/dotnet/core/blob/master/release-notes/download-archive.md
For ASP.Net Core, which uses Kestrel for hosting, you only need the runtime (or the SDK) as well. (I tested this on Windows 7 and Linux Debian)
When hosting with IIS, see Andre.Santarosa answer
Prior to run .NET Core on windows 7, your system must have SP1 and Hotfix KB2533623 insalled, install IIS package via Control Panel then DotNetCore WindowsHosting (this allow IIS to handle ASP.NET Core requests) - Link: https://go.microsoft.com/fwlink/?LinkID=827547
When you create your IIS application, it will create an application pool, set .NET CLR in this pool to "No Managed Code".
This should be enough you to run
I'm an asp.net developer and recently trying to archive asp.net-core.
Since it's quite new, I would like to ask, how do you launch a asp.net-core project in a Windows machine?
For normal asp.net, my approach is publishing the project using Visual Studio, bring everything to a Windows machine, use IIS to create a website and point the directory to my physical file.
How about a website that created by asp.net-core?
Do I need to install asp.net-core in server machine? (i don't prefer this)
What should I do with the published file? There are two folders generated after publishing the project:
netcoreapp1.0
PublishOutput
Well, you still can use the file system mechanism to publish an ASP.NET Core project from Visual Studio. But VS uses the dotnet CLI under the hood to do the same stuff. Usually you configure your deployment depending upon your hosting environment such as Windows Server and Linux Server.
For Windows Server
You have to install ASP.NET Core Module in order to publish on IIS successfully. This will also install .NET Core SDK. You can than have the advantages of SSL Terminations and others provided by IIS on Windows Server.
For Linux
You have to use the .NET Core SDK here as well for a published app to acquire the .NET Core runtime (This is why you get those 2 folders). You use Nginx or HAProxy to get all SSL Terminations, Port-Forwarding etc.
I have two web based application. One of them is a WCF server application and the other is a client application and consume first application services.
When they are hosted in a Windows 8 machine's IIS they work good. But when they are hosted in Windows 8.1 they do not work. Client application shows a timeout error message.
Strange point is when client application in Windows 8 connects to server application in Windows 8.1 it works with no problem. If I connect Windows 8.1 client application of Windows 8 server application it works too.
Initially I guessed it may be related to IPv6 so tried to test several IP addresses like localhost, [::1] and many others. But nothing changed.
Now I guess Windows 8.1 has forbidden self WCF hosting (Client and Server in same machine). But have now idea how can I solve problem.
If I use WCFTesetClient in Windows 8 machine to test Windows 8 itself or Windows 8.1, both of them works.
I'm using WSHttpBinding. Both applications are ASP.NET MVC web applications hosted in IIS.
UPDATE:
Why both server and client are on same machine? Because this is a dev machine. In operational environment server and client are on separate machines.
I have a WCF works fine in all Windows 7 versions except Home edition. Is there anything more to do with Windows 7 Home editions to invoke the WCF ?
From Unsupported Scenarios of WCF
For various reasons, Windows Communication Foundation (WCF) does not
support some specific security scenarios. For example, Windows XP Home
Edition does not implement the SSPI or Kerberos authentication
protocols, and therefore WCF does not support running a service with
Windows authentication on that platform