My first FB project

FinalBuilder Discussion
1

Hi All,

I am doing my first FB project and have a few questions (we are using Perforce SCM):

1) Is it necessary/recommended to extract the latest version of source files to a temp build folder? If yes, what we need to do?
2) We need to increase the AssemblyInfo.cs file of a .NET C# project. What is the best action to do this?
3) Shall we check out the AssemblyInfo.cs file before incrementing the version number of using a copy of this file in a temp folder will suffice? If yes, what we need to do?
4) Does a FB sample on building a Perforce managed source code exist?

Thanks in advance,

Alberto

 

 

 

 

 

2
  1. The folder doesn’t have to be a temp folder, however the Perforce Sync action allows you to specify where to put the files.
    2) Assembly Info Updater action
    3) Yes, files need to be writable so that they can be updated. You will need to use the Perforce Open for Edit action.
    4) No, we cannot possibly create sample projects that cover everything that people want to do with FinalBuilder, we would have no time left to actually develop the product.

3

Thanks Vincent,

>> 1) The folder doesn't have to be a temp folder, however the Perforce Sync action allows you to specify where to put the files.
Ok, we will use the something like c:\build as destination folder. To do a P4 sync operation on the build server do you suggest to make a fictious 'build' user? Both perforce and FinalBuilder are installed on the server.
 
>> 2) Assembly Info Updater action
Where do I specify what to increment in the AssemblyInfoUpdater action? For example the BuildVersion ? Should I add something into the Attributes list?

Thanks,

Alberto

4

2) The Assembly Info Updater only knows how to update the entire value of the attribute. I have attached a demo on how to use a property set to do this

AssemblyInfoDemo.fbp6 (13.029 KB)
5

Hi Vincent,

I can't increment the fileBuildNumber. See the log below. For some reason only the buildNumber is updated (not the fileBuildNumber). Why?

[assembly: AssemblyVersion("3.0.521.0")]    
[assembly: AssemblyFileVersion("3.0.520.0")]

Thanks,

Alberto

PropertySet define [ AssemblyNumbers ]
    Status: Completed
      Date: 12/10/2009
      Time: 14:15:34:029
       End: 14:15:34:029
  Duration: 00:00:00:000

Action Messages:
Load [ C:\Build\Eyeshot3\SyncDest\Eyeshot\Main\Control\Properties\AssemblyInfo.cs ] to [ AssemblyNumbers ]
    Status: Completed
      Date: 12/10/2009
      Time: 14:15:34:038
       End: 14:15:34:064
  Duration: 00:00:00:026

Action Messages:
Scanning AssemblyInfo file C:\Build\Eyeshot3\SyncDest\Eyeshot\Main\Control\Properties\AssemblyInfo.cs
Assigning values to PropertySet AssemblyNumbers
Setting MajorVersion to "3"
Setting MinorVersion to "0"
Setting BuildVersion to "520"
Setting RevisionVersion to "0"
Setting FileMajorVersion to "3"
Setting FileMinorVersion to "0"
Setting FileBuildVersion to "520"
Setting FileRevisionVersion to "0"
PropertySet [ AssemblyNumbers ] increment [ BuildVersion ]
    Status: Completed
      Date: 12/10/2009
      Time: 14:15:34:064
       End: 14:15:34:064
  Duration: 00:00:00:000

Action Messages:
Property BuildVersion is now 521
PropertySet [ AssemblyNumbers ] increment [ FileBuildVersion ]
    Status: Completed
      Date: 12/10/2009
      Time: 14:15:34:064
       End: 14:15:34:070
  Duration: 00:00:00:006

Action Messages:
Property FileBuildVersion is now 521
AssemblyInfo Updater [ Files: 2 ]
    Status: Completed
      Date: 12/10/2009
      Time: 14:15:34:080
       End: 14:15:34:096
  Duration: 00:00:00:016

Action Messages:
Processing File : C:\Build\Eyeshot3\SyncDest\Eyeshot\Main\Control\Properties\AssemblyInfo.cs
Updating Assembly Version from Property Set "AssemblyNumbers"
Processing File : C:\Build\Eyeshot3\SyncDest\Eyeshot\Main\Geometry\Properties\AssemblyInfo.cs
Updating Assembly Version from Property Set "AssemblyNumbers"

 

6

Hi

I have added another option to the actions to allow updating the AssemblyFileVersion from the property set :

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1852.exe

7

Thanks, already downloading…

We also don’t receive e-mail notification from the forum. Already checked the e-mail in the user profile and it’s correct.

Thanks,

Alberto

8

Hi Alberto

Thanks for the heads up on that, for some reason the subscriptions had stopped working, I disabled them and re-enabled them and now they appear to be working.

9

Thanks Vincent,

It works perfectly. What about using this 'version number' to label the build? (we use Perforce)

Two other thing I noticed:

1) {smartassembly} action doesn't allow parameters to be used. We normally do in a batch file:

"C:\Program Files (x86)\{smartassembly}\{smartassembly}.com" "c:\devDept\nextEyeshot\SmartAssembly projects\standard.{sa}proj" /build /input="c:\devDept\nextEyeshot\Eyeshot\Bin\Release\Standard\devDept.EyeshotStandard.dll" /output="c:\devDept\nextEyeshot\Eyeshot Standard\Bin\devDept.EyeshotStandard.dll"

therefore we need to use the Execute Program action. ({sa} was purchased by Red-Gate, therefore should become even more popular)

2) On a clean Windows Server 2008 R2 installation, the running man of the FB User Interface does not run .

Alberto