14 Answers, 1 is accepted
To my understanding, ASP.NET vNext is currently in CTP4 stage, with a Beta1 version yet to published in the upcoming weeks. That's why at this juncture we don't have a test version of our ASP.NET MVC product built against ASP.NET vNext. However, we're closing watching the evaluation of the ASP.NET framework in the future.
Once a stable ASP.NET vNext Beta release is available publicly, we'll evaluate it thoroughly and will prioritize/align our plans for Telerik UI for ASP.NET MVC development for 2015. Stand by for more information in the upcoming months.
Kind regards,
Sebastian
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Rank 2
We're working on a build for Beta 6 and we will release NuGet packages that support it.
These won't go live on NuGet.org at least until Visual Studio updates its support to Beta 6.
Regards,
T. Tsonev
Telerik
Rank 2
Hey,
Visual studio did update support for beta 6 on 27th of July, check http://www.asp.net/vnext (but itd not automatic and needs to be installed ). According to roadmap ( https://github.com/aspnet/Home/wiki/Roadmap ) Beta 7 should be 'supported' in next 2 weeks.
Having said that I dont mind if its not in the official NuGet feed as long as its available somewhere ;)
Thank you for the great job,
Rok
I am happy to announce we already support the latest Beta versions of ASP.NET 5 and MVC 6 with Telerik UI for ASP.NET MVC, and you can find more information on this topic in this blog post. For your convenience I updated the project in it to Beta6 and attached it to this forum thread to experiment with it.
Best regards,
Sebastian
Telerik
Rank 2
Thanks for the reply, shortly after posting that i realized that there is a new .805 version available which works perfectly.
Kind regards,
Rok
Rank 2
Hi Again,
is there an (easy) way to build vnext nugetpackage from sources, they seem to be missing xproj project?
BTW: 'final' Beta7 build is available on asp.net/vnext
Regards
Rok
To my understanding, you don't need xproj file but rather you can use the project.json file as depicted in these online sources:
http://mikemengell.com/asp-net5/creating-and-publishing-a-nuget-package-for-asp-net5-and-dnx/
http://stackoverflow.com/questions/30032370/how-to-nuget-pack-vnext-class-library
Also have in mind this shortcoming when building NuGet packages with VS 2015.
As for Beta7, we are aware of this new vNext Beta and we'll update our public UI for ASP.NET MVC 6 Beta feed to work with it soon. Additionally, in the coming weeks my colleague Stefan will update the blog to illustrate how the project from it can be deployed to a Linux or a Mac machine, so stay tuned.
Best regards,
Sebastian
Telerik
Rank 2
Wow, I am always amazed how fast you guys are!
I am aware of how to build vnext libraries, but there doesn’t seem to be project.json in the source code either. Could it be that I am simply looking at the wrong place (telerik.ui.for.aspnetmvc.internal.2015.2.827.commercial.zip and telerik.ui.for.aspnetmvc.2015.2.902.commercial.zip)?
Thanks
Rok
If you want to build your NuGet package from an ASP.NET 5 MVC project you have, you need to use the project.json file from the project itself for this purpose, as explained in the resources I liaised in my previous response.
Let me know if I am missing something.
Regards,
Sebastian
Telerik
Rank 2
I guess there might be some misunderstanding :) ,
I don’t always target the same dnx version as you do (some of my things are on nighty vnext builds), so I would like to build Kendo.Mvc package myself in order for it to even have a chance to work. If all the versions of all the included packages dont match exactly nothing works ( Multiple assemblies with equivalent identity have been imported: '<in-memory assembly>' and '<in-memory assembly>'. Remove one of the duplicate references.).
I realize most of the time it won’t work without me changing the code to accommodate for underlying framework changes and refactorings, but it need to account for those in my stuff anyway.
We don't offer project.json file as part of the UI for ASP.NET MVC 6 Beta distribution. The reason for that is the vNext Beta versions constantly introduce breaking changes with each subsequent update, and we constantly need to update our Beta to keep pace. We do that for "official" vNext Betas, but we cannot do it for nightly vNext builds.
Therefore, even if we include project.json file, if our Beta produce doesn't work against the latest vNext nightly build (due to namespace changes or other breaking changes, which happens very often so far), you won't be able to use it.
I hope you understand our position. I'll forward your feedback to be taken into account by our devteam for the future RC and RTM vNext release, when we could consider adding project.json file to the distribution.
Kind regards,
Sebastian
Telerik
Rank 2
I sure do :), thats what I meant by "I realize most of the time it won’t work without me changing the code to accommodate for underlying framework changes and refactorings, but it need to account for those in my stuff anyway."
The ASP.NET MVC 6 source is a different code base than the existing wrappers. We don't currently ship it as part of the package.
We'll start shipping it with when MVC 6 hits at least the RC state. The changes for each beta are quite substantial and we don't think it will be useful to base any code off it.
Regards,
T. Tsonev
Telerik