There some open source MVC 2 projects out there but what are your recommended open source MVC 3 projects?
Music shop is OK for beginner. But here are few real world application which are quite good for experienced developer.
NopCommerce 2.0 based on MVC3 http://nopcommerce.codeplex.com/releases/view/51060
Sutekishop http://code.google.com/p/sutekishop/
Orchard proejct (MVC3, CMS) http://orchardproject.net/
You can use NerdDinner
http://nerddinner.codeplex.com/discussions/235392
And the 2nd project is MusicStore poject.
http://mvcmusicstore.codeplex.com/
These are 2 project you find mention in most of the talks in mix and pdcs
Related
Up until now I had been using MVC3 for my apps but with the new update of Visual Studio 2012 I got MVC4. I migrated a few of my apps and now they are broken.
I noticed that the new project template for an Internet application creates a ~/Content/themes/base folder.
And yet, up until now I had been accustomed to use the App_Themes folder for that. In fact, with VS.2013 you can use "Add ASP.NET FOlder | Themes".
So I am now confused with MVC4, has It deprecated the App_Themes folder (which seems more appropriate to me than ~/Content) ? or is there a significant difference?
App_Theme come from ASP.NET Platform and one goal of mvc is get a clean html code
One of the things that ASP.NET MVC is missing is the ability to
easily implement Themes. The older, more mature standard ASP.NET
framework includes theme support via the App_Themes folder; however
limited it can be, it’s still more than ASP.NET MVC currently has.
Well, at least until I wrote this little custom ViewEngine and
ControllerBase class to help out and allow us to very easily implement
Themes within our ASP.NET MVC applications
take a look this helpful article this link
When I installed MVC4 beta on a development PC, it had a template for SPA (Single Page Application). Today on a different PC with the same setup (VS2010 SP1, win7), I installed MVC4 RC but no longer is the SPA template available (see image). Any one else having this issue? or is this a documented change that I could not find?
Changes from ASP.NET MVC 4 Beta
The major changes from ASP.NET MVC 4 Beta in this release are summarized below:
Removed ASP.NET Single Page Application: ASP.NET Single Page Application (SPA) shipped with ASP.NET MVC 4 Beta as an early preview of the experience for building applications that include significant client-side interactions using JavaScript. SPA won’t ship with the final MVC 4 release, but will continue to evolve outside of the MVC 4 release. Check out the ASP.NET SPA home page for details.
...
http://www.asp.net/whitepapers/mvc4-release-notes
P.S., Wow I am glad that I didn't use it for an app I build right now. I was considering it 3 months ago, but decided not to risk it because MS said that it is experimental.
You can get the SPA template in the Fall 2012 update. More information on the template here and here.
It`s very risky now
For example if you try to run it with System.json for serialization it runs well with WebApi and DBDATAContext methods but it`s impossible to use it with Entities relationship entity circular errors and so on. (There is a solution to change private access of method get, but would be too much work to have to change in all the access methos of all your entities.
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 am currently learning MVC2. actually working on my first MVC2 project.As the MVC3 beta is launched and available to download. please suggest me should i use MVC3(Beta) or continue with MVC2 and second thing is, if i move to MVC3 then what major advantages i will get from it.
My project is an ERP application.
Please suggest me what should i do.
Thanks
I suggest you take a look at this blog post from Scott Gu :
http://weblogs.asp.net/scottgu/archive/2010/11/09/announcing-the-asp-net-mvc-3-release-candidate.aspx
To name some advantages, you can use the Razor View Engine, which depending on your requirements, it will make your view code nicer. I believe that's the case for an ERP System.
This is not 100% mvc3 related, but with the RC you get NuGet installed with it, if you're planning on using external libraries to help you out, that's a great way to manage them.
Partial Page output caching is a great feature for systems that share bits and pieces across different ui's.
Unobtrusive JavaScript and Validation is also another great new feature that will help you keep your code's maintainability among other benefits.
MVC3 also has some benefits from the dynamic aspects of .NET 4, and that also helps you keep your view code cleaner.
And my end point would be, MVC3 is already on RC stage....it already has Go Live license and support...if you're learning, I would suggest learning the latest, you will get all the knowledge you need to use mvc 1 and 2, and also the new things about mvc 3.
One factor is the release date of MVC 3 compared to the release date of your application, i.e. you should not ship an application based on a beta version of MVC.
If you switch to MVC 3 beta, you should be aware that there may be changes in the final release, so you may have to make changes for each version until the relase, and your application is only guaranteed to work with one specific pre-release version, until the final release of MVC 3.
We are planning to upgrade our technology to VS 2010. But I wonder if the MVC 2.0 is working properly since it has many issues raised from software developer who used it please see here: http://aspnet.codeplex.com/releases/view/41742.I want to use MVC 1.0 in VS 2010 is it compatible?
Indeed as Robaticus said, MVC2 works well and you shouldn't be afraid to use it... but if you really want to stick with MVC 1.0, take the relevant MVC DLLs and copy them into a known lib folder, and then directly link your project to those. By doing this, you will be directly linking to the old MVC libraries which will still work just fine. Just don't link to any of the MVC 2.0 libraries that will undoubtedly be sitting in the Global Assembly Cache.
MVC 2 works great; I'm using it right now. There are some very slight changes to the signature of some framework components, but overall works great. Would recommend 2 because they have a lot of new features to take advantage of and make your life easier.
If you had to, MVC 1 and MVC 2 they give you the source code, which you can include and use in your project, so you are always covered there.
MVC 1 and MVC 2 are compiled in .NET 3.5 SP 1 version, so you may be able to use the MVC 1 DLL directly...
HTH.