> No, result is the same (like .CP.4 project).
I would try the following:
* Make sure you're only referencing BLToolkit.Data.4.dll (and not
other BLT assembly)
* Make sure you're referencing the "release" assembly (not debug)
* Try to NGEN BLToolkit.Data.4.dll on the server
* Download Resharper and run a "optimize assemblies" on your
references (if you've never done this it can remove quite a few
assemblies that are not needed)
* Configure your application pool (IIS) to not shut down / recycled.
This way the pool is not shut down and you won't have the warm up.
This would work for sure, but may not be possible in a shared
environment.
If none of these make a difference my guess would be that further
optimization would require the attention of somebody who knows the
internals of BLT.
Good luck.