[Wixedit-devel] [ wixedit-Bugs-3571266 ] Import Folder Button Lags the Program Out

[SourceForge.net <no...@so...>]

Bugs item #3571266, was opened at 2012-09-24 10:09
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=726876&aid=3571266&group_id=133314

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Import Folder Button Lags the Program Out

Initial Comment:
The import Folder button in the new project wizard completely lags out the entire program and causes it to be entirely unresponsive for at least ten minutes under the situation outlined later. After doing some debugging in Visual Studio using the provided source code I found the lag was caused by several mapped network drives that contain several terabytes of data shared across 4 separate drives. The Folder dialog then displayed and worked perfectly importing folders as expected.

The following are the steps I used to get the lag. Please note there were nearly several terabytes of data shared across network drives.
1. Open wixedit v0.7.5.
2. Go to file and press new.
3. Press next on the wizard window that appears.
4. Press Import directory.
5. This is the point at which the WizardForm lagged out for 15-20 minutes while doing several Directory.GetSubDirectorie() calls in FolderSelectDialog.cs (see attached image).
6. I imported a small directory containing some small images and they were all added to the *.wxs file that I later saved. The 

I expected the appearance of the wizard would follow within seconds of pressing Import folder button then Sub directories would be loaded as needed. Or I expected to see the default .NET 2 folder browser dialog. Instead I saw a non-responsive screen that I thought at first was caused by an infinite loop bug in the software.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=726876&aid=3571266&group_id=133314