Publish a dotnetcore3 (was 2.2) project to remote IIS (8.5 ) + Swashbuckle/Swagger

  • Posted:
  • Proposals: 17
  • Remote
  • #2592331
  • OPPORTUNITY
  • PRE-FUNDED
  • Awarded
The One Technologies
Tanzeel A.Natrix Software P.Ramesh M.Shakir J. + 12 others have already sent a proposal.
  • 9

Description

Experience Level: Entry
I have a 'Hello World' dotnet 2.2 project with a Swagger API (its the bear bones on an API site).
Moving from V2 to V3 you notice the change with "Newtonsoft.Json.Converters" for when you are pulling in settings.
The main point issue is just publishing the project to IIS.
dotnet core 2.2 is quite different to 3.0 - code upgrading is required.

If I copy the v2.2 then it complains that it cannot see the 2.2 lib (because its now at v3)
This all worked fine on the LocalHost in V2.2 but in v3 JSON is built in.
All this aside getting the App to start, to get the Swagger to display - I only get 404.
I have tried publishing to Azure using the VS2019 built in Publish but that does not work.
The DevReach is meant to just work in IIS.
So if the DevReach was the basic hello world project that should work in IIS, fine locally why not remotely?

https://github.com/danroth27/BlazorWeather
https://github.com/jamesmontemagno/DevReach - James Montemagno @ DevReach2019 in Sofia
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-3.0
https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-core-3-1-preview-1/

New Proposal

Create an account now and send a proposal now to get this project.

Sign up

Clarification Board Ask a Question

  • Sumair I.

    Before publish, rebuild project in a a Release Mode and then publish.Are you doing it?

  • Sumair I.

    Hi there , i got the same kind of issue with me yesterday and i resolve this fortunately. if i tell you the resolution can you award me this project?