Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I was looking for advice around on whether which framework to consider for my university's final year project. I'm on my final year and need to create a project management website for demonstration of my programming skills. There'll be an admin, multiple users, such as student, project supervisor and lead (clients). I've already developed few functionalities using ASP.NET Web Forms but there have been little confusion on which approach will be better, as I've seen many web solutions available online mostly with MVC framework. As it's a university project for demonstration of an online project management system, it will not be the type of large scale web development.
It really does not matter if it will be large scale project or not, MVC is the way to do it. Web Forms are not supported anymore. Although they are great way of implementing web sites, they are old and they are really not scaling well with today web standard requirements. My advice is to use Default MVC app template that comes with Visual Studio and adjust it to your needs. AS far as users go, you can use MVC Filters to restrict access to certain actions or functionalities.
Use ASP.NET Core - it will be a good experience for your future interviews :)
This experience will also be useful for ASP.NET MVC 5 and WebApi 2.
I also faced same issue when i was doing my final year project. finally i decided to go with MVC and it helps me a lot to when finding an internship.it will really help in future interviews also. i just download sample MVC project from the internet and just follow their coding. i used http://www.sourcecodester.com/ to find sample MVC Projects.hope this help you.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'm a starter in web developing, weak at php-js-css but have c# experience.
For a new website project I want to use c# but have some problems with the view.
I won't use those standard-looking webform controls that I use for desktop apps, I need a better and modern appearance, a "Bootstrap-like view" for webform controls.
My goal is:
To be not having to learn js-css in detail for this website project, since it will take extra time for me to learn these. I want to solve this problem with c# compatible and easy to use tools / frameworks if possible.
For this purpose:
can I use a such a recommended framework class with c#,
or could just a css template do it,
or is there a 3rd simpler way
It is important for me to choose the right way before I start the project, any help is appreciated.
You absolutely can. You need to use javascript or typescript for the UI and then use Asp.Net WebApi to do any of the server-side functionality. Any of the popular javascript frameworks play very well with WebApi as long as you create the endpoints the correct way.
Here are some tutorials that can help get you started:
Hands On Lab: Build a Single Page Application (SPA) with ASP.NET Web API and Angular.js
AngularJS CRUD Operations with WebAPI, EF and Bootstrap
ASP.NET Web API application with Angularjs Forms and Bootstrap
Creating your first SPA Application using AngularJS and WebAPI – All CRUD Operations
Pluralsight also has a number of video tutorials that are well worth the cost if you can afford it.
Hope that helps.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I'm asking this just to see experiences from others.
For most of the cases having ASP MVC web site is an overhead. At least for me it's much cleaner and easier to have WebAPI which responds with JSON and then you can attach either SPA application or Mobile app or whatever.
I have a feeling that if you are using ASP MVC controllers will not be controllers, but controllers full of the if conditions and some session bags which are hanging around. Views are combination of HTML and Razor which in most cases looks really ugly and full of "TODOs" ;)
I can understand if it's used in older projects and now we just need to maintain them. But when you are starting a new one, why you would choose ASP.NET MVC or any other similar framework?
In my opinion, it is all about your expectations - if you need REST you should take WebAPI of course, but in case of RPC Style Actions requirements in your project, MVC will be better choice
It depends on the resources available. If you have a team already that is doing all pure UI (all request/response to the backend is via a RESTful API), then you can have those team create the UI for you and you can focus on the API. These UI applications are mostly client-facing products.
But sometimes in your team there is a need to develop in-house or internal applications such admin/operations applications, and the UI requirement is not as sophisticated , the teams skillset is not heavy on UI, and there is a need to develop the application ASAP, then I would go with MVC.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
We have a multi site project in Sitecore 6.5 Web Forms which requires decent refactoring, architecture redesign and we want to upgrade it to sitecore 8. Of course it will be easier to start something brand new, but the project is huge and probably it won't be possible to rewrite it to MVC in completely new solution because of time that will be required to have all sites up and running. That's why we started to think if it is possible to keep the old solution and add there MVC project which allows us to write new sites in MVC and slowly refactor the legacy code in the meantime.
I saw John West's post about using Web Forms and MVC in a single solution http://www.sitecore.net/learn/blogs/technical-blogs/john-west-sitecore-blog/posts/2012/06/using-web-forms-and-mvc-in-a-single-solution-with-the-sitecore-aspnet-cms.aspx but I need to be certain that it will not cause any problems in the long run, before we propose this solution to the customer.
Does anyone have experience with keeping both type of projects in a production application? Is it possible to do a migration sublayout by sublayout without any risk? Can we have in one time part of the site in web forms and part in MVC (of course with pages separation to only Web Forms or only MVC controls)? Do you know about any constraints that we should be aware of?
No problem to have MVC and Web Forms together in a Sitecore 8. but out of the box there is no support to mix MVC and Web Forms placeholder. So a page is MVC with MVC sublayout. or Web Forms with WebForms sublayouts.
There are solution to do mix that. But it is not advisable see https://github.com/HedgehogDevelopment/sitecore-mvc-aspx-interop
Web Forms on a MVC page:
http://www.chrisvandesteeg.nl/2014/02/11/usercontrol-renderings-in-a-sitecore-mvc-website-wffm-for-mvc/
A while back we had this subject on a SUGNL meetup you can read the summary on: http://sitecore.robhabraken.nl/index.php/2288/sugnl-colours-2015/
Or read this
http://www.nonlinearcreations.com/Digital/how-we-think/articles/2015/05/MVC-Web-Forms-Hybrid-Sitecore.aspx
It is indeed possible for Sitecore WebForms and MVC to co-exist within the same solution. It seems like you have two goals here though which should be treated separately. 1) the updgrade to Sitecore 8 from 6.5 which is not a small task and 2) conversion from WebForms to MVC.
Assuming a re-write is out of the question, I would start first with getting the solution upgraded to Sitecore 8 (or even better to 8.1). If your existing solution uses the DMS, then this will be a significant job in addition to the rest of the upgrade.
After you have a working WebForms solution upgraded to Sitecore 8 / 8.1 you could then think about changing parts of the solution to MVC. WebForms and MVC can happily co-exist within a project, the only limitation is that each page should be either 100% WebForms or 100% MVC. Creating an MVC version of the Layout would be the first task, followed by your components. It is possible that during your conversion process you could have duplicate markup but that should not be a major issue. If you are new to Sitecore MVC you will want to learn about the different rendering types available and know which to choose for what purpose (here is an introduction to Sitecore MVC presentation concepts and notes about moving to Sitecore MVC). If there are any forms in your solution, I would upgrade them last as they might require the biggest change when moving to MVC.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was looking in the Internet if there is any article about trends in ASP.NET. There are many such articles and each one gives their own suggestions.
Could you point some technologies that are commonly used building ASP website?
I'm interested in trends in:
standard websites
client-server apps using client basing on ASP (maybe bad idea?)
I want to find out about the technologies, useful libraries, etc.
Please, don't hate this thread, as far as I noticed (in posts/comments in the whole Web), many people that want to start learning e.g. ASP with most known and the best technologies (for this time) on their own have problems with finding clearly answer.
Specialists could share their experiences and tell something about technologies used in their companies/projects. Maybe, please, describe the kind of your app and used technologies. Thanks
If you read .NET Technology Guide for Business Applications by Microsoft press, you will have a better idea what options there are (mostly Microsoft stack). It all depends on your requirements, so you might want to think about them first.
For me personally, in a lot of cases I end up with ASP.NET MVC 5 (with bootstrap 3 for responsive design), web API 2 for the backend services, and deploy them to Azure.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I want to make web apps. Should I start with a ASP MVC books or first with C# books, due ASP MVC is written in this language.
Thank you.
Absolutely definitely and without any hesitation you should first learn the .NET framework by picking a CLS language such as C# or VB.NET before getting into ASP.NET MVC. Once you learn .NET, depending on your level of experience of web development in general you might start by learning the HTTP protocol and some markup such as HTML. I have seen many developers starting to work with ASP.NET MVC without knowing anything about the HTTP protocol which is at the base of every web application. Javascript comes next.
Once you are familiar with those concepts you could jump into ASP.NET MVC. At least that's the advice I can give you. If you have no experience with .NET and you start directly with ASP.NET MVC that would be very counter productive.
Yes, you should learn C# first. Especially if you have no prior programming language. If you already know an OO language, it might not be that important to study C# first, but I would definitely recommend you to read a book on it, or use tutorials and practice, before diving into MVC.
MVC is a framework. You write code for it in one of the .NET languages, such as C# or VB.NET. If you can't code C# at a basic level (or one of it's friends), MVC, the book and its examples, will make no sense to you.