使用ASP.NET MVC或不使用 [英] To use ASP.NET MVC or not to

问题描述

我为我所工作的公司编写了三个程序：一个用于跟踪项目经理的图纸请求，另外两个是用于跟踪对请求进行的工作的计划程序。这些程序是用VB.Net编写的，并使用DataGridViews显示SQL Server的计划列表。这些表单包含执行列表项操作的按钮，按员工排序列表的组合框，DataGridView双击和ContextMenu功能，以及用于搜索列表的TextBox和按钮。



我的公司现在希望这些是基于Web的应用程序（在本地IIS上运行）。我了解C＃并学习了一些ASP.Net MVC，但我不确定ASP.Net MVC是否适合这些项目。我研究过使用MVC创建的网站，看起来你希望网站看起来像。那么，在您的专业意见中，ASP.Net MVC是否适合这些类型的项目？你有没有看到我提到的ASP.Net MVC做过的事情？



感谢您的时间和任何洞察力！



我尝试过：



研究过使用ASP.Net MVC设计的网站。

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.

推荐答案

使用asp.net mvc或不是真的取决于它是否适合工作/满足您的需求。你所描述的项目听起来就像一个很好的应用程序......但是所有其他数十亿框架都可以供你使用。你特别提到DataGridViews ......这些只不过是HTML中的表格（或者你选择渲染它），这需要循环你想要显示的数据集合。您可以在MVC（以及任何基于Web的框架）中以多种不同的方式呈现数据网格视图。



如果这是你需要做的事情时间量...与您熟悉和熟悉的东西一起消除学习曲线，以便您按时交付。



如果asp.net mvc是新的对你和你有一些时间需要交付，你觉得你想学习新的东西......去MVC框架。



如果你想要成为最前沿的，去JS只有前端的mvc框架路径。



我一直都在使用MVC，喜欢用它，对我来说这很容易再次使用和理解......只取决于你想做什么。

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.

将桌面应用程序移动到Web应用程序可能需要重新编写它无论你采用何种技术，无论如何都要重新设计。你还必须学习很多新概念。您最大的问题将是它想知道如何简单地将您的桌面应用程序转换或转换为Web方式。相反，你将不得不忽略有关桌面开发的所有内容并进入Web思维框架;您不会像在桌面应用程序中那样轻松控制前端，并且您需要处理Web应用程序无状态的事实，并且您无法像使用state\logic一样加载GUI使用桌面应用。一个Web应用程序往往有一个愚蠢的客户端和一个智能服务器而一个桌面应用程序只有一个组件。



微软设计的webforms（MVC的前身）更多对于从桌面应用程序迁移的人来说，它很熟悉它试图模拟数据绑定的，事件驱动的范例，但你仍然会遇到我提到的问题。在某些方面，使用MVC会让你专注于你正在处理所有新技术的事实。

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.

这篇关于使用ASP.NET MVC或不使用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！