Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to use Entity Framework(with Self Track Entities) in my winform application; but i could not find any example of STE(Self Track Entities) with winform. Can someone tell if it’s not recommended to use with winform?
As far as I know the use of STE is to track the changes being made and it requires little code for doing insert/update/delete. So, would it be a good idea to use it with that thought in mind?
The main purpose of STEs is that they can track changes when they are detached. They are mostly recommended in scenarios where your entity must cross physical boundary (like web services) so it needs to track changes when deserialized in another process and transport these tracked information back to original process.
Is it your scenario? If you don’t have any process boundary between loading the entity and showing it in WinForm you don’t need STEs. WinForm application is connected stateful scenario so you can use common attached entities and life context will track all changes for you (and it will do it much better than STEs).