Creating a client-server architecture in C # [closed]

Question

Creating a client-server architecture in C # [closed]

Navigation

#1 by (1 votes)

1

I made a N-tier test application (database access, presentation, business model, and transfer objects) worked quietly and I learned a lot about 3 layers and N layers.

Now I want to make a program that is client-server and I have these doubts:

When we talk about server, the business layer of the system stays all on the server or on the client as well, since I reference the business DLL in the presentation application?
If the business layer is whole on the server, how do I access it on the client?

If I also want to separate the database access layer, can I keep the connection to the database persistent? My idea is to build an application that I have the ability to set up any database using ODBC.

c# .net cliente-servidor services

asked by anonymous 05.07.2018 / 01:33

1 answer

footer "fixed" at the bottom of the page, but after the content I am not able to complete the merge this error always appears:

score 1 · Answer 1

When we talk about server the system business layer gets all server or client as well, since I reference the business DLL in the presentation application?

It depends. This may indicate that you did not do the layers as well. One part is on the client, one part is on the server and one part is on both.

If the business layer is whole on the server, how do I get access to it on the client?

I do not know if I understand, but it does not do anything special, just communicate the way you decided to do between the client and the server, establish criteria. Difficult to respond in an abstract way, it has an absurd amount of doing this.

For the server also work as a service, can I just make an application console and ask to install or do I have to develop it as an application service?

Basically this is, see . But you can use a template that comes with everything set up to make it easier:

More .

If I also want to separate the database access layer, can I keep the connection to the database persistent? My idea is to build an application that I have the ability to set up any database using ODBC.

Yes, but generally is not necessary, almost always this lot of layer, generalization is idealism and cake recipe that does not bring real advantage, on the contrary. Now it would be nice to learn to do simpler things that seem to be getting harder nowadays. When more complexity puts in the more experienced application needs to be, more accurate than team, more trouble arranges. There are cases you need, but they are rare.