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.
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 2 years ago.
Improve this question
So, near 6 months I learning Java. But now I'm got a good job vacancy on c#, .net. I'm very interested in this job. They know about that I'm learned java, so they gave me a test task. And I ask about help from one of the most powerful community in the world. Can somebody explain me what technology I must use for each concrete part, and maybe give me GitHub example for study, or explain mechanism of dialog between technology. Or make some analogy from java
I need to make database with tables, and web service for it, and HTML page for view. At first page will load all records from database, but second it will load only fresh records. And in this web form gone be some buttons for queries to database.
Technical requirements:
no asp.net web forms, it should be HTML
table should be made on tag and with CSS styles
logic for working with table, should be on javascript
calling web service on js too
web service can be asmx, rest, WCF
queries from buttons can be made by js or on web service by SQL or LINQ
The target technologies should be using the net core technologies.
You can use html with net core MVC https://learn.microsoft.com/en-us/aspnet/core/mvc/overview?view=aspnetcore-5.0
The ASP.NET Core MVC framework is a lightweight, open source, highly testable presentation framework optimized for use with ASP.NET Core.
ASP.NET Core MVC provides a patterns-based way to build dynamic websites that enables a clean separation of concerns. It gives you full control over markup, supports TDD-friendly development and uses the latest web standards.
This framework can also supply rest api connectivity that can be called from javascript.
You can also integrate with a framework like angular: https://medium.com/asp-net-and-angular/how-to-create-an-asp-net-mvc-5-project-with-angular-6-in-visual-studio-part-1-8b116e19a335
The ASP.NET Core MVC framework is a lightweight, open source, highly testable presentation framework optimized for use with ASP.NET Core.
ASP.NET Core MVC provides a patterns-based way to build dynamic websites that enables a clean separation of concerns. It gives you full control over markup, supports TDD-friendly development and uses the latest web standards.
For database connectivity, you can use entity framework core, for simple crud applications.
Dapper is also a good idea if you want to write your own queries.
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.
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 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 9 years ago.
Improve this question
I'm about to do a project on financial data visualization. Nothing advanced really, just some user input manipulated and visualized as an output with some charts and numbers. The thing is though, that even though the plan is to have it as a .NET desktop application to begin with an idea is to later transform it into a web based application. And since I've got no experience with that whatsoever my question is simply: Can one write a desktop application in C# .NET and later "upload" or "convert" it into a web based interface without too much work?
I've heard of ASP.NET that seems to be a pretty well used framework for web applications, but I cannot find anything about converting a desktop application into ASP.NET application.
Thanks in advance!
IF you divide your application into parts as you should - e.g. business logic, data access layer etc (into different dlls preferably), then all you need to do is just create a new UI, which isn't as bad as creating the app from scratch...
There is obviously a confusion in definitions. You (and it seems some of the guys that posted their answers here) have probably misunderstood the technology.
You can't compare ASP.NET to C#, because one is a web framework, the other is a programming language. ASP.NET can and does use C# (or VB.NET or other .NET language). ASP.NET can then be divided to MVC and Webforms. If you want to compare it to something, you should compare it to windows frameworks like WPF and Winforms.
That said, if the two apps have the same functionality, the logic and the C# stays basically the same. The only thing that changes is the framework that's used for the UI. That's why I'm talking about dividing the app into subprojects, which you can then reuse as needed.
As far as I got your question, there is no way to convert a .Net Desktop Application to a web application. you will need to re-write it. sorry buddy.
Unfortunately not.
When you start developing your Application for Desktop (for example with Windows Forms) the differences to a Web Application are too big too automatically convert.
I suggest to make a web Application from the beginning.
MfG Mike
I think there are service/companies/utilities that do do that, but you don't hear a lot about them, prob because they are not great. I don't know of other technology families that do that better either.
If the eventual goal is a website, prob just start with the website and forget the desktop. Slower to develop and more to be aware about to be secure are the other downsides.
the downvotes are prob about the question already being asked. If you google "stackoverflow: C# desktop to website conversion", here are three posts that are similar, in descending order of informativeness.
Converting ASP.NET Web Forms application into Desktop Application
Can I convert from C# to asp.Net to host application online?
How to Convert C# Desktop Application Project to website