Why does this code
View
Worked in Laravel 4.0 and not anymore in 4.1?
One possibles reason from http://laravel.com/docs/releases:
Laravel 4.1 features a totally re-written routing layer. The API is the same; however, registering routes is a full 100% faster compared to 4.0. The entire engine has been greatly simplified, and the dependency on Symfony Routing has been minimized to the compiling of route expressions.
Related
After upgrading from 5.2 to 5.4 it seems the 'addContainerExtension(..) method has been completely dropped since 5.3.
We relied on this method for injecting our own custom rules. The method does not seem to have been marked deprecated - its purely missing from the API
Our usage of this method is
for (ProjectDefinition pd : context.projectReactor().getProjects()) {
pd.addContainerExtension(ruleSet);
pd.addContainerExtension(testExecutionService);
pd.addContainerExtension(resultProvider);
}
Any suggestions / help appreicated ?
This API was used to inject some components from the scanner to each module pico container (mainly MavenProject). We have dropped this dangerous feature.
But you don't need to use this to contribute your own rules. Simply pass your extensions in the getExtensions() method of your Plugin class.
Soon i will be starting to work on a small to medium web project. I will be the only developer to work on this project. So i am looking for pointers towards some design decisions/tools/technology. I would like to use asp.net MVC for this web project (the reason being this project has got good chance to grow a lot, therefore thinking more maintainable).
We use oracle as our backend and configured enterprise application data access block to use with odp.net and seems to have worked well. But all of our previous projects were typically asp.net web forms/windows forms.
So with mvc, is it better to use ORM like nhibernate than DAAB?
I have gone through this article, but still confused.. Thanks
does anyone have good links or tips on best practices concerning migrating from ASP.NET Webforms to ASP.NET MVC?
We have a large webforms application that we would like to piece by piece migrate to MVC. Here is our current setup.
Two big Webforms project (VB)
Multiple class libraries and services (C# and VB.Net)
Subsonic 2.2 Data access layer
SQL Server 2008 DB
We are considering the following:
Keep the classic webforms project running as is for now while developing.
Create new MVC project based on MVC 3 with Razor view engine
Use Nhibernate (Repository pattern) DAL
Convert/build the existing functionality module by module in the MVC project
Replace some functionality in the old webforms project with new MVC modules if possible. Integrate via eg. Iframes.
In time the new MVC app will replace the old webforms project entirely.
We would like to keep the DB as is so we also need a tool to create the Model based on the DB.
Is this a possible solution?
WebForms applications use server-side session a lot because most of the server controls use it internally. You will not be able to use any of the server controls that you used in WebForms in MVC3 (atleast without some tinkering).
MVC3 promotes the use of restful architecture, where any state is maintained in html or url or cookies, and these are reasons why I think you should revisit the decision to convert to MVC3. Do so only if it will give you a huge advantage, because I suspect you will be reinventing ground up your existing app - I suspect there will be an equal amount of effort migrating it as to while developing it new.
Again there is nothing preventing you from creating an "area" or a "region" of MVC in your webforms app, if your goal is to use MVC for future development.
If you still want to move to MVC3, take a look here
It is ok solution. Also for NHibernate you can use MyGeneration with NH plugin to generate models on top of existing DB. And it is also possible to host WebForms and MVC together in one web app. Just finished quite the same task. But used EF for DAL.
Drupal is frequently referred as a Content Management Framework, does it comply with the MVC paradigm? If it does, how Drupal implements MVC?
Thanks.
No, Drupal follows the PAC (Presentation-Abstraction-Control) model rather than MVC. There is an excellent blog post explaining this at Larry Garfield's site.
Drupal 8 now incorporates Symfony components. So this means while a Drupal 8 application is not an MVC framework/CMS as a whole, Drupal 8 modules are implemented in an MVC pattern with controllers, routes and Twig templates for Views.
No it does not.
You can however develop software using mvc architecture and there are even modules to facilitate that, but the system it self does not. maby it will in the future.
but some fundamental concepts of drupal, like the hooks, are conflicting with the mvc paradigm
No, drupal is not an MVC framework at all.
In the future I will be working with MVC with java/j2ee,hibernate,and more, but for now I have asp.net, php, python, ruby, etc. If I learn how to use MVC asp.net or MVC with a php framework, or RoR, will that help me with the Java version? I don't want to wait until I start the java project before I start really learning how to use MVC, but if the .net or php versions of mvc are so different that it will be a major relearning, then I might not use the non-java mvc frameworks.
In short, is learning MVC on one platform good for learning it on all platforms? I realize the tools and languages will be different, but my question is for general knowledge.
I hate working on things in a "special" way for a one time project that will show no future benefit.
Thank you.
MVC is all about splitting your application into 3 major parts. The model which contains most of the code that interacts with your database, the controller which accesses the model and gets the data it needs which then gets passed to the view which renders this for the user to see.
No matter which technology/framework you choose this basic principle will remain and only the technology used behind it will change.
For example if you went the PHP route and choose symfony as your web framework you would be using Doctrine or Propel as your model/ORM. If you used JBoss Seam you would be using Hibernate/JPA as your ORM and EJBs as your controllers.
Even though these 2 frameworks follow the same rules when it comes to separating logic from design they also require you to learn very different concepts to utilize them correctly.
For instance in JBoss Seam, the framework relies heavily on your knowledge of scope and stateless and stateful session beans where in symfony there is no such concept (sort of).
So whatever route you choose, there is still much to learn after you've mastered the concept of MVC.
MVC is a basic software architectural pattern. It's just an abstract concept. Its specific implementations will differ based on the language and platform you are using (as does everything), but the basic concepts remain the same.
So in a word: yes. Learn what MVC means as a concept and you'll be able to transfer that knowledge between platforms and technologies.