![]() In the meanwhile, take a look (not the final look & feel): ![]() I consider it a good proof of concept, but I am going to spend some of next week trying to figure out a less invasive approach. Unfortunately, the current way of intercepting EF traffic is extremely invasive, and I don’t really like it. Initial testing also shows that I’ll be able to provide much more information about EF than I’ll be able to do with Linq to SQL. Some drinks later, we had a working version of EF Prof that was actually able to intercept all queries coming from the Entity Framework. This is what I do, more or less, so we decided to tackle that problem in the bar. ![]() ![]() It appears that there is much need for that. I was sitting with Julie Lerman today, and we got into a discussion on how to provide more information to EF users. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |