This project is read-only.


Topics: General
Aug 29, 2014 at 2:41 PM
Talking about next version, some people began to discuss about ASP.NET VNext :

I would like to have your thoughts:
What useful features ASP.NET VNext can bring to Orchard?
Or How such a CMS would have been built if we already had the features of ASP.NET VNext?

Here are some topics:
Dynamic compilation
NodeJs like
    Packages : kpm
Dependency Injection        
Data Access
    Entity Framework
Aug 30, 2014 at 4:20 AM
Edited Aug 30, 2014 at 4:21 AM
It would be my wet dream to rebuild Orchard and leveraging everything that comes with ASP.NET VNEXT, and maybe using Entity Framework and a Document DB architecture on top of that, like what Sebastien did with YesSQL on top of SQL Server (I don't know if he uses an ORM for that or not - probably unnecessary for a Document DB, but at the same time exposing access to the DB through EF seems useful when as a module developer you want to work with a relational model).

With Roslyn it seems that we can scrap all of the dynamic compilation code.
Nov 22, 2014 at 6:14 PM
@sfmskywalker the wet dream has started
Nov 23, 2014 at 8:20 AM
Edited Nov 23, 2014 at 7:19 PM
This is also for me a wet dream hahaha

An interesting feature of ASP.NET I loved is the new razor Tags that allow to hide all the ugly Razor Helpers and see only clean html there. It would be nice to see core templates and theme machine moving to this.

Related to IoC I'm not sure ASP.NET VNEXT is better than Autofac. I would make efforts in this direction only if it shows clearly advantages

Orchard command line commands looks also a good candidate to integrate on what vNext offers for running actions through command line

Related to access data and EF I agree with you as I exposed in this looong discussion :) :

Non directly related with ASP.NET VNEXT two points:
As I have exposed a few minutes ago also at the access data discussion I would make an extensive use of async/await mechanism for improving performance in a cloud VM where performance of monothread actions is specially penalized in comparison to multithread ones. Something that doesn't happen in physical machines.

Finally, it would be great to look how to fit something like Polymer in Orchard
Nov 23, 2014 at 10:47 AM
Here are some interesting sessions presented during the last Orchard Harvest conference :

Orchard 2 0 Vision:
Sebastien Ros talked about vNext.

The Future of Widgets :
Steve Taylor talked about Polymer.

Introduction to ASP Net vNext:
By Eilon Lipton and Scott Hunter

Developing with ASP NET vNext:
By N. Taylor Mullen
Nov 23, 2014 at 11:00 AM
Please keep autofac :) MS always have slightly odd ideas about IoC
Dec 4, 2014 at 10:58 AM
A VNext implementation has started here.

@PaulDevenney At the moment I have everything running with the built in DI container, though this may change later.
Jan 18, 2015 at 5:03 PM
Just pushed some cool updates to the VNext stuff.
  1. Wired up all the DI so the plugin architecture works. There are some perf issues I need to investigate, but it works at the moment.
  2. Added Middleware, taking the work that was done on the Owin branch.
  3. Added some middleware to test projects.
  4. Controllers now being served up with dependencies injected in to them when they are required.
Next up:
  1. Re-factor the way Settings are injected in to use IConfiguration, thus allowing people to use Yaml or JSON or whatever.
  2. Turn the Demo Module in to a sample site.
  3. Re-factor the way we talk to the file-system. Look to use the VNext abstraction of the File system API's.
Apr 13, 2015 at 8:02 PM
This project is looking great! Will ASP.NET v5 features like Rosyln compilation and OWIN support make it easier for in-place updates of Orchard and/or individual modules? I know there has been discussion for a long time about in-place upgrades but things like app pool resets make it difficult.