fix to remove usage of IIS port. (dotnet-architecture#552)

* fix to not using IIS port. add more information in readme to start application with correct profile correcponding in the appsettings * Update README.md Co-authored-by: Steve Smith <steve@kentsmiths.com>
pierre3 · Oct 24, 2021 · 530df9d · 530df9d
1 parent c02efcd
commit 530df9d
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -47,7 +47,7 @@ After cloning or downloading the sample you should be able to run it using an In
 
 ![eShopOnWeb home page screenshot](https://user-images.githubusercontent.com/782127/88414268-92d83a00-cdaa-11ea-9b4c-db67d95be039.png)
 
-Most of the site's functionality works with just the web application running. However, the site's Admin page relies on Blazor WebAssembly running in the browser, and it must communicate with the server using the site's PublicApi web application. You'll need to also run this project. You can configure Visual Studio to start multiple projects, or just go to the PublicApi folder in a terminal window and run `dotnet run` from there. Note that if you use this approach, you'll need to stop the application manually in order to build the solution (otherwise you'll get file locking errors).
+Most of the site's functionality works with just the web application running. However, the site's Admin page relies on Blazor WebAssembly running in the browser, and it must communicate with the server using the site's PublicApi web application. You'll need to also run this project. You can configure Visual Studio to start multiple projects, or just go to the PublicApi folder in a terminal window and run `dotnet run` from there. After that from the Web folder you should run `dotnet run --launch-profile Web`. Now you should be able to browse to `https://localhost:5001/`.   Note that if you use this approach, you'll need to stop the application manually in order to build the solution (otherwise you'll get file locking errors).
 
 If you wish to use the sample with a persistent database, you will need to run its Entity Framework Core migrations before you will be able to run the app, and update the `ConfigureServices` method in `Startup.cs` (see below).
 

diff --git a/src/PublicApi/appsettings.Development.json b/src/PublicApi/appsettings.Development.json
@@ -1,7 +1,7 @@
 {
   "baseUrls": {
     "apiBase": "https://localhost:5099/api/",
-    "webBase": "https://localhost:44315/"
+    "webBase": "https://localhost:5001/"
   },
   "Logging": {
     "LogLevel": {

diff --git a/src/PublicApi/appsettings.json b/src/PublicApi/appsettings.json
@@ -1,7 +1,7 @@
 {
   "baseUrls": {
     "apiBase": "https://localhost:5099/api/",
-    "webBase": "https://localhost:44315/"
+    "webBase": "https://localhost:5001/"
   },
   "ConnectionStrings": {
     "CatalogConnection": "Server=(localdb)\\mssqllocaldb;Integrated Security=true;Initial Catalog=Microsoft.eShopOnWeb.CatalogDb;",