If you look here http://sigmahost.net/keith/sfhelp/ you will see examples of the errors I am getting.



You can see that the 1.5 and 1.6 DLL's are in the GAC, yet only the 1.6's seem to be available to VS2005 and my projects. The project shown was done in 1.5 and shouldn't know anything about 1.6, but you can see that the reference to Microfour Strataframe Base shows version 1.6.0.0 and has a path to the \Common Files\Microfour\Strataframe directory which now only contains the 1.6 DLL's. Is that my issue, that I have loaded references improperly?



I checked more last night and every project I have no will not load into VS after updating to 1.6.



Thanks for the help, as right now I am dead in the water.




Keith Chisarik

The Add Reference window looks at the folder that we specified within the AssemblyFolders VS registry key.  Since it's just a folder (the C:\Program Files\Common Files\MicroFour\StrataFrame), we can only have one copy of the file in that folder, so the install overwrites the 1.5 DLLs that are out there with the 1.6 DLLs.  If you want to be able to see the 1.5 DLLs in the Add Reference window, you will need to create a folder somewhere to store them and add the registry key pointing to that folder. 

The key you will need to add is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\<some name>

The <some name> will need to be replaced with something like "SF 1.5" or "StrataFrame 1.5"; it isn't used, but it helps you identify it if you come back in there later.  You will then need to set the value of the (Default) value within the key to the full path of the folder containing the 1.5 DLLs.

After you do that, the next time you restart VS, you will be able to see both the 1.5 and 1.6 DLLs as selectable items in the Add Reference window.

That magically fixed all my problems, I didn't even have to re-add my references in my projects, they just found the 1.5 DLL's after I added the registry key.



Awesome, you guys are worth your weight in gold.



Last question, do you have any problem with me doing this, keeping some old projects that I consider "complete" in 1.5, and maintaining new projects in 1.6? I would upgrade a project if in the future it required a major overhaul. I am just used to doing this, I have projects in different versions of VFP (6,7,8, and 9) because it isn't worth the time to update them.



If you tell me I need to rethink this approach, I will.



Thanks again.

Keith Chisarik

This is entirely up to you and I understand your logic.  If a product is going to continue to mature then we always migrate it forward.  However, if it is complete and never going to change..hopefully ...then if it ain't broke, don't fix it