I'm not sure if it is EF or DevForce behavior (I assume it is EF) but would like to know if I can stop it.
I'm sharing same model on server between my Silverlight project and using it on server for WCF services. In case of services - all calls are in and out and have very small scope..
Here is example picture of what I see in Profiler:
Basically, I persist my entities and EF automatically refereshes it's state - loading keys, etc.
But I KNOW that this is my last call and service will exit after that. How can I control if it's even possible so EF doesn't refresh itself and doesn't issue those additional selects against database? Trying to optimize as much as I can