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 have an Asp.net MVC project that includes three management systems:
1.Car rental system
2.Bus ticketing system
3.Home delivery system
Each system should have different types of modules and each module deserves an area of its own.How should i manage the project. Should I create three different projects for
car rental,bus ticketing, home delivery system and create nested area to manage their own modules.I also want to maintain generic repository pattern,unit testing.
For asp.net MVC you can create one core MVC project that include (add reference) in other project that project contain your Car, Bus and Home areas.
You can create a main web project for your application with three areas for three modules.
And you can create three class libraries for three different businesses.
So, if you need to change any business logic, you just go to the particular dll and made changes. (ex. go to MyWebApp.Service.Car and update and compile the dll and update this dll to your production site to update the business logic for the car rental system)
Please feel free to ask any doubts on this...
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 5 years ago.
Improve this question
I want to working on the Single Page Application Based on .Net Core 2.0 with AngularJS for front-end. We have request that the application must be modular, which means that we must separate Back-end and front-end for each modules. We have been trying to find best approach for the project.
We try to use ASP.NET Boilerplate - Application Framework for this approach but i don't know how to support static files such as html and JavaScript files for angular per modules and We cannot configured Main Web-app to lookup static files in different location (modules must separate with project files).
I cannot find examples for this case (Modular App Based on .NET core and WebAPI and AngularJS,Typescript ...). Do anybody have suggestion how can we solve this problem, or do you suggest another approach or framework or sample code.
Note: The main problem is add routing With angularJS in Modules when modules are load in Main application start up Event.
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 5 years ago.
Improve this question
I have been reading about using azure for asp.net solutions and I am sold. I have questions about a ton of stuff but I would like to know how to scale a layered application. I read in a book that we could for performance and scaling sake we can have our models, business logic and DbContext in a separate project and that this project can be on a separate server. So I guess my question is can a .NET class library be hosted in IIS? how would doing this scale and give me an advantage. Sorry I am an advanced beginner so you will need to bear with me. Thanks
You can't host just a class library technically.
Having them in a separate project is not done for scaling reasons. It's done so you can reuse the models in unit tests etc.
One thing you can do of course is to create an API project, which will be hosted in e.g. Azure App Service. Then you can build an MVC project that then uses this API through HttpClient and the like. This separates your front-end and back-end allowing both apps to scale independently depending on their load. This would of course require them to be in separate App Service Plans in Azure as otherwise they share the server instances. The plan can be changed later though, so you can move them to a separate plan later and start with a common one for now.
If you want to break down your app into even smaller pieces, I would advise looking into microservices architecture.
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
If I have to develop large system using ASP.NET with multi modules. What is the best practice of designing it? Is it be divide the modules to folders in the same web project or divide them to separated web projects in the same solution?
In a project containing more than 500 aspx pages, we used a single web project, a data connection layer project, a dataaccess project and a business layer project.
The web project is divided into multiple folders also containing sub folders.
The result is a very fast running asp.net project. Also, opening the project in Visual Studio takes only a few seconds.
Project, Folders, Solution Folders and even Solutions (where necessary) can be used to divide large system into readable, easy to understand logical blocks.
Dividing it into folders is better as it would maintain the simplicity of your project.
less references is proportional to faster loading time.
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 8 years ago.
Improve this question
I have created an MVC5 project with a template registration, now there has emerged a need to register users in a desktop application. (i.e. a manager uses a desktop application to add info about personal, and while doing that he creates user accounts for the web site). What is a good approach to do that?
If you must make a desktop app, I would suggest that your desktop app calls to your website to do maintenance via a web service. This will be much easier to maintain. You can do this with either WCF or WebApi.
I would suggest you to avoid desktop applications. Its difficult to maintain compared to web projects.
You can use only one database and point your two projects to that database or you can use two projects and use replication.
Have these three projects in your solution:
PublicWeb (with MVC5)
AdminWeb (with MVC5)
DataAccess (This project will only contain C# methods and will call SQL stored procedures to update tables. I would suggest you to create your database objects (tables and stored procedures) before creating the data access classes and methods.
If you don't want to use DataAccess methods is you can use an Object Relational Mapper software (i.e. NHibernate, Entity Framework or myGrandmasFalseTeeth)
Project should be different if by expected number of visitors are high (like million visitors in a week). In that case you can use NoSql database with Angular JS.
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 9 years ago.
Improve this question
I am starting a project in asp.net. I want to use 3 layer architecture. now I have problem with layers. I manage these layers like this:
but I have seen somewhere that uses App_Code and some other formats. could you please help me which one is true and standard?
App_Code is a special ASP.NET folder which is used by ASP.NET Websites. It is not used by precompiled ASP.NET applications. You can read more about the differences between the two in this article. So if UI is an ASP.NET Website you could use the App_Code folder to put some logic although this is better suited to external libraries as you have in your current design. This allows for better unit testability of this code and reusability.
Avoid the use of App_Code. Anything you put in here doesn't compile until the site is executed. Any dependency that your forms and user controls have is best put into your UI layer, outside of the main web folder. You'll have a lot more peace with objects that are compiled early rather than later.
Now-a-days I see this standard a lot:
ProjectName
-ProjectName.Core (All poco classes and interfaces)
-ProjectName.Data (All entity framework stuff)
-ProjectName.Service (All business logic)
-ProjectName.Web (All font end logic)
"Core" is reference in all projects to move data around.
"Data" is referenced only in "Service".
"Service" is referenced only in "Web".