How to archive a medium-sized MVC application

I am working on creating an MVC application for an existing error sorter, ASP.net website.

I use to transfer data to a querysting website and am not sure how to do this in MVC. I really understand the MVC model and how everything works, but as a beginner, my thought process is a bit overshadowed.

Views / Project / Index.aspx - My first page, List of projects

<ul id="ProjectList">
    <% foreach (var item in Model) { %>
        <li><%= Html.ActionLink("Details", "IssueType", new { id=item.ProjectId })%></li>
    <% } %>
</ul>

On my ASP.Net website, to create a problem for this project, I get a URL similar to this:

Issue.aspx?pid=3&issuetypeid=6

I'm coming from

Projects.aspx --> IssueTypes.aspx --> Issue.aspx

collecting projectId and issueTypeId objects on the path in the query string.

This allows me to write to the database, knowing the identifiers of the project identifier and the problem identifier.

How would it be like in MVC architecture?

+3
2

Nerd Dinner Asp.Net MVC, . RESTful - REST.

, Nerd Dinner, MVC, REST.

0

Nerd Dinner - , .

, , - Nerd Dinner . , .

ASCX , . .

, . , v admins.

asp.net MVC . .

+2

Source: https://habr.com/ru/post/1711525/


All Articles