Commented by: @hvlad

It will be great if Beta1 packages would be updated when (currently missed) embedded package will be build

Commented by: maziar navahan (maziar1)

i report same problem in FB2.1 alpha 1 but other admin don accept this :-(

Commented by: maziar navahan (maziar1)

not only Microsoft.VC80.CRT.manifest

for me in windows 2003 R2 enterprise the vcredist_x86.exe require install before beta 1 installation

Commented by: @reevespaul

re: Missing Manifest

This issue was fixed in CVS at about the same time the bug was logged. But, can someone clarify what, exactly, is the problem? I am having a hard time reproducing any problem with W2K3 R2 and Fb 2.1. Is there an error message? What is it?

-----

Never mind. A clean install of W2K3 shows the problem clearly enough.

Commented by: @reevespaul

re: vcredist

We distribute the MS runtime libraries so as to minimize system dependencies. But we also allow installation of fbclient or gds32 into <sys>. This won't work unless vcredist*.exe has been installed. Many (most?) applications rely on finding the client library in <sys>, which is why I am thinking that installing vcredist*.exe should be manadatory. This would then remove the need to distribute any of the MS runtimes.

In fact, we do have a problem here - applications that rely on loading the client library from <sys> will fail if the manifest for the MS runtimes has not been deployed. AFAICT, we are not allowed to deploy this manifest ourselves. It must be done via vcredist* .

Commented by: @dyemanov

Let's run vcredist* during the installation then.

Commented by: @reevespaul

Ha! Ha! Very funny. :-(

Unfortunately, this is not ideal for two reasons...

1/ Unless we upgrade to VS2005 SP1 we must use the original vcredist*.exe. But this has a dependency upon MSI v3, which is not available on clean installs of Win2k or XP. The VS service pack removes this restriction.

2/ The 64-bit installer will also include installation of a 32-bit client. This would mean we have to include two versions of vcredist*.exe with the 64-bit kit.

I don't know what the solution is. For now (ie, Beta 2), I think we will have to document the issue and tell users where to get vcredist*.exe.

Commented by: @reevespaul

Or, another solution would be to statically link fbclient, thus removing the dependency on the ms runtime.
I tried earlier but hit a linker error. Didn't have time to look at it further.

Commented by: @reevespaul

Beta 2 will link statically, thus removing the need to deploy any MS runtime libraries.

Commented by: Freddy Ertl (freddy)

The fbclient.dll in Beta 2 (2.1.16780) still contains a reference to MSVCR80.DLL. Will this be removed in the final release?