This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
When run under VisualStudio, code:
runs much slower then, when run without VisualStudio. I've attached a sample program where you can check this - code is simple, create n entities, add them to table, and then measure time needed to get them all with uow.Query I did some measurements, here are results:
Can we do something about this? Our developers run program under VisualStudio, and this behaviour causes great productivity losses. |
|
|
Thanks for sending through the repro, it looks like we can improve this so Ill push up a change for tonights nightly build that should remove the problem in this case. Whats going on here though is just the difference in behaviour when running under a debugging environment where Visual Studio "handles" first chance exception events (even if the exception is actually handled by the underlying code) and gives you an opportunity to pause execution and inspect the stack etc, so there is processing involved in making that information available which represents the difference in time when running natively. In this particular scenario there is an exception being generated which is handled that stems from the Guid values being returned as strings (due to the BindAllAsText option) in the DataReader leading to an exception being raised from our expectation of them being Guids prior to falling back to another method of handling them. Ive added some additional checks which will avoid the exception in this case.
|
|
|
This fix helped a lot. Thank You. |
|