UpdateAssemblyInfo: create local tmp file in \obj.

[lessneek]

Now UpdateAssemblyInfo task creates temp assembly info file within
$(ProjectDir)\obj$(ConfigurationName).

Fix #146.

To include generated temp assembly info file to a nuget symbols package you should write in nuspec a line like this one:

<file src="BuildTest\**\*.cs" target="src\BuildTest\" />

[JakeGinnivan]

@SimonCropp you are more familiar with the task side of things

[JakeGinnivan]

Anyone? @nulltoken @SimonCropp @andreasohlund

I don't really use the task side of things so would prefer not to review this

[lessneek]

I'd prefer not to use the task as well, but this task can update AppVeyor build number and do not touch AssemblyInfo.cs files without restoring previous state.

[andreasohlund]

Looks good to me, @SimonCropp can you do a once over before we pull?

[SimonCropp]

looks good

[lessneek]

Update NuGet package please.

[gep13]

Update NuGet package please.

Hello,

Although this pull request has been accepted, it is part of a larger milestone, namely 2.0.0. As a result, a new nuget package will not be created until everything for 2.0.0 is ready. I don't think this is far off though, so please be patient.

Gary

[andreasohlund]

You can also grab the latest artifacts from the buildserver if you can't
wait:

http://builds.particular.net/viewLog.html?buildId=64876&tab=buildResultsDiv&buildTypeId=GitFlowVersion_1Buil

Side note: The version number looks hosed? cc @JakeGinnivan

On Tue, Dec 9, 2014 at 8:12 AM, Gary Ewan Park notifications@github.com
wrote:

Update NuGet package please.

Hello,

Although this pull request has been accepted, it is part of a larger
milestone, namely 2.0.0. As a result, a new nuget package will not be
created until everything for 2.0.0 is ready. I don't think this is far off
though, so please be patient.

Gary

—
Reply to this email directly or view it on GitHub
#316 (comment)
.

[gep13]

Side note: The version number looks hosed? cc @JakeGinnivan

Not good. Looks like this started happening on the 4th December. :(

[andreasohlund]

Seems to be this commit:
12359cc

On Tue, Dec 9, 2014 at 8:43 AM, Gary Ewan Park notifications@github.com
wrote:

Side note: The version number looks hosed? cc @JakeGinnivan
https://github.com/jakeginnivan

Not good. Looks like this started happening on the 4th December. :(

—
Reply to this email directly or view it on GitHub
#316 (comment)
.

[JakeGinnivan]

Fixed this in my latest PR, we were parsing '1' as SemanticVersion=1.0.0

If we merge my PR then we should be fine to release 2.0.0.