Reply to thread

Message

<blockquote data-quote="Mr.Mitchell" data-source="post: 15837" data-attributes="member: 10300">The idea is that Nant uses the exact same build files as used by Visual Studio, this makes it so that the Nant buildfile never needs updating. This works quite well, except if some invalid references sneak into the VS.NET build files. VS.NET seems to ignore invalid references, so they are not detected by the main devs. This does not happen often, but sometimes (like now) it screws up the Nant build. I will ask one of the devs to fix this reference and then the Nant buildfile will work again.Postbuild.bat is called automatically at the end of a succesfull Nant build through the postbuild step in the VS.NET buildfiles, so no need to put all that stuff in the Nant buildfile. Running Postbuild.bat manually is ONLY needed as a workaround to copy and register the DirectShowHelper.dll.Nope these are not needed. When I wrote this guide I had to add them, but that was related to a bad SDK install I found out later. The targets in my current buildfile look like this: [code]&nbsp; &lt;target name=&quot;release&quot;&gt;&nbsp; &nbsp; &lt;solution configuration=&quot;release&quot; solutionfile=&quot;MediaPortal.sln&quot;&gt;&lt;/solution&gt;&nbsp; &lt;/target&gt;[/code]So no paths needed anywhere.I have had the idea to update the guide, cause some stuff is obsoleter and can be easier, but I wanted to wait for the Nant final version, but that is taking such a long time :-(. Might be a good idea to update the guide anyway with the latest Nant release candidate. An list with the exact steps will be added to the guide, any other requests?</blockquote>

[QUOTE="Mr.Mitchell, post: 15837, member: 10300"] The idea is that Nant uses the exact same build files as used by Visual Studio, this makes it so that the Nant buildfile never needs updating. This works quite well, except if some invalid references sneak into the VS.NET build files. VS.NET seems to ignore invalid references, so they are not detected by the main devs. This does not happen often, but sometimes (like now) it screws up the Nant build. I will ask one of the devs to fix this reference and then the Nant buildfile will work again. Postbuild.bat is called automatically at the end of a succesfull Nant build through the postbuild step in the VS.NET buildfiles, so no need to put all that stuff in the Nant buildfile. [color=red]Running Postbuild.bat manually is ONLY needed as a workaround to copy and register the DirectShowHelper.dll.[/color] Nope these are not needed. When I wrote this guide I had to add them, but that was related to a bad SDK install I found out later. The targets in my current buildfile look like this: [code] <target name="release"> <solution configuration="release" solutionfile="MediaPortal.sln"></solution> </target>[/code]So no paths needed anywhere. I have had the idea to update the guide, cause some stuff is obsoleter and can be easier, but I wanted to wait for the Nant final version, but that is taking such a long time :-(. Might be a good idea to update the guide anyway with the latest Nant release candidate. An list with the exact steps will be added to the guide, any other requests? [/QUOTE]

Verification