New NAnt structure in March 2011

pokorra

I will open a new thread where we can write about new changes that happen through the new NAnt build structure.

I just made a commit, and you should run nant clean before you run nant compile the next time, because I have renamed the generated files from the winforms generator, so that they are not picked up by the bazaar add dialog. See also sourceforge.net/apps/mantisbt/o ... php?id=295

pokorra

Just to let you know, that nant generateSolution will now create additional solution files, in delivery/projects/sharpdevelop3 (and vs2008).
Those solution files contain all csproj files required for a special purpose, eg. the client, the server, the PetraTools or Testing.
This might be useful for developing just in one part of OpenPetra, and also for debugging, since only one executable is part of the solution, in the case of OpenPetra.Client.sln and OpenPetra.Server.sln.

see more details sourceforge.net/apps/mantisbt/o ... php?id=299

For Thias: I have found a way to properly use the nant task xmlpeek with the XPath. I remember you wrote that it behaved very difficult than expected. I have finally found the solution: I need to remove the xmlns from the top of the csproj file, before I try to use XPath on it. Then I can use the proper XPath syntax. NAnt is using System.Xml.XPath after all.

pokorra

And another improvement, which hopefully will help us:
we have a new task quickCompile, which does not in any way replace nant compile.
It does not generate any files, and just runs msbuild (or xbuild on LInux, which I have not got round to test myself with the new build system).
Running nant quickCompile, will default to compile the whole OpenPetra.sln.
But if you use the parameter -D:solution=Tools, or -D:solution=Client, or -D:solution=Server, or -D:solution=Testing, only the selected solution will be compiled.

Advantages:

we can see again errors and warnings, which are quite hidden in nant compile, due to the overflow of messages.
and it is much faster again, msbuild might be using several CPU cores, we suspect.

So my recommendation is:
Once, run nant generateSolution.
While you are developing, you either compile directly from your IDE, or you can compile with nant quickCompile -D:solution=Client

I am sure we will find more ways to work more efficiently, using the new cleaner structure but at the same time maintaining easy tools for developers.

More details for this commit: sourceforge.net/apps/mantisbt/o ... php?id=300

pokorra

nant generateORM works now as it has before, generating the cached tables, typed datatables and datasets, and dataaccess routines

also available: generateORMCachedTables, generateORMData, generateORMAccess

Notice: you will need to compile the solution yourself, nant generateORM will only generate the code, without compiling.

pokorra

nant generateSolution (or quicker for just fixing the solution files: nant generate-solution-all-internal) will now set the PetraServerConsole project as the startup project in the solution OpenPetra.Server.sln. It will also set the correct commandline parameters for the correct config file.
The same is for PetraClient in OpenPetra.Client.sln.

This should be a good help for debugging from within SharpDevelop (probably VisualStudio as well).

for those who are interested:
SharpDevelop just picks the last project in the solution as the startup project, even though the projects are displayed in alphabetical order in the project view, the order in the sln file counts.

pokorra

we now have a target called

nant initConfigFiles

which writes or rewrites the config files in the etc directory, and also writes the file version.txt.
This is needed for the Testing modules.

pokorra

new target nant quickClean deletes files by a pattern, not because they are part of a project.
nant quickClean cleans all generated files and the delivery directory.
this helps when switching between branches, otherwise you still have generated files after running nant clean

pokorra

nant generateSolutionNoCompile now works without compiling most of the code, only nanttasks and Ict.Common and PetraTools are compiled automatically.
this helps with getting csproj and sln files in order to fix compiler errors in the code

pokorra

Sorry about the last commit.

I have now reverted the function of nant generateSolutionNoCompile, it works as it has before.

I have changed the new functionality to nant quickGenerateSolution, unfortunately somehow there is a problem with missing references, eg. Ict.Petra.Shared.MCommon does not refer to Ict.Petra.Shared.dll anymore.

thiasg

pokorra wrote
Sorry
I have changed the new functionality to nant quickGenerateSolution, unfortunately somehow there is a problem with missing references, eg. Ict.Petra.Shared.MCommon does not refer to Ict.Petra.Shared.dll anymore.

Since sourceforge.net/apps/mantisbt/o ... php?id=344 nant minimalGenerateSolution does exactly that...

ThiasG