To use ASP.NET MVC or not to

Question

0.00/5 (No votes)

See more:

I have three program that I wrote for the company I work for: One deals with tracking requests for drawings from project managers, the other two are schedule programs that track work being done on the requests. These programs were written in VB.Net, and use DataGridViews to display the schedule lists from SQL Server. These forms have buttons to perform actions to list items, ComboBoxes to sort the list by employee, DataGridView double-click and ContextMenu features, and a TextBox and button for searching the list.

My company is now wanting these to be web-based apps (running on local IIS). I know C# and have learned some of ASP.Net MVC, but I'm unsure if ASP.Net MVC is the way to go for these projects. I've researched sites created with MVC, and these look like you would expect a website to look. So, in your professional opinion, would ASP.Net MVC be a good fit for these types of projects? Have any of you seen anything like I mentioned done with ASP.Net MVC?

Thanks for your time and any insight you can offer!

What I have tried:

Researched sites that have been designed with ASP.Net MVC.

Posted 1-Nov-17 10:43am

WolfmanLee

Updated 1-Nov-17 23:52pm

Add a Solution

Comments

j snooze 1-Nov-17 17:12pm

I don't see why not. I went from using webforms to MVC (dabbled a little in angular as well). With so many jquery widgets out there you can probably replicate all that functionality. I've used the https://datatables.net/ jquery plugin effectively for sorting and searching through the datagrid. there are some context menu items as well. Just mix and match and you'll learn alot. Since most development is web these days the skills will be welcome on your resume :)

j snooze 1-Nov-17 17:13pm

I should note that once I went to MVC, I didn't want to go back to webforms.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

David_Wimbley · Answer 1 · 2017-11-01T13:23:00

Going with asp.net mvc or not really depends on whether its the right tool for the job/meets your needs. From your projects you've described it sounds like a fine application...but so does just about all the other "billions" of frameworks out there that are available for you to use. You specifically mention DataGridViews...these are nothing more than tables (or however you choose to render it) in HTML which would require looping over the collection of data you are trying to display. You can render data grid views in a bunch of different ways in MVC (and any web based framework).

If this is something you need to crank out in a short amount of time...go with what you know and are familiar with to eliminate the learning curve so you can deliver on time.

If asp.net mvc is new to you and you've got some time before it needs to be delivered and you feel like you want to learn something new...go with MVC framework.

If you want to be bleeding edge, go a JS only front end mvc framework path.

I use MVC all the time and love working with it, to me it is easy to use and understand but again...just depends on what you want to do.

F-ES Sitecore · Answer 2 · 2017-11-01T23:52:00

To move a desktop app to a web app is probably going to require it to be re-written and re-architected anyway no matter what tech you go with. You'll also have to learn a lot of new concepts. Your biggest problem will be going into it wondering how you can simply translate or convert your way of doing desktop apps to a web way. Instead you'll have to ignore everything about desktop development and get into a web mindframe; you are not going to have the ease of control over the front end as you do in a desktop app and you need to deal with the fact that web apps are stateless and you can't load the GUI with state\logic like you will with a desktop app. A web app tends to have a dumb client and a smart server whereas a desktop app only has one component.

Microsoft designed webforms (the predecessor to MVC) to be more familiar to people moving from desktop apps and it tries to emulate the data-bound, event-driven paradigm, but you'll still have the issues I mentioned. In some ways using MVC will keep you focussed on the fact that you're dealing with all new technology.

To use ASP.NET MVC or not to

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0