Ext.Net and ASP.NET 5 (vNext)

Page 1 of 2 12 LastLast
  1. #1

    Ext.Net and ASP.NET 5 (vNext)

    Hi,

    yesterday, MS released VS 2015 (Keynote: Visual Studio 2015 - Any app, Any developer) and we planned port our application to ASP.NET 5 vNext and ASP.NET MVC 6. So we have a question, will Ex.Net for MVC work with that thechnologies?
  2. #2
    Hi Andrey,

    Last week I tried to build the Ext.NET solution in VS 2015 and it built flawlessly. We even add a VS 2015 .sln in the SVN trunk.

    Though, we have not tested Ext.NET with ASP.NET 5 and MVC 6 intensively. Just some basics. But it is something we are going to support, definitely.

    If something doesn't work with ASP.NET 5 and MVC 6, please report to us and it will get a high priority for fixing.
  3. #3
    there is no thumbs up so I just wanted to say: thanks in advanced! Looking forward to it!
  4. #4

    Doesn't work

    We create a test ASP.NET MVC 6 (beta) project, the was some controller and view (Home, About, Contacts). Projects was builded and runed in browser, shown this pages.

    When we add Ext.Net in Nuget packages manager, project was builded, but pages not showns in browser. There was error:

    An unhandled exception occurred while processing the request.
    
    ReflectionTypeLoadException: Íå óäÃ*åòñÿ çÃ*ãðóçèòü îäèÃ* èëè áîëåå çÃ*ïðîøåÃ*Ã*ûõ òèïîâ. ÎáðÃ*òèòåñü ê ñâîéñòâó LoaderExceptions äëÿ ïîëó÷åÃ*èÿ äîïîëÃ*èòåëüÃ*ûõ ñâåäåÃ*èé.
    â System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
    
    Stack Query Cookies Headers Environment
    ReflectionTypeLoadException: Íå óäÃ*åòñÿ çÃ*ãðóçèòü îäèÃ* èëè áîëåå çÃ*ïðîøåÃ*Ã*ûõ òèïîâ. ÎáðÃ*òèòåñü ê ñâîéñòâó LoaderExceptions äëÿ ïîëó÷åÃ*èÿ äîïîëÃ*èòåëüÃ*ûõ ñâåäåÃ*èé.
    â System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
    â System.Reflection.RuntimeAssembly.get_DefinedTypes()
    â Microsoft.AspNet.Mvc.DefaultControllerTypeProvider.<>c.<get_ControllerTypes>b__6_0(Assembly a)
    â System.Linq.Enumerable.<SelectManyIterator>d__1`2.MoveNext()
    â System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
    â Microsoft.AspNet.Mvc.Core.ControllerActionDescriptorProvider.BuildModel()
    â Microsoft.AspNet.Mvc.Core.ControllerActionDescriptorProvider.GetDescriptors()
    â Microsoft.AspNet.Mvc.Core.ControllerActionDescriptorProvider.OnProvidersExecuting(ActionDescriptorProviderContext context)
    â Microsoft.AspNet.Mvc.Core.DefaultActionDescriptorsCollectionProvider.GetCollection()
    â Microsoft.AspNet.Mvc.Core.DefaultActionDescriptorsCollectionProvider.get_ActionDescriptors()
    â Microsoft.AspNet.Mvc.Routing.AttributeRoute.GetInnerRoute()
    â Microsoft.AspNet.Mvc.Routing.AttributeRoute.RouteAsync(RouteContext context)
    â Microsoft.AspNet.Routing.RouteCollection.<RouteAsync>d__9.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    â Microsoft.AspNet.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Diagnostics.Entity.DatabaseErrorPageMiddleware.<Invoke>d__6.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    â Microsoft.AspNet.Diagnostics.Entity.DatabaseErrorPageMiddleware.<Invoke>d__6.MoveNext()
    --- ÊîÃ*åö òðÃ*ññèðîâêÃ* ñòåêÃ* èç ïðåäûäóùåãî ðÃ*ñïîëîæåÃ*èÿ, ãäå âîçÃ*èêëî èñêëþ÷åÃ*èå ---
    â System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    â System.Runtime.CompilerServices.TaskAwaiter.GetResult()
    â Microsoft.AspNet.Diagnostics.ErrorPageMiddleware.<Invoke>d__4.MoveNext()
    May be you can give an step by step instruction how to setup MS VS 2015 ASP.NET 5 MVC 6 project with Ext.Net?

    We look at project but found only reference to Ext.Net, we think it is not enough to correctly work our application? There must be handler or some think like this?
    Attached Files
    Last edited by geoffrey.mcgill; Jul 23, 2015 at 12:36 AM.
  5. #5
    Hello,

    When Ext.NET 3.2.0 was released, VS2015 had not been released yet, so the NuGet packages really might not work correctly out-of-the-box just now.

    Thanks for reporting the problem, we will bear in mind that the NuGet packages must also be compatible with VS2015/ASP.Net 5/MVC6 when we update them.

    EDIT: Have you tried downloading latest Ext.NET SVN and running MVC examples explorer on VS2015?
    Fabrício Murta
    Developer & Support Expert
  6. #6

    No

    No, we didn't try it. We need that Ext.Net work with new version of ASP.NET 5 and MVC 6, I think there is no problem with old version of ASP.NET in VS 2015, it is support .NET 4.5.
  7. #7
    That's what I'm trying to say. If you build SVN version of EXT.NET from VS2015, with the VS2015 .sln file provided, you'll probably be able to run the generated DLLs on ASP.NET 5 + MVC 6.

    Packages you pull from NuGet will bring pre-compiled binaries from before VS2015 release, so nothing there will be built for newer versions of ASP.NET.

    That's why I asked if you tried to build from latest SVN sources. As a premium customer, you have the benefit of the last minute updates thru the SVN code base.

    That is, unless you find a bug on the SVN build itself. As far as Daniil tested, it works fine so you might not have a problem with it.
    Fabrício Murta
    Developer & Support Expert
  8. #8
    Hello,

    I've created two feature issues on gitHub:
    - #854: .NET Framework 4.6 support
    - #855: ASP.NET MVC 6 support

    We'll update this thread as soon as we have them implemented.
    Fabrício Murta
    Developer & Support Expert
  9. #9
    Hi,

    ok, thanks, we will waiting for.
  10. #10
    Added .NET v4.6 build configurations in the revision 6526 (trunk). It goes to 3.2.1.

    Review of a possibility to support MVC 6 is to be done yet.

    For the beginning - no final (non-beta) release of MVC6 yet? In my best understanding there isn't. The latest MVC6 release on NuGet appears to be "6.0.0-beta6":
    https://www.nuget.org/packages/Microsoft.AspNet.Mvc

    Most likely, MVC 6 support won't go to 3.2.1, but I am going to start investigating anyways.
    Last edited by Daniil; Aug 17, 2015 at 3:57 PM.
Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions