Re: Odd behavior/Hang with CFileDialog in vista.

I have a bug I'm tracking down that only occurs in vista.

The behavior is slightly different on Vista 64 and Vista 32.

The code instantiates a CFileDialog object via CFileDialog openDlg(...)

We initialize the dialog then use roughly the following loop

do
{ // Repeat until user either cancels or chooses an existing file
   bResult = false;

   if (openDlg.DoModal() == IDOK)
   { // User has selected a file and pressed OK
    outSelectedFile->Assign(openDlg.GetPathName(), NULL); // get the file name
    bResult = true;
    }
}
while (bResult && !outSelectedFile->OSIsFileExists());

Now the bug comes when the user types random letters(or anything that isn't
an actual file in the directory). Then hits OK

On XP, things work fine, we will find that we don't have a real file name so
go back and hit DoModal() again till we do have a valid file or they hit
cancel.

On Vista 64, debug mode asserts inside dlgfile.cpp

hr = (static_cast<IFileDialog*>(m_pIFileDialog))->SetFileTypes(nFilterCount,
pFilter);

can continue from this assert and will get a dialog up saying params invalid
(CFileDialog has goneaway)

Release mode no assert, just dialog.

But on Vista 32 we hang and eventually system asks if we want to close a non
responding app.

I could turn off vista dialog type but hate to do this.

It seems doModal is having issues setting up stuff on vista the second time
through.

One option I suppose would be to have *Dialog = new CFileDialog (...)
instead of having a local version, and delete and create it each time through
but this seems heavy handed.

Is it ok/correct to have this kind of a loop and recall DoModal on the
CFileDialog?