On 2011-09-21, Michael Schall wrote:
> I think it would be beneficial to add the svn url (with revision) to
> the assembly description then so this information is available to the
> end user.
svn trunk will now add it to the AssemblyDescription attribute.
Stefan
I think it would be beneficial to add the svn url (with revision) to
the assembly description then so this information is available to the
end user.
On Wed, Sep 21, 2011 at 3:51 AM, Stefan Bodewig wrote:
> Hi all,
>
> after playing with it I was faced with a compiler warning about the
> format.
Hi all,
after playing with it I was faced with a compiler warning about the
format. "Standard" version formats require the numbers to be unsigned
shorts whose range the ASF's svn revisions have long left behind.
The result is not only a warning that we could ignore but also a version
number that
On 2011-09-12, Dominik Guder wrote:
> Am 09.09.2011 05:52, schrieb Stefan Bodewig:
>> On 2011-09-08, Dominik Guder wrote:
>>> using nant for retreiving svn revision to property svn.revision:
>>> use svn log (repository access)
>>> >>output="_svnrevision.xml" failonerror="true">
>>>
Am 09.09.2011 05:52, schrieb Stefan Bodewig:
On 2011-09-08, Dominik Guder wrote:
using nant for retreiving svn revision to property svn.revision:
use svn log (repository access)
It is likely fair to assume that whoever uses NAnt also has a svn
command line client arou
On 2011-09-08, Dominik Guder wrote:
> using nant for retreiving svn revision to property svn.revision:
> use svn log (repository access)
>output="_svnrevision.xml" failonerror="true" >
>
>
>
>
>
> xpath="/log/logentry/@revision"
> property="svn.revision
On 2011-09-08, Michael Schall wrote:
>> Interesting. How do you integrate this with your build process?
> I can give you specifics if you want, but we use MSBuild and MSBuild
> Community Tasks (http://msbuildtasks.tigris.org/)...
> We have a target that uses the SvnInfo task to find the Subersi
Am 08.09.2011 17:01, schrieb Michael Schall:
We set the forth digit to 0 for the AssemblyVersion attribute and SVN
revision number for the AssemblyFileVersion attribute. This way you can
slipstream fixes without breaking compatibility with other's code, but
you still have the revision number if
> I'd rather release 1.2.NEXT then. YMMV.
We had issues where if the AssemblyVersion didn't match exactly, .Net would
not load the assemblies without a redirect.
> Interesting. How do you integrate this with your build process?
I can give you specifics if you want, but we use MSBuild and MSBui
On 2011-09-08, Michael Schall wrote:
> We set the forth digit to 0 for the AssemblyVersion attribute and SVN
> revision number for the AssemblyFileVersion attribute. This way you can
> slipstream fixes without breaking compatibility with other's code, but you
> still have the revision number if y
We set the forth digit to 0 for the AssemblyVersion attribute and SVN
revision number for the AssemblyFileVersion attribute. This way you can
slipstream fixes without breaking compatibility with other's code, but you
still have the revision number if you want it.
We also add the actual SVN url to
Hi,
I don't expect us to release betas or any other kind of two releases
that would only differ in the forth digit of the version number. So we
could simply set it to 0 (which I think currently happens in trunk,
didn't check).
Right now I'm afraid I won't be able to build all binaries on the sam
12 matches
Mail list logo
