Welcome tag moderator AKA Unofficial DEV cheerleader. While most of my friends are found on SnapChat or Tic-Toc, you can find me here. And I OOP, but Iām not a VSCO girl.
I just tried this but there was no ValuesController generated. There was only a WeatherForecastController with just a Get method. There was also no wwwroot generated. I'm running .Net Core 3.0.100 on Windows 10.
I was able to start it and got a result through the browser. Now I can look through the attributes for defining the routes.
Thanks for the post.
Welcome tag moderator AKA Unofficial DEV cheerleader. While most of my friends are found on SnapChat or Tic-Toc, you can find me here. And I OOP, but Iām not a VSCO girl.
Welcome tag moderator AKA Unofficial DEV cheerleader. While most of my friends are found on SnapChat or Tic-Toc, you can find me here. And I OOP, but Iām not a VSCO girl.
Welcome tag moderator AKA Unofficial DEV cheerleader. While most of my friends are found on SnapChat or Tic-Toc, you can find me here. And I OOP, but Iām not a VSCO girl.
Oh, that's so sweet of you, but it's not really necessary, I've got the gist of what's going on with this. I need to concentrate on building this API for our project. Now at least the structure of how to do it is put together. I'm adjusting things to run async for the rest of the methods.
Hi Katie! Thanks for your comment, indeed you have differences because I've used netcore 2.2. I'll clarify this in the post. Nevertheless, the explanation of how it works and what the different annotations mean remains the same.
Thanks again!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I just tried this but there was no
ValuesControllergenerated. There was only aWeatherForecastControllerwith just aGetmethod. There was also nowwwrootgenerated. I'm running .Net Core 3.0.100 on Windows 10.I was able to start it and got a result through the browser. Now I can look through the attributes for defining the routes.
Thanks for the post.
Hi there Katie, are you using Visual Studio 2019? or are you on VS Code?
I used VS Code. Why, is there a difference?
Not really but I was gonna recommend simply creating the web API project via Visual Studio 2019, since visual studio will template it for you.
Or alternatively using the visual studio 2019 create conroller function, which will create a controller skeleton for you
Odd that the
dotnet new webapidid not correctly create your project template.perhaps if you were to install
dotnet tool install --global dotnet-aspnet-codegeneratorvia powershell, more info on that available here and here
In the future, I'll probably scaffold using VS2019. I only did it through the command line to follow the post.
I think I got different results because I'm using a newer version of .NET Core. There is so much stuff here to learn š
Could be, I can't say I tried the
dotnet newcommand yet on .NET Core 3.0.If you'd like I could give it a test at home and let you know my results.
Oh, that's so sweet of you, but it's not really necessary, I've got the gist of what's going on with this. I need to concentrate on building this API for our project. Now at least the structure of how to do it is put together. I'm adjusting things to run async for the rest of the methods.
Well happy developing!
Hi Katie! Thanks for your comment, indeed you have differences because I've used netcore 2.2. I'll clarify this in the post. Nevertheless, the explanation of how it works and what the different annotations mean remains the same.
Thanks again!