[CLOSED] Trunk CDN referring to 2.5 branch Error 404.

[michaeld]

Just noticed this...

Trying to figure out how to revert back to 2.4

[michaeld]

Okay, the answer is switch the AssemblyInfo.cs file in Properties to

[assembly: AssemblyVersion("2.4.0.*")]

[Daniil]

Correct. We push the sources to CDN on releases only.

[michaeld]

Curious why the trunk assembly updated to 2.5 before it was ready?

[geoffrey.mcgill]

Curious why the trunk assembly updated to 2.5 before it was ready?

The moment 2.4.0 is released, the version number should be increased. Typically we haven't done this in the past, but I did increase for the current Svn build.

This obviously caused unforeseen complications if using the Svn build and pulling resources from the CDN.

I think I'll avoid increasing the build number the next time around, until we're ready to release.

I'll also search around for some policies on when to typically increase the major-minor build numbers of projects.

Hope this helps.

[michaeld]

I think I'll avoid increasing the build number the next time around, until we're ready to release.

I think that's best policy, even though I understand that it can be confusing downloading from the trunk and determining version recent changes apply towards. Maybe you can distinguish with File Version versus Assembly Version. That or instead CDN off a const value instead?

However, I posted this issue because I thought you guys should at least be aware of the impact of the decision. I realize also it's not wise to use the CDN when running code from the trunk, especially with many bug fixes in the client code. But sometimes minor changes are unaffected/unrelated to used code, so sometimes I'll test with CDN turned on to compare the performance vs reliability boundary before posting to production.