Here we go again. Why can't a new release use the latest version of MVC?
I updated my project and got MVC version warnings, again, just like in the fall.
Sure enough, I downloaded the SOURCE code and looked, and it uses MVC 5.2.6 still.
NOTE: If a ticket is put into the system, it will take weeks or even months for a fix because this is always deemed low priority.
5 Answers, 1 is accepted
I apologize for any inconvenience caused by this.
The developers have already addressed the issue and the version of System.Mvc is updated. The update will be included in the next Service Pack. If you would like to avoid seeing the warning in Visual Studio sooner I suggest downloading the next internal build when it is available.
Thanks Viktor for the update. It was upsetting because our release will go out before any update. However, I found a way to suppress the build warning.
But is there anyway that this can be prevented in the future since it happens almost each time?
Basically, before building a release, check and see if all Microsoft packages are up-to-date.
We are working on a process to ensure that the latest MVC version is used with the Kendo components. It should be applied soon so such warnings can be avoided in the future.
I am afraid that we do not have an exact date scheduled for the Service Pack, however, it would be probably be available for download mid to late February.