Designer is very slow to open (or hangs) in active directory environment

DinG · Post by **DinG** » Thu Apr 23, 2009 10:35 am

Our application is deployed from a web server, and all assemblies are signed to enable them to have trusted access to local resources. The users work in an Active Directory environment with roaming profiles. When they try to launch the Designer from within the application, it takes a long time (several minutes and sometimes never) to open. There is no problem launching in standalone PCs outside their network - it takes 30 - 40 secs the first time, and 4-6 secs afterwards.

Has anyone come across this problem before - it is a bit of a show-stopper for our users!

I wonder whether there may be issues with accessing the Local Settings directory which is within the roaming profile? Are there any security settings that need to be adjusted?

DinG · Post by **DinG** » Mon Apr 27, 2009 7:22 am

I should add that after the Designer eventually opens (after several minutes), each operation (e.g. removing a field) takes a long time (one or two mintues).

I've just discovered that in recompiling the code under .Net 1.1 (which I needed to do in order to strongly name the assemblies) I did not set the conditional compilation constant for Net11. Is this likely to have anything to do with my problem?

Post by **Jan** » Sat May 02, 2009 5:06 pm

Hello,

At this moment we don't have any additional information which can help you. This problem occurs on one specific computer or on any computer?

Thank you.