Stashing Finalbuilder itself in our version control system

Greetings!

We put as many pieces as possible into our version control system (compilers, frameworks, etc) to simply rolling out new build systems. We have always has Finalbuilder v2 and v3 in our perforce system, and we call and use those copies of finalbuilder.

We are now moving to finalbuilder v6.

Any advice on how to get the finalbuilder animal itself into version control, to run from that dir? (and to remove it from windows programs installed on the build system) ?

 

thanks a ton!           

Hi Rafael

FinalBuilder 6 is a whole lot more complicated than FB2 or 3. There are type libraries that need registering and assemblies that need installing in the GAC. I cannot recommend this as a way of installing FinalBuilder on a machine.



Waaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaah.




GAC ?? <gag!></gag!>

Global Assembly Cache. The finalbuilder msbuild task assembly and visual studio tfs addin assemblies are gac installed. The msbuild task assembly is used by the msbuild, visual studio.net and C++Builder 2006/7/9 actions for formatting the output. Other than that, the FBActionCtx.dll com dll needs to be registered, but only after FB60CustomActionInterfaces.tlb type library is registered.

You will also have to consider the license key installation (doesn’t live in the registry like older versions) and the configuration files.

HTH

I know what the GAC is (sorry)… I was trying to say “GAC?? Ack!”

Anyway, thx much!