smcsmc1
asked on
Windows Entity Framework WCF and WPF
I am a newbie to all of the above topics although I have been studying about all three.
My problem is that I have inherited an application that makes use of Sql server, Entity Framework, WCF and my peers have determined that, based on what we are looking to accomplish and the way the application exists currently (it is unacceptably slow, I believe due to the fact that the author of the code was a newbie as well when he developed.
Our conclusion at work is that he "taught himself" about all of the above technologies that were used on our dime and the result is like a bowl of spaghetti to those of us trying to re-engineer it.
We have decided that using WCF for this application was like using an elephant gun on mosquito.
This "question" may be too big of a topic for this forum but I figured it could not hurt.
I have two dlls and an executable. The first .dll has knowledge of the database and the second is the WCF service that pumps the data out in requests sent to it via the WPF application and its control bindings to the WCF service.
I want to functionally remove WCF from the picture and plug the GUI and its controls and other items directly into a single Entity Framework .dll.
As I said, this may be too big of a question but perhaps I could get back insights on one or more of the questions I ask.
The application is small and has virtually no throughput requirements. 95% of the time ther is only one user entering data via the WPF gui. The number of forms is small (10 or so).
As I said, question may be too large but thanks in advance for any possible feedback.
My problem is that I have inherited an application that makes use of Sql server, Entity Framework, WCF and my peers have determined that, based on what we are looking to accomplish and the way the application exists currently (it is unacceptably slow, I believe due to the fact that the author of the code was a newbie as well when he developed.
Our conclusion at work is that he "taught himself" about all of the above technologies that were used on our dime and the result is like a bowl of spaghetti to those of us trying to re-engineer it.
We have decided that using WCF for this application was like using an elephant gun on mosquito.
This "question" may be too big of a topic for this forum but I figured it could not hurt.
I have two dlls and an executable. The first .dll has knowledge of the database and the second is the WCF service that pumps the data out in requests sent to it via the WPF application and its control bindings to the WCF service.
I want to functionally remove WCF from the picture and plug the GUI and its controls and other items directly into a single Entity Framework .dll.
As I said, this may be too big of a question but perhaps I could get back insights on one or more of the questions I ask.
The application is small and has virtually no throughput requirements. 95% of the time ther is only one user entering data via the WPF gui. The number of forms is small (10 or so).
As I said, question may be too large but thanks in advance for any possible feedback.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.