Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
U

User 9445141

@User 9445141
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • N-Tier best practices when using in MVC application
    U User 9445141

    Hello! I am just curious if it would be good practice to have all of my layers in the same project, or should I create a separate project(Web API) as my data layer, for example, and call it from my MVC application. I feel I can still create the separate layers in the same project but just use a controller as the middle layer to call a Web API that would handle the database inquiries, then report back to the controller for the View the user is interacting with. Does this sound like good practices for sticking with n-tier architecture? Thank you!

    C# architecture asp-net database json tutorial
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups