I like to here which folder structure you prefer for your symfony projects? Do you use the new 3.0 version or do you prefer your own special one? I really like to hear your expert opinions.
I'm using Symfony 2.7.
Do you put the Resources folder in the app folder or in the AppBundle?
Do you have more than one bundle or do you prefer the one and only AppBundle?
DDD driven oder database driven?
Thank you in advance. :-)
There are many questions like yours in SO.
Symfony best practises
Symfony - Organizing Your Business Logic
Related
I hope this isn't too vague.
I am wanting to create an mvc project in which I can use in other projects. I am wondering whether I can do this with Areas. Although when trying it looks at the wrong folder for the views. Does any one know a way of doing this? or Is there a different method?
Check out portable areas, I think its exactly what you are looking for.
http://lostechies.com/erichexter/2009/11/01/asp-net-mvc-portable-areas-via-mvccontrib/
You can use EmbeddedResourceVirtualPathProvider which works for MVC views and also other content files (e.g. js/css/aspx).
We have started a new Asp .net web project. We plan to do in in MVC. Is it a good practice to use Microsoft's MVC 3 tool or is it good to define our own structure? Web site requirements are normal. Some people suggest if we use microsoft tool we will loose our control in the project????? Any problems that we may face when we use micosoft MVC 3 tool (Razor)?
no really, there isn't any problem -present and future; if you have deep knowledge about issues such as OOP, ASP.NET structure and how it works, MVC architecture, etc. I suggest you strongly use and enjoy ASP.NET MVC 3 and Razor :D
If you are new to MVC then I would suggest go through basic (or advance dependending upon how much you know) MVC tutorials before deciding arch. Things can be done in various ways and it differs from project to project. Once you build your knowledge about things like DomainModel, serviceLocator, IoC, ViewModel, Helpers, repository pattern etc. you will have better idea about which tool to use. I would start looking at some of the sample projects on the codeplex. (would not be too hard to find)
Good luck
If I said yes, would you go ahead and use it? The same goes for building a house or working on any project. What has worked for me, might not work for you. I would start from reading learning resources on here. I would also suggest reading about HTTP protocol and its stateless nature as well as looking at differences between web forms and mvc frameworks. Good luck.
I currently have an ASP.NET MVC project with several other projects, class libraries mostly. I want to create a "mobile-friendly" version of the ASP.NET MVC app that uses the WURFL library, and I just want to know if it would be a bad practice to create a separate MVC solution? Or should I have the mobile detection within the same MVC project and serve up appropriate views? I just want to keep my concerns separate from an architectural point of view. Is it bad practice to do a redirection based on device?
I think it's better to create the separate solution cause:
1. You will know for sure that users use mobile devise for see this vertion
2. Sometimes autodetection not work correctly
3. Build the new solution can be faster that setup the mobile detection on old solution
PS> Sorry for my english :)
i am pretty new to CI. been looking at few template libraries but found either they have much more than I need or not enough.
so i started to build my own. is there anything i should keep in mind? in terms of security? caching? etc etc
thank you
A template library is pretty simple to create and unless you have a need for all the stuff that one of the many available have I would just roll your own. With that said I tend to use the one by Phil the most as it matches the closest with the way I do things.
I'm developing a small cms based on asp.net mvc. I'd like to have one user interface for all editing e.g like this http://www.example.com/dashboard/{controller}/{action}etc. What is the best practice for this kind of project structure?
My suggestion is to follow the standard MVC project conventions. Of course you can write your app using different conventions but the point of conventions is that once you learn where things go it's really easy to add new things and it's really easy for others to "read" your project. I would go with the suggestions in Scott's blog.