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.
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
When ASP.NET MVC came, Microsoft announced many times in many places that it wasn't supposed to replace ASP.NET Web Forms. In other words, it's just another technology that you might find useful, or you might use Web Forms in other scenarios.
However, as companies enter into the market, they can't have a jungle of technologies, because that's too expensive. They usually select a mature technology, stick to it, build on it and extend it and reuse elements in it to reduce costs.
Now we're trying to decide to move to Owin/Katana from Web API. We just wonder if it's OK that we move 100% to Owin?
The reason I'm asking this question is because we've created a very rich codebase for Web API, including streaming, compression, authentication, normalization of UGC, support of I18N & L10N, and more.
If we want to move to Owin, we need to re-create these facilities/utilities again for Owin, because its architecture is different from Web API.
We want to move to Owin, because it's faster, lighter, self-hosted server, and seems to be the future of service technologies from Microsoft.
Is it safe for us to move to Owin completely and imagine a future in which all of our services are delivered through Owin, and we discontinue using Web API?
OWIN is just a specification, nothing more. It describes a common interface that servers and applications can both use, so that applications don't need to be tightly coupled to servers.
Katana was the first step towards decoupling ASP.NET from IIS. Work on Katana has stopped now, according to the official roadmap. The ideas and technologies developed for Katana have made their way into the next version of ASP.NET (ASP.NET Core).
It rarely makes sense to build applications on top of OWIN itself, because you're operating at the lowest level of abstraction above HTTP (literally dealing with raw requests and responses). That's usually only necessary if you are building middleware components that need low-level access.
In other words: you shouldn't rebuild your application on OWIN, because you'd be spending a lot of time reinventing all of the stuff already in ASP.NET.
ASP.NET Core is the next evolution of ASP.NET and Web API. It has all the things you mentioned: it's fast, lightweight, and can self-host. If you need to rebuild your architecture, do it on ASP.NET Core.
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 7 years ago.
Improve this question
I'm starting to learn C# and I'm confused as to what the difference is between C# and ASP.
From what I've learned, ASP .Net is most likely a server-side web development framework that can be used in C# code while .Net, on the other hand, is like a library of classes built in C#. However, where is the MVC from? How can I learn MVC using C#?
The first concept to get is .NET which is a framework at the base of all the things you are asking about. It has libraries and functions that can be used when programming.
The .NET framework can be developed with using a number of different languages. C# is one of these languages, there are a number of others.
ASP.NET is a set of .NET libraries that have tools for developing rich web applications. An ASP.NET application will be deployed in a web server, usually IIS, but it can use all of .NET behind it. It can be programmed using any language available for .NET, including C#.
A .NET MVC applciation is an ASP.NET application, using the MVC design pattern and the special MVC tools provided in ASP.NET.
C# is a language.
ASP.NET is a framework that uses various compiled languages (C# or VB.NET) as well as markup languages (the default ASP.NET one, or Razor, or whatever else you plug into it). It's a bridge between your application and IIS.
And ASP.NET MVC is a set of libraries for ASP.NET, in particular giving a new markup language (Razor) and various IIS pipeline components (the URL rewriter, the various mechanisms to bind arguments to actions etc).
C# is a language. That language is a .net language (it uses the .net framework, compiles to CLR bytecode, etc.). Other .net languages also exist - most notably VB.net, but there are others as well.
ASP.net (that is, "classic" ASP.net, also often referred to as "WebForms") is a web development framework for use with the .net framework. You can write ASP.net code in C#; you can also write ASP.net code in VB.net or other .net languages. ASP.net MVC is a different web development framework also for use with the .net framework - you can also write MVC code in C# or VB.net, and so on.
MVC is just a design pattern that can be applied to any software design with a user interface.
M -- Model -- This layer contains the data used by your application
V-- View -- This is the actual user interface
C -- Controller -- This layer governs the interaction between the model and
the view.
you can read more here:
MVC