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 4 years ago.
Improve this question
I want to create a modular architecture in MVC 6, with several interchangeable modules. Mostly for separation of concerns on grand scale, some modules will be "base modules" (always included). But all should have the same level of decoupling. Now that we have DI and IOC builtin the architecture of this might differ vastly.
I have looked around all over SO and only found MVC 4/5 and MEF solutions, but seeing as the new Startup.cs has changed considerably, and added new methods and best practices, i was wondering if there was a new way to do this.
I did however find the aspnet/Entropy project on GitHub, and they have Mvc.Modules package, which might do the trick although this might not be an official thing anytime soon.
EDIT:
It seems that the Mvc.Modules mentioned above isn't completely separated yet (controllers specifically), so it only half does the job.
Since MVC 6 is currently under development, it might be a better idea to look at the source code (especially the tests) to find features that you want to use when you cannot locate what you need on the Internet.
MVC 6 has support for DI of both Controllers and Views. Here are the tests for Controllers and Views.
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 9 months ago.
Improve this question
I'm new to Slickflow. What is the use of Slickflow in Dot net core and how to use it? Is it an API or MVC Project or something other?
Edit:-
How can I implement Slickflow in my project? Give an example like see Users flow or anything you want. I'm considering which classes and how to do make a diagram?
If you are talking about this SlickFlow. It looks like a .NET, .NET CORE Open Source Workflow Engine with this GitHub repo. Here is their Quick Start Tutorial as well as some SlickFlow Application Code Example with complete C# code.
There are two articles from code project:
Slickflow NETCore Open Source Workflow Engine
Slickflow Coding Graphic Model User Manual
I am one contributor from slickflow team, if someone has any questions, we can do any help here. Thanks
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 7 years ago.
Improve this question
I am working on a asp.net mvc project. Also I want to use n-layer solution structure. So, I am using the following structure for my solution. It shows specially the part of the solution I have doubts with. I am planing to create interfaces for each entity I need in order to not repeating code and not have problems when passing data (lists or objects) from dal to presentation. What do you think? Is that a good approach?
[
I think you're missing the point of what MVC is. It effectively handles your layers. Using a BAL and DAL is N tier application. If you were using a real MVC project these layers are meaningless.
It's better to work with Generic repository pattern. LINK
You should create a Domain layer which will be the core of your project, in there you put your entities, your interfaces for entities, repositories and services, and this layer do not references any other layer. It makes your architecture more flexible, for example, if you work with NHibernate, but needs to change to EF, you just create a Class Library, and implements the repository interfaces that is in Domain layer, and the other layers not need any change.
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 8 years ago.
Improve this question
I would like to learn about how to allow third party code integration (module development) with standard ASP.net WebForms Application as well MVC applications.
What should be taken care of when developing an ASP.net Web Application to be able to integrate custom modules?
What are the standard practices and general approach for this?
Edit:
By custom modules, it could mean something like components in Joomla CMS.
Your question is too generic to provide a meaningful reply, but modules in most cases are encapsulated in an external class, which is referenced and registered in the web application.
If you want to be able to include new modules at runtime, you can take a look at MEF and use that. Otherwise, it would be just mostly designing your application so that it can instantiate classes from external assemblies.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I find the way of "having controller/view in same project, all model in separate class library" not intuitive to me. I prefer to have it vertically, i.e. having related controllers/views/view model in separate projects.
So I look up the internet and find that some (not many) people are using the area feature, but I find it a pain when it comes to do routing.
So why can't I put controller/views/view models as separate projects instead of area? Am I not able to do that or does that decrease performance so nobody uses it?
You can structure the solution however you want. Everything is configurable to work the way you want. Furthermore, the way you structure your solution should have no effect on performance.
It's going to be much more straightforward to structure the solution the idiomatic, default way. Other users of MVC are already familiar with the default way, which makes for easy collaboration. Even if you feel another structure is better - even if it is better - you're still going to greatly benefit from tolerating the default structure.
You actually can move the views model and controllers to the other projects.
It is not something available out of the box.
You would need to create your own implementation of few MVC infrastructure classes like: ViewEngine, controller factory and etc. I wouldn't recommend going this way as you would have really hard time migrating your project to new versions of ASP.NET MVC and the classes which Microsoft supplies are well tested and optimized.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am in the need of looking for a .net shopping cart, I am a .net developer not PHP and I need that the shopping cart solution be extendible.
In the past I have used Magento, and its probably the best solution out there, but I dont want just to learn another programming language.
Is there any as good as magento but done in .NET??
Some requirements I need:
MultiStore in one single database.
Ability to create themes.
Complex shopping cart discount rules as in Magento
As far as I know, there are only two written in .NET, and one of them is geared towards MVC.
ASP.NET MVC
http://merchanttribe.com/
http://www.nopcommerce.com - Version 3.0 and above is now MVC
ASP.NET
http://www.nopcommerce.com/ - Version 2.9 and below is web forms
dashcommerce http://dashcommerce.org/ is also a good option
has evolved from the old Commerce Starter Kit
Another one is OpenNetCommerce from which dashCommerce derived and went commercial. nopCommerce haven't tested lately, but it used to have issues with the speed.