Which design pattern is typically used when designing a WCF data services driven Winforms application?
Please excuse me as I am a bit new to the following technologies and practices. I have been given the task to create a management suite utilizing an MDI GUI. This suite will be the front end to a WCF data service. My question is, what design pattern is typically used by most professionals when designing such an application. At the moment, I have been looking into both MVC and 3-tier design patterns.
Which design pattern is typically used when designing a WCF data services driven Winforms application?
Please excuse me as I am a bit new to the following technologies and practices. I have been given the task to create a management suite utilizing an MDI GUI. This suite will be the front end to a WCF data service. My question is, what design pattern is typically used by most professionals when designing such an application. At the moment, I have been looking into both MVC and 3-tier design patterns.
Interfaces, Adapters, exposing business objects via WCF design
I know there have been countless discussions about this but I think this question is slightly different and may perhaps prompt a heated discussion (lets keep it friendly).
How do I reduce the number of WCF config files in a SOA?
After embracing the whole SOA thing, I’ve found that I’m gradually drowning in a sea of web.config and app.config files.
How do I reduce the number of WCF config files in a SOA?
After embracing the whole SOA thing, I’ve found that I’m gradually drowning in a sea of web.config and app.config files.
Minimizing data sent over a webservice call on expensive connection
I am working on a system that has many remote laptops all connected to the internet through cellular data connections.
Minimizing data sent over a webservice call on expensive connection
I am working on a system that has many remote laptops all connected to the internet through cellular data connections.
Minimizing data sent over a webservice call on expensive connection
I am working on a system that has many remote laptops all connected to the internet through cellular data connections.
Is Moving Entity Framework objects over a webservice really the best way?
I’ve inherited a .NET project that has close to 2 thousand clients out in the field that need to push data periodically up to a central repository. The clients wake up and attempt to push the data up via a series of WCF webservices where they are passing each entity framework entity as parameter. Once the service receives this object, it preforms some business logic on the data, and then turns around and sticks it in it’s own database that mirrors the database on the client machines.
Is Moving Entity Framework objects over a webservice really the best way?
I’ve inherited a .NET project that has close to 2 thousand clients out in the field that need to push data periodically up to a central repository. The clients wake up and attempt to push the data up via a series of WCF webservices where they are passing each entity framework entity as parameter. Once the service receives this object, it preforms some business logic on the data, and then turns around and sticks it in it’s own database that mirrors the database on the client machines.