n-layer

Is the dependency injection a cross-cutting concern?

由 风流意气都作罢 提交于 2020-01-15 11:48:11
问题 I am designing an app and I am using a n-layer architecture, I have: - a presentation layer - a domain bussines layer - a data acccess layer - a cross-cutting layer Then I am trying to isolate my project from an specific DI framework, that is create my own IContainer interface and ensure that my components depends only to this interface. Then I have 2 questions. 1 - Is this last a good practice ? 2 - (And the more important) Is dependency injection a cross-cutting concern ? That is can I

MVC or MVP architecture for winform applications using Entity Framework as ORM

由 风格不统一 提交于 2020-01-12 04:02:33
问题 I am going to develop a winform project of considerable size. I am planning to use Entity Framework as ORM tool. Now I am searching for an architecture(MVC/MVP/MVVM etc..) to implement all these. Firstly there are few choices for n-layered architecture for windows forms and most those I get are written prior to EF came into market. I got a framework called Rocket Framework from codeplex(http://rocketframework.codeplex.com) I have looked around it but am skeptical that it will accommodate a

C# NAudio rendering a waveform ASP.net without DMO or ACM

由 一笑奈何 提交于 2019-12-25 07:28:48
问题 I'm trying to draw out a waveform using ASP.net on an Azure Website (which doesn't have the ACM or DMO codecs installed), so I had to use NLayer to read the mp3 file. The code I have below works perfectly with the regular DmoMp3FrameDecompressor, but when I use the NLayer decompressor it doesn't. Maybe the format of the NLayer decompressor is 32bit Float and not 16bit PCM. byte[] data = new WebClient().DownloadData(URL); int maxAmplitude = 0; short[,] dataArray = new short[Width, 2]; //using

Azure Key Vault Connection Strings and N-Layered Design

由 我的未来我决定 提交于 2019-12-24 18:59:37
问题 This question relates to the following post which maybe helpful: Azure DevOps CI/CD and Separating Connection Strings from Source Control I'm currently working on an N-Layered project based off of an article by Imar Spaanjaars named ASP.NET N-Layered Applications I'm trying to implement Azure Key Vault to, I guess you can say, abstract secrets from the application itself. Goal I want implement Azure Key Vault using this N-Tier concept. I have a sample project located at NLayer-Spaanjaars

What format is data in when passed to a domain layer for validations

由 五迷三道 提交于 2019-12-23 04:55:20
问题 I am confused about what form data is supposed to be in when passing data from a User Interface in the Presentation Layer to an Application Layer then the Domain Layer for validations. I am passing in a DTO but I've heard I should not. Rather that I should only pass in primitives and scalars to the Domain Layer. I'm not sure how this is done if not using a DTO class structure. Below is how I am using a DTO from my UI: My User Interface may have values as follows on screen: Product Name:

What are the benefits of an N-layered architecture?

由 ◇◆丶佛笑我妖孽 提交于 2019-12-12 20:37:43
问题 What are the benefits of an N-layered architecture? How does that make an application better? 回答1: From here: Other applications will be able to reuse the functionality exposed by your layers. You will be able to distribute your layers over multiple physical tiers. This can make a very good impact on your application by improving performance (sometimes), scalability and fault tolerance. The maintenance of your application is easier because of the low coupling between layers. Adding more

n-layered architecture - BLL, DAL and interfaces. What is best practice?

由 谁说胖子不能爱 提交于 2019-12-09 22:02:59
问题 I have a question regarding n-layer architecture. I thought long and hard before asking this question as there's a lot of similar questions here already... however, after literally a day and a half looking at it and reading these other answers I'm still unsure. The variety of seemingly similar terminology and different approaches has me confused. If I had a BLL and a DAL in different class libraries, one way to communicate between the BLL and DAL would be to utilise an interface, kind of like

.NET N-Tier Architecture: What do I do about the Model objects?

由 岁酱吖の 提交于 2019-12-08 16:29:14
问题 I am creating a solution from scratch, using ASP.NET Web forms C#. I am concerned about the model objects as I don't want to create duplicate sets of model objects in each layer. What is the best practice for using Model objects in 3 layer architecture in Web Forms ? The structure I have in mind is as follows: UI BLL DAL Model The Model will contain all the model classes that can be used in each section of the layers. I thought this would be useful as each layer needs access to the model

n-layered architecture - BLL, DAL and interfaces. What is best practice?

由 耗尽温柔 提交于 2019-12-04 16:33:20
I have a question regarding n-layer architecture. I thought long and hard before asking this question as there's a lot of similar questions here already... however, after literally a day and a half looking at it and reading these other answers I'm still unsure. The variety of seemingly similar terminology and different approaches has me confused. If I had a BLL and a DAL in different class libraries, one way to communicate between the BLL and DAL would be to utilise an interface, kind of like a DTO defined in another separate DLL that was referenced by both BLL and DAL. My domain model

In which layer should Specification Pattern objects be “new'ed up”?

由 元气小坏坏 提交于 2019-12-04 11:41:25
问题 So, I've looked at some posts about the Specification Pattern here, and haven't found an answer to this one yet. My question is, in an n-layered architecture, where exactly should me Specifications get "newed" up? I could put them in my Service Layer (aka, Application layer it's sometimes called... basically, something an .aspx code-behind would talk to), but I feel like by doing that, I'm letting business rules leak out of the Domain. If the Domain objects are accessed some other way
订阅 n-layer