The given key problem was the way you had your connection strings setup, at least in the sample you gave me.  That is why I mentioned that your use of the SetConnections() method was not correct.  Just to see if this is your problem, hard code the connection string and do not call the SetConnections method....from the AppMain or anywhere else.

Ok. Great! That fixed those problems.  Everything works in design time again. i deleted the browsedialog and re-created it and STILL got that "given key" problem... what should I be looking for? My other browse dialogs in my program work... not sure whats going on...

Here are the DLLs for you.

Mike, it could be that the extensibility DLL that we gave you is getting a MissingMethodException or something like that.  If some method signature within one of the core DLLs changed, it could be that an exception is being thrown and snuffed by VS (it likes to do that so that 3rd party addins by guys like us don't kill VS )  Let me zip up the rest of the core DLLs and replace all of them and tell me if you can open the browse dialog.

I tried that two or three times and its still not working... is there something i need to do to manually register the file once i've put it in the GAC? I remember vb6 you used to have to run regsvr32...

What is also interesting is that I didnt have an Extensibility xml file in Common Files\StrataFrame until i added the one you gave me.

I replaced the extensibility dll you just gave me with the original one and the Search Fields Criteria dialog came right up... what am  i doing wrong?

I don't think you got it replaced then.  I am pretty confident that the issue has been resolved and the behavior you are getting is indicitive of a version conflict.  I went through this a number of times before I posted the fix.  Are you sure that you updated the GAC?  Try manually deleted the Extensibility DLL in the GAC and the adding it back with the new one.

Ok I replaced the old extensibility file with the one you provided PLUS i replaced the extensibility file in C:\Program Files\MicroFour\StrataFrame\Assemblies with the one you just gave me.



However now when I open the SearchFields dialog and click on a field and then click edit... the dialog just closes... no error message...just disappears...



I removed the field and then clicked Add... it let me setup the new field but then i clicked ok it didnt add the field to the list...

I have made a change to the extensibility DLL that should resolve your problem.  The instructions on implementing the changes are below.  As a side note, one thing I noticed that wasn't right within your application was your use of the SetConnections() method.  This is really something that should never be called outside of the SetDataSources method in the AppMain.vb file.  You connections should already be established before you starting showing and loading forms....at least in most cases. 

1. Close down Visual Studio
2. Drag the DLL into the c:\windows\assembly folder (GAC)
3. Copy the DLL and XML file to c:\program files\common files\microfour\strataframe
4. Re-open Visual Studio and you should be good to go!

Ok, Here's what I tried. I'm using ver 6.3.3 of DevExpress and ver 1.6 of StrataFrame. I created a blank StrataFrame application...created a BO based on the customers table in the StrataFrame Sample database. I dropped the CustomerBO on the form and dropped the BrowseDialog on the same StrataFrame StandardForm. Then I setup the BrowseDialog and it produced the same results.



I opened this project on two other computers including my own. One of them even had Visual Studio SP 1 installed and we got the same results. On my test computer I uninstalled SF1.6 and re-installed SF1.5 only to discover that this functionality didnt exist in 1.5



I've attached the project I created.



I am including screenshots that show my version of Visual Studio.



My Visual Studio Version





Visual Studio Version of my collegue

If you create a maintenance form or a standard form you will see that they both inherit MicroFour.StrataFrame.UI.WIndows.Forms.StandardForm.  A MaintenanceForm is just a template with a header and maintence form toolstrip already dropped on the form.

I cannot reproduce your behavior as much as I am really trying to.  If you create a new project, create a BO, drop on a browse dialog, and try to go through the same steps do you get the same results?  Also, are you dropping the browse dialog directly on the form or is this an inherited browse dialog?  Is the browse dialog dropped on a user control?  Last, could you create a simple project that reproduces the behavior so I can test it on this side?  Thanks.