Ivan is right as well, if you have been making changes, then backtrack and figure out what might have changed.

Well, I am drawing a blank over here. The message is telling you that it can't find the Localization embedded files in the SF source code. Those are stored into a folder called Localized Messages, and are all set as Embedded Resources. I don't know what your boss changed in the source code... You could probably start asking him and thinking if his changes could produce the error. Reinstall SF on your machine and get it working. Then get the list of changes he did and start changing on yours too, one by one, and test at each build. This way you will be able to identify what causes the error and we can try to fix it from there.

I got your PM, but I am going to respond here so that everyone else gets the benefit of this discussion as well.  First of all, there isn't a lot that can go wrong, so we just need to backup and troubleshoot one piece at a time.  We too work in a multi-developer environment, so StrataFrame is geared this way.

To begin, you made a comment about the StrataFrame menu item no longer being there, this is because we use an Add-In to load StrataFrame.  When an add-in fails, Visual Studio will set the add-in file to a LoadBehavior of 0 to keep it from loading next time.  I can tell you where to change this later, but that is why it went away.

Let's start fresh on your machine.

1. Let's remove all of your connection settings on YOUR machine where things are failing
   
2. Open Windows Explorer, and on Windows 7 you will find the files here: C:\ProgramData\MicroFour\ConnectionData
3. Delete AppKeys.dat and Connections.dat
4. Next, Uninstall StrataFrame on your machine
5. Make sure that Visual Studio is closed
6. Install the new StrataFrame build.  When prompted, check the "Skip the data deployment phase"
   
   
   
   The database has already been setup by the first and functional install of StrataFrame.  No need to do this again.
7. After the installation, when you go into Visual Studio, you will be prompted to connect to SQL Server.  Enter the appropriate SQL Server connection settings.

At this point you should be good.  If you run into any errors, please post them.  Thanks.

I copied the source code to my macine and build it, nothing changed, I am stilll getting the same error.

Please help

My Boss told me that he compiled using "any CPU" option.

I can't think of anything more specific at the time being. Maybe you could also copy the source code he changed on his machine to your machine and compile it with your Visual Studio.

I deleted the dlls from the GAC, copied the new dlls to the windows/assembly folder and StrataFrame folder. I am still getting the same error. I am now asking to my boss for the configuration. Any more suggestions?

Try deleting them all from the GAC first, then copy the ones built from the other machine back. Also, copy them to your machines "C:\Program Files\Common Files\MicroFour\StrataFrame" too. In my projects, all SF DLLs reference the DLLs from the Common Files. You could also check that your boss compiled them using Any CPU for the Plataform, you will find that in the Configuration Manager.

I uninstalled strataframe completely and then installed it. It was working perfectly well.

I drag the dlls from one window to another window containing the assembly folder as you have suggested in another post. When I run Visual Studio I noticed that the Dlls are not registered to GAC at all.

I run my batch file again and I am sending you the resulting contents for the assembly folder attached.

Could you please help us? We are totally locked to this issue in our company.

Note: Please take also into consideration that the PC building the dlls has a 32 bit Core2Duo CPU and Windows Server 2003 installed and the PC that we are trying to install has a 64 bit Core2Quad CPU with Windows Server 2008 R2 installed

Before copying DLLs and such, try a plain SF install on your machine pointing to the SQL Server you need. You should be able to get it working with the original install properly, test creating a new Project, things like that. After you get it working, then we go and try copying the other DLLs to your GAC.

After you get it working, then update the DLLs in the GAC. The batch file seemed fine, but I would advice you to do it manually to be sure. Drag the DLLs from one folder to the windows\assembly folder. By the way, you are administrator at your machine, right? To be sure the install goes fine, right click the SF installation EXE and run it as administrator.