-
The main reason why not all Transaction Scope isolation levels are listed is to maintain compatibility with the same constructs in Enterprise Service portal. There is indeed application level override for isolation level. Just add the following to your config file < add key = " CslaDefaultTransactionIsolationLevel " value = " ReadCommitted
-
You may also look at distributed in memory caching system such as App Fabric for this because you get good performance and redundancy combination out of this type of solution without putting extra pressure on your DB server. Also, you always want to have a back up plan if cached data is not found and fetch it again if so.
-
It is important to evaluate what you are trying to achieve with compression. On a typical LAN with 100 GB cards my vote would be not to use compression. It has overhead in terms of CPU and memory usage. My suggestion would be to analyze your code and see where the bottleneck is. New communication protocol is both faster and more memory efficient than
-
Essentially your client and server must match, so you need to use the same bindingConfiguration element on both sides, and does not look like you do.
-
Make sure server and client settings match. Set security mode=Transport on both sides.
-
You can then probably just setup multiple start up projects, then you can just hit F5.
-
The unfortunate part about MEF is that it is not thread safe. The second parameter you specify still does not make it completely thread safe either, and if I remember correctly, documentation indeed says that You have to wrap all calls to create a container and compose parts inside lock{}. I ran into this issue about a year ago. I believe the main problem
-
You can comment out the attribute, and just create transaction scope in code so that you can set desired timeout. However, I think you need to change the app so that you do not have to insert that much data from the client. You would be better off using SP to create the data on the server. Calling insert 1000000 repeatedly will never be fast. My 2 cents
-
I do not believe this will work at all. You cannot pass open connection to the context. I belive that your only option is distributed transactions.
-
In addition to what Rocky says, you might want to consider getting away from root list and instead have just one building as the root with a search screen to allow users to select a single building. YOu have to be carefull with EF when populating 2500 objects in a single swoop. I would get aways from lazy loading as this may results in excessive number