Recent changes to bugs

Very nice post, good luck! ;-)

2011-02-16T09:10:51Z

Very nice post, good luck! ;-)

Crash while trying to add .designer.cs files into CSPROJs

2010-06-14T16:40:31Z

Hi.

I know that it has already been an issue about this, but I'm currently linked with Prebuild's trunk and the application is crashing when it tries to add .designer.cs files in a csproj. I'm using a structure <Match path="source/cs/ROOT_NAMESPACE" pattern="*.cs" recurse="true"/> for all my C-Sharp source files adding. Below follows the traceback:

Prebuild v2.0.4
Copyright (c) 2004-2008
Matthew Holmes (matthew@wildfiregames.com),
Dan Moorehead (dan05a@gmail.com),
David Hudson (jendave@yahoo.com),
Rob Loach (http://www.robloach.net),
C.J. Adams-Collier (cjac@colliertech.org),
See 'prebuild /usage' for help

[!] Match in project MyProject returned no files: Resources\*.jpg
Creating Visual Studio 2008 solution and project files
...Creating project: MyProject
Unhandled error: Length cannot be less than zero.
Parameter name: length
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at Prebuild.Core.Targets.VSGenericTarget.WriteProject(SolutionNode solution, ProjectNode project)
at Prebuild.Core.Targets.VSGenericTarget.WriteSolution(SolutionNode solution, Boolean writeSolutionToDisk)
at Prebuild.Core.Targets.VSGenericTarget.Write(Kernel kern)
at Prebuild.Core.Kernel.Process()
at Prebuild.Prebuild.Main(String[] args)

Unfortunately I can no longer the last tag because of VS 2010 support.
Cheers,
Vinicius Pessôa.

frameworkVersion attribute ignored for MonoDevelop target

2010-05-17T14:43:22Z

Problem : The "frameworkVersion" attribute of the "Project" nodes in prebuild.xml is ignored when generating the MonoDevelop Project configuration file. This can block the build in Monodevelop (for OpenSim for instance) : some references are identified as not available for the default frameworkVersion used.

Expected behaviour : if frameworkVresion is set to "v3_5" in prebuild.xml, the generated .mdp files should contain a "targetVersion" attribute in the project node set to "3.5".

Solution : I think a minor modification of the WriteProject method in Prebuild/src/Core/Targets/MonoDevelopTarget.cs:185 should do the trick. I attached a patch.

SupressWarnings option not respected by NAnt build

2010-02-06T07:41:43Z

Generated NAnt build does not respect SupressWarnings option in prebuild.xml

Nant output directory does not respect configuration

2009-05-22T18:42:25Z

At least for exe projects the nant project output is directed to project/bin/Release or project/bin/Debug instead of the output directory defined in the prebuild.xml.

Exe projects nant build has gac references with .exe ending.

2009-05-22T16:57:21Z

With exe projects the generated nant build file has references like System.Drawing with .exe ending instead of .dll. This works correctly for Library projects. The ending might be generated based on the project type.

How changing from Library project to exe project affects generated nant file includes:
<include name="System.dll" />
=>
<include name="System.exe" />

Visual Studio 2008 WinForm design.cs support missing

2009-05-22T14:57:55Z

For visual studio 2008 projects do not correctly reference all three files belonging to a winform. Namely the xxx.cs, xxx.Designer.cs and xxx.resx even if you refer the .cs file explicitly with file type Form.

Nant: project references do not respect localCopy="true"

2008-12-29T19:13:56Z

If I refer to library project output in exe project and set localCopy="true" nant build does not copy the library output to the exe project output in the same manner as external library dependencies. This would be very usefull if I have several library and exe projects in the same build and would not want to put output from all to same directory.

Prebuild fails on network shares.

2008-12-13T16:53:47Z

If you try to run prebuild on a project that lies on a network share, Prebuild will fail with the following message:

Prebuild v2.0.3
Copyright (c) 2004-2008
Matthew Holmes (matthew@wildfiregames.com),
Dan Moorehead (dan05a@gmail.com),
David Hudson (jendave@yahoo.com),
Rob Loach (http://www.robloach.net),
C.J. Adams-Collier (cjac@colliertech.org),
See 'prebuild /usage' for help
[X] Δεν υπάρχουν άλλα αρχεία. <-- translation: "File not found"
[X] Object reference not set to an instance of an object.
[X] Object reference not set to an instance of an object.
[X] Object reference not set to an instance of an object.
Unhandled error: Object reference not set to an instance of an object.
at Prebuild.Core.Utilities.Log.WriteException(LogType type, Exception ex)
at Prebuild.Core.Kernel.ParseNode(XmlNode node, IDataNode parent, IDataNode preNode)
at Prebuild.Core.Kernel.ProcessFile(String file)
at Prebuild.Core.Kernel.Process()
at Prebuild.Prebuild.Main(String[] args)

This looks like a permission problem or a path problem (network share is mapped to Z:\trunk). Any ideas?

buildAction="FileCopy" support on MonoDevelop target

2007-07-08T00:32:28Z

This is in the latest version (2.0.1). I cannot make a file included (not source code to compile) in a MonoDevelop project to be copied to the output directory, even if the copyToOutput="Always" is set for that file.

So, I modified the target for MonoDevelop to check, when setting the buildAction, if copyToOutput was set for that file. It makes buildAction = "FileCopy".

I attach this patch.

Congratulations for this project. I think is very useful.