Why Does ASP.NET Core 2 Web API Give 404 Error?












0














There was no problem until I added a new controller to my ASP.NET Core (v2.1) Web API. Now, all my controllers are giving 404 error. The last added controller is UsersController. I'm not sure if I've changed something else.



UsersController.cs



using System.Threading.Tasks;
using DatingApp.API.Data;
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Mvc;

namespace DatingApp.API.Controllers
{
[Authorize]
[Route("api/[controller]")]
[ApiController]
public class UsersController : ControllerBase
{
private readonly IDatingRepository _repo;
public UsersController(IDatingRepository repo)
{
_repo = repo;
}

[HttpGet]
public async Task<IActionResult> GetUsers()
{
var users = await _repo.GetUsers();

return Ok(users);
}

[HttpGet("{id}")]
public async Task<IActionResult> GetUser(int id)
{
var user = await _repo.GetUser(id);

return Ok(user);
}
}
}


launchSettings.json



{
"profiles": {
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"launchUrl": "api/values",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
},
"DatingApp.API": {
"commandName": "Project",
"launchBrowser": false,
"launchUrl": "api/values",
"applicationUrl": "http://localhost:5000",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
}


Startup.cs



public void Configure(IApplicationBuilder app, IHostingEnvironment env, Seed seeder)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler(builder => {
builder.Run(async context => {
context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
var error = context.Features.Get<IExceptionHandlerFeature>();
if(error != null)
{
context.Response.AddApplicationError(error.Error.Message);
await context.Response.WriteAsync(error.Error.Message);
}
});
// app.UseHsts();
});

// app.UseHttpsRedirection();
// seeder.SeedUsers();
app.UseCors(x => x.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader());
app.UseAuthentication();
app.UseMvc();
}
}


I've tried to restart Kestrel web server until now. Did not work for me.










share|improve this question




















  • 2




    You must have changed something else, roll back your changes until it starts working again.
    – DavidG
    Nov 12 '18 at 22:46










  • I'm not sure if I've changed something else. Can you check your git commit history to identify the change?
    – mjwills
    Nov 12 '18 at 23:15










  • Instead of, "ASPNETCORE_ENVIRONMENT": "Development" I used "ASPNETCORE_ENVIRONMENT": "Production" and it's gone. I can't find anything to say.
    – Tayfun
    Nov 12 '18 at 23:17


















0














There was no problem until I added a new controller to my ASP.NET Core (v2.1) Web API. Now, all my controllers are giving 404 error. The last added controller is UsersController. I'm not sure if I've changed something else.



UsersController.cs



using System.Threading.Tasks;
using DatingApp.API.Data;
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Mvc;

namespace DatingApp.API.Controllers
{
[Authorize]
[Route("api/[controller]")]
[ApiController]
public class UsersController : ControllerBase
{
private readonly IDatingRepository _repo;
public UsersController(IDatingRepository repo)
{
_repo = repo;
}

[HttpGet]
public async Task<IActionResult> GetUsers()
{
var users = await _repo.GetUsers();

return Ok(users);
}

[HttpGet("{id}")]
public async Task<IActionResult> GetUser(int id)
{
var user = await _repo.GetUser(id);

return Ok(user);
}
}
}


launchSettings.json



{
"profiles": {
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"launchUrl": "api/values",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
},
"DatingApp.API": {
"commandName": "Project",
"launchBrowser": false,
"launchUrl": "api/values",
"applicationUrl": "http://localhost:5000",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
}


Startup.cs



public void Configure(IApplicationBuilder app, IHostingEnvironment env, Seed seeder)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler(builder => {
builder.Run(async context => {
context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
var error = context.Features.Get<IExceptionHandlerFeature>();
if(error != null)
{
context.Response.AddApplicationError(error.Error.Message);
await context.Response.WriteAsync(error.Error.Message);
}
});
// app.UseHsts();
});

// app.UseHttpsRedirection();
// seeder.SeedUsers();
app.UseCors(x => x.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader());
app.UseAuthentication();
app.UseMvc();
}
}


I've tried to restart Kestrel web server until now. Did not work for me.










share|improve this question




















  • 2




    You must have changed something else, roll back your changes until it starts working again.
    – DavidG
    Nov 12 '18 at 22:46










  • I'm not sure if I've changed something else. Can you check your git commit history to identify the change?
    – mjwills
    Nov 12 '18 at 23:15










  • Instead of, "ASPNETCORE_ENVIRONMENT": "Development" I used "ASPNETCORE_ENVIRONMENT": "Production" and it's gone. I can't find anything to say.
    – Tayfun
    Nov 12 '18 at 23:17
















0












0








0


1





There was no problem until I added a new controller to my ASP.NET Core (v2.1) Web API. Now, all my controllers are giving 404 error. The last added controller is UsersController. I'm not sure if I've changed something else.



UsersController.cs



using System.Threading.Tasks;
using DatingApp.API.Data;
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Mvc;

namespace DatingApp.API.Controllers
{
[Authorize]
[Route("api/[controller]")]
[ApiController]
public class UsersController : ControllerBase
{
private readonly IDatingRepository _repo;
public UsersController(IDatingRepository repo)
{
_repo = repo;
}

[HttpGet]
public async Task<IActionResult> GetUsers()
{
var users = await _repo.GetUsers();

return Ok(users);
}

[HttpGet("{id}")]
public async Task<IActionResult> GetUser(int id)
{
var user = await _repo.GetUser(id);

return Ok(user);
}
}
}


launchSettings.json



{
"profiles": {
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"launchUrl": "api/values",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
},
"DatingApp.API": {
"commandName": "Project",
"launchBrowser": false,
"launchUrl": "api/values",
"applicationUrl": "http://localhost:5000",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
}


Startup.cs



public void Configure(IApplicationBuilder app, IHostingEnvironment env, Seed seeder)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler(builder => {
builder.Run(async context => {
context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
var error = context.Features.Get<IExceptionHandlerFeature>();
if(error != null)
{
context.Response.AddApplicationError(error.Error.Message);
await context.Response.WriteAsync(error.Error.Message);
}
});
// app.UseHsts();
});

// app.UseHttpsRedirection();
// seeder.SeedUsers();
app.UseCors(x => x.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader());
app.UseAuthentication();
app.UseMvc();
}
}


I've tried to restart Kestrel web server until now. Did not work for me.










share|improve this question















There was no problem until I added a new controller to my ASP.NET Core (v2.1) Web API. Now, all my controllers are giving 404 error. The last added controller is UsersController. I'm not sure if I've changed something else.



UsersController.cs



using System.Threading.Tasks;
using DatingApp.API.Data;
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Mvc;

namespace DatingApp.API.Controllers
{
[Authorize]
[Route("api/[controller]")]
[ApiController]
public class UsersController : ControllerBase
{
private readonly IDatingRepository _repo;
public UsersController(IDatingRepository repo)
{
_repo = repo;
}

[HttpGet]
public async Task<IActionResult> GetUsers()
{
var users = await _repo.GetUsers();

return Ok(users);
}

[HttpGet("{id}")]
public async Task<IActionResult> GetUser(int id)
{
var user = await _repo.GetUser(id);

return Ok(user);
}
}
}


launchSettings.json



{
"profiles": {
"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"launchUrl": "api/values",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
},
"DatingApp.API": {
"commandName": "Project",
"launchBrowser": false,
"launchUrl": "api/values",
"applicationUrl": "http://localhost:5000",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
}
}
}
}


Startup.cs



public void Configure(IApplicationBuilder app, IHostingEnvironment env, Seed seeder)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler(builder => {
builder.Run(async context => {
context.Response.StatusCode = (int)HttpStatusCode.InternalServerError;
var error = context.Features.Get<IExceptionHandlerFeature>();
if(error != null)
{
context.Response.AddApplicationError(error.Error.Message);
await context.Response.WriteAsync(error.Error.Message);
}
});
// app.UseHsts();
});

// app.UseHttpsRedirection();
// seeder.SeedUsers();
app.UseCors(x => x.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader());
app.UseAuthentication();
app.UseMvc();
}
}


I've tried to restart Kestrel web server until now. Did not work for me.







c# asp.net-core-webapi asp.net-core-2.1






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 12 '18 at 22:45

























asked Nov 12 '18 at 22:39









Tayfun

12




12








  • 2




    You must have changed something else, roll back your changes until it starts working again.
    – DavidG
    Nov 12 '18 at 22:46










  • I'm not sure if I've changed something else. Can you check your git commit history to identify the change?
    – mjwills
    Nov 12 '18 at 23:15










  • Instead of, "ASPNETCORE_ENVIRONMENT": "Development" I used "ASPNETCORE_ENVIRONMENT": "Production" and it's gone. I can't find anything to say.
    – Tayfun
    Nov 12 '18 at 23:17
















  • 2




    You must have changed something else, roll back your changes until it starts working again.
    – DavidG
    Nov 12 '18 at 22:46










  • I'm not sure if I've changed something else. Can you check your git commit history to identify the change?
    – mjwills
    Nov 12 '18 at 23:15










  • Instead of, "ASPNETCORE_ENVIRONMENT": "Development" I used "ASPNETCORE_ENVIRONMENT": "Production" and it's gone. I can't find anything to say.
    – Tayfun
    Nov 12 '18 at 23:17










2




2




You must have changed something else, roll back your changes until it starts working again.
– DavidG
Nov 12 '18 at 22:46




You must have changed something else, roll back your changes until it starts working again.
– DavidG
Nov 12 '18 at 22:46












I'm not sure if I've changed something else. Can you check your git commit history to identify the change?
– mjwills
Nov 12 '18 at 23:15




I'm not sure if I've changed something else. Can you check your git commit history to identify the change?
– mjwills
Nov 12 '18 at 23:15












Instead of, "ASPNETCORE_ENVIRONMENT": "Development" I used "ASPNETCORE_ENVIRONMENT": "Production" and it's gone. I can't find anything to say.
– Tayfun
Nov 12 '18 at 23:17






Instead of, "ASPNETCORE_ENVIRONMENT": "Development" I used "ASPNETCORE_ENVIRONMENT": "Production" and it's gone. I can't find anything to say.
– Tayfun
Nov 12 '18 at 23:17



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271126%2fwhy-does-asp-net-core-2-web-api-give-404-error%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271126%2fwhy-does-asp-net-core-2-web-api-give-404-error%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Xamarin.iOS Cant Deploy on Iphone

Glorious Revolution

Dulmage-Mendelsohn matrix decomposition in Python