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.

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.

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

Thank you for the replies. I am going to apply Trent's message step by step and inform you about the results. Meanwhile I would like to tell that I asked to my boss and he told me that the changes in StrataFrame source code are only minor changes and they can be called only bug-fix changes. He also mentioned that these changes are working perfectly well in his PC (Windows 2003 Server/32 bit Core2Duo CPU).

Hi,

I finished all 7 steps successfully without any error. Everything is working fine with Strataframe, I am waiting for the next steps to install new source code dlls.

Now, as for new source code, it sounds as though you have made changes to StrataFrame.  Honestly, this is really never a good idea.  If there is something at the root level that is an issue, then we should be made aware so that it can make standard distribution.  If you are extending the framework, you should create your own assemblies that inherit from StrataFrame.  Then you can override, etc. and not have any core issues.

But at any rate, you will want to get the most recent version of source code.  You will then build it in debug mode so that you can track any errors that may come up during development more easily.  These assemblies should be updated in the GAC once built using the gacutil.  The AfterBuild.bat files attempt to do this for you in the post build events of the project.  If you open up the GAC and see multiple versions of the same assembly of StrataFrame with the same version, then you will need to remove the one that you are not using.  I recommend building StrataFrame in MSIL (All CPUs) as this will reduce downstream issues.

If you take any of these steps and it doesn't work, then you know that it is the source code you are building.  At that point, there is not much I can do for you as you will need to talk with your co-worker and figure out what has changed and how to resolve these issues.

Hi Trent,

Please take into consideration that the changes to the StrataFrame source code is working perfectly well in my boss PC (Windows 2003 Server with 32 bit Core2Duo CPU). The changes to the source code are only some bug-fix changes, new properties are added and Foreign Key Support is added. We can share the code with you if it is required.

We are thinking that if the dlls are working in one environment perfectly well, they should be able to work in another environment too.

Could you please help us?

Now you have SF originally working on your machine, have you by any means tried making the changes one by one to your source code, compiling it, and testing it? Since he has made changes to the source code, I would think he has a list of them. And as they are not many, as you said, it would point you directly to where the issue could be.

I will be trying to implement the changes to the new version of StrataFrame and post the problems here.

Thank you for your support. I managed to handle the problems with 1.7.3.5 by applying all changes one by one.

I like version 1.7.3.5