Legacy Release Candidates

2014-02-12 00:00:00 -0800

Release candidates 1 & 2 were discussed, indirectly, in the pre-release announcement. I'm about to push release candidate 3, which should be the final release candidate before the real and true legacy release! It's just that we broke an awful lot of the task APIs in the process. And I want to alert you to the changes before the push.

We didn't have to make breaking changes. We could have spent a few versions introducing aliases, parallel features, and the like. Then, obsolete and remove them over time. But, we're way behind and, given the state of things, it was a reasonable option. There were a lot of inconsistent styles, naming, and patterns that were causing trouble.

I hope, now, you won't have to visit the docs every time you use a task, but, rather, once! You'll see the same "kinds" of breaking changes throughout, here is a summary

Breaking Changes

aspnetcompiler

assemblyinfo

csc

docu

fluentmigrator

ilmerge

msbuild

msdeploy

mstest

mspec

nchurn

ncoverconsole

nugetinstall

nugetpack

nugetpush

nunit

nuspec

output

plink

specflow

sqlcmd

vssget

xunit

zip

blog comments powered by Disqus