I need help.

Besides the obvious.

I recently replaced my old workstation with a new 64-bit Windows 7 machine.  It is sweet.  I have VS2008 installed and installed SF with the most recent version.  I backed up the local SF database on the XP machine and restored it the new v7 machine.  All seems to be fine, except the BOM has Xs on everything.  It does not read the source database.  That is troublesome.

I need help.  Are there other gotchas waiting for me?

Thanks,
Bill

When I rebuild the Inherited UI, I get the following message:

MicroFour StrataFrame Inherited UI -> C:\Program Files (x86)\MicroFour\StrataFrame Source Code\MicroFour StrataFrame Inherited UI\bin\Debug\MicroFour StrataFrame Inherited UI.dll
"C:\Program Files (x86)\MicroFour\StrataFrame Source Code\AfterBuild.bat" "C:\Program Files (x86)\MicroFour\StrataFrame Source Code\MicroFour StrataFrame Inherited UI\bin\Debug\MicroFour StrataFrame Inherited UI.dll" "C:\Program Files (x86)\MicroFour\StrataFrame Source Code\MicroFour StrataFrame Inherited UI\bin\Debug\MicroFour StrataFrame Inherited UI.xml"
The system cannot find the path specified.
'"C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0A\bin\gacutil.exe"' is not recognized as an internal or external command,
operable program or batch file.

The solution states that the build (or rebuild) succeeded; however, I am getting odd errors related to old versions of DevEx that have never been installed on this new machine.

Did I install something wrong?

There is an Afterbuild.bat file that is distributed with StrataFrame that copies the built assembly to the Common Files folder as well as the GAC after the assembly is built to replace the previous assembly.  You may need to adjust your local path to include these files.  Since you are running on a 64-bit platform, I recommend just copying the gacutil.exe to the expected path. But if not, then just adjust your afterbuild.bat to point to the proper locations.

This is the contents of the AfterBuild.bat file located in the program folder:

"%ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" -i %1 -f
"%ProgramFiles%\Microsoft SDKs\Windows\v6.0A\bin\gacutil.exe" -i %1 -f
copy /Y %1 "%CommonProgramFiles%\MicroFour\StrataFrame"
copy /Y %2 "%CommonProgramFiles%\MicroFour\StrataFrame"

First of all, I do not have Visual Studio 8 or SDK v2.0.  I suppose I could change it to 9, but there is not v2.0 in that SDK folder...only a 3.5 folder.  No gacutil.exe exists in the bin directory.

Second, since all of the MicroFour stuff is loading in the x86 folder, would the wildcards even work?

Thanks for your help!!!
Bill

Here is what I have in mine and I run a 64-bit OS:



"C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\gacutil.exe" -i %1 -f

copy /Y %1 "C:\Program Files (x86)\Common Files\MicroFour\StrataFrame"

copy /Y %2 "C:\Program Files (x86)\Common Files\MicroFour\StrataFrame"







Actually they would. As the GAC is the first place anything is pulled from. The Program Files location is what is used for reference purposes. At any rate, if you don't see the gacutil.exe, just copy it someplace and point the path to it.

Perfect!  That worked.

Now, I have two warnings for things that are no longer used in the app:

Unable to apply publish properties for...
'microsoft.office.interop.outlook'
'office'

Not sure how to get rid of these items.  I do not have the Microsoft Office suite installed.  We are migrating to OpenOffice.

Don't know other than it would appear that there is a reference to this assembly. Do you have this reference in any of your projects? Where do you get these warnings? I don't recall these ever being in StrataFrame.

I actually triple checked every assembly...those references are not found anywhere.  I did utilize those at one time, but since we are abandoning a direct link to Microsoft Office products from the application, I decided to begin removing these references.  As far as I know, none of the code references these assemblies.  I'll double-check.  I will also do the standard...close the IDE and reopen.

Also, when you do something like this, it doesn't hurt to smoke it from disk (um...delete it) and then get it from source control again to make sure that there are not any left over references.

It's a click-once setup thing.  From the Publish tab of the Properties window for the app, I selected Application Files.  The two were in there...I excluded them and removed them from the list.  After rebuilding, the warnings have vanished.