As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am to develop a website for a IT company, I want to use ASP.NET MVC 3 to develop it I also want to use a CMS with it so that it is easy to change the content of the site, without having to go into the codes.
I want to use MVC 3 for this.
Can anyone help me in deciding which CMS should I go for ?
My requirement is to create a website for an IT company using ASP.NET MVC 3, and use a CMS with it so that content management becomes easy.
Any ideas / help / links / will be appreciated.
Update : Now Wordpress is also available with .NET
Warm Regards
There is no "plug-in" CMS that you can use in MVC. You would have to write it yourself.
There are, however, a number of CMS's that allow you to extend them via MVC. Orchard, for example is a popular one.
There is a big difference between an MVC site that has a CMS and a CMS that allows you to extend it with MVC. You should understand this distinction, and decide which way you want to go.
It sounds like you're looking for a solution like N2 CMS. It's an API that allows you to create a CMS programmatically.
http://n2cms.codeplex.com/
You can try to use MVC Easy CMS. It can be installed as NuGet package to the existing MVC 3.0 project.
You can plug Umbraco v5 into an existing MVC site or an existing MVC site into Umbraco v5. Umbraco v5 is a complete rewrite currently based on MVC3.
The open source DD4T project (Dynamic Delivery For Tridion) provides an MVC.NET front-end to SDL Tridion WCM-managed content.
Tridion is however quite expensive, so I'm not sure I should be even mentioning it...
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm about to foray into ASP.NET Web Development and I already know some of the very basics using Visual Web Developer and some of the implementations of Web Forms. However, instead of continuing to go down the Web Forms path and mastering VIEWSTATE and all of the ugliness that comes along with it, I've decided to go the MVC route.
At this point, I'm wondering, should I continue to learn Web Forms and then move over to MVC? Or can MVC be learned independently without knowing a thing about Web Forms? What's my best course of action?
No, don't even look at Web Forms.
MVC is modeled much closer to how HTTP actually works, which makes it much easier to work with and to build today's web applications with client side scripts. Combining Web Forms and javascript is really a pain.
MVC is also much better in that it helps getting the server side structure right. It is possible to use a model-view-presenter (or controller) separation on Web Forms too, but it has to be ducked taped on top of Web Forms.
Finally, you will have nearly no use of any WebForms knowledge when starting with MVC. It's rather the other way around, the WebForms developers I've taught MVC have to be de-brain-washed from WebForms first ;-)
While much of the excitement in the .NET community is around MVC, many of the applications out there continue to be in webforms. If for no other reason, you should continue to learn webforms so that you can convert applications over to MVC.
I've been working on MVC since the 1.0 RC, but no matter where I have gone in my consulting work, if there is .NET you almost invariably will see webforms. In fact I would dare say in the enterprise the majority of applications are still in webforms.
In my view MVC is a much better platform, and webforms will probably not be supported eventually (although Microsoft continues to say it will). Still how many of us said that VB6 will go away and got burned when we find an ancient bug and have to spend days just figuring out how things work?
We're still years away from having webforms be phased out completely, and you don't want to restrict what you can and can't do because you decided MVC is the only way (your company may not want to spend the money on converting their mega-spectacular webforms app because you don't like webforms).
More knowledge never hurts, but ignorance can burn you.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I want to develop a personal blogging website using ASP.NET MVC 4.
I know that I could be using WordPress/ Joomla/ Orchard/ Umbraco/ Funnelweb, etc., instead of reinventing the wheel but I really wish to try it out myself.
I do not want my website to look like some beatle-aged archaic remain. I see plugins like Akismet/ Prettify/ Markdown/ nrelate that add amazing functionalities to your blog. But I am not really sure if I would be able to use any of these in my custom application as most of them are PHP based. I want to stick under the Microsoft roof and implement technologies like HTML5, CSS3 Silverlight5 and WCF 4.0, along with ASP.NET MVC 4. (At least thats what I plan to do)
I understand that I need to develop a scalable database design that could accomodate newer functionalities in the future. Additionally, the exorbitant focus on SEO and cross-browser capabilities is overwhelming. Permanent links for individual blogs, internal navigation, video-embedding inside posts, etc., sound like building Rome in a day
Please if you could guide me personally or direct me to appropriate resources, it would be very helpful.
I am sort of doing it right now on my own. It's not done yet but it will give you an idea: MvcBloggy.
Also, have a look at FunnelWeb source code. It's written in C# and uses ASP.NET MVC 3 I believe but it's a really good resource and easy to follow.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I know many have asked the MVC vs Webforms question many times. My question is slightly different in that I am currently updating my skills from ASP.NET2/VB.NET to ASP.NET4/C#. I am seriously thinking that I should perhaps not waste time in upgrading my Webforms skills which are Okish, but instead put the effort into starting again with MVC. I keep looking at all the properties of ASP.NET server controls and sigh !!! I do see the benefit in just focussing on web technologies such as JS, CSS and now JQuery and CSS3.
I would be interested in your thoughts?
It sounds like you are doing a clean-slate here. You are changing languages and technologies. My advice would be to identify what you feel is the best technology going forward and learn that. You are already committing to learning something new - make it the most valuable experience you can make it.
From my perspective, I would recommend MVC. Personally I feel that this is the better platform to move forward on. You will have to add quite a few auxiliary skills such as Razor, JQuery and all the rest but it will be worth it. The bottom line though is that it is what is best for you. If your environment is better served by Webforms, then that is the best choice for you.
Six months ago I changed jobs. I was previously working at a large company that was still on .NET 2.0, VB.NET and ASP.NET WebForms. I now work at a company that uses .NET 4.0, C# and ASP.NET MVC3. So, I've been through this myself.
If you understand how the web works and want complete control over the client experience, MVC is the answer without a doubt. At my previous job I would end up pulling my hair out because I hated how WebForms prevented me from creating a page with clean markup. But, a lot of people don't know how HTTP, CSS, Javascript and HTML all fit together. WebForms was a solution to that. But, it's much more fun and performant to have complete control of what you sent to your customer/client.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
Good day!
I'm planning to upgrade WebForms application and I have two possible choices:
Write it in ASP.NET MVC 2.0 with WebForms view engine and upgrade it to 3.0 when it will be out
Write it using ASP.NET MVC 3.0 RC with Razor as view engine
It seems that Razor is the only 3.0 feature I really can take advantage off for this task.
The launch date for application is Q1 of 2011 so there is a chance that ASP.NET MVC 3.0 will come out as RTM.
So, is Razor mature enough?
From what I've read I don't think upgrading a 2.0 app to mvc 3.0 will be that difficult. So I am sticking with the stable code for now, and then upgrading once a stable release of 3.0 is out. I think it will be just as much work to start with 3.0 and then fix all the little changes upon the actual release of it.
Bottom line for me is that MVC 2.0 is fully functional and works with few issues. They have not called 3.0 a stable version yet for a reason.
There is more to MVC 3 than Razor, but you aren't specific so will hold my peace.
As regards Razor, it is just a ViewEngine. No different to Spark, NHaml, etc. So even MS can get that right first time out. Is it mature? No. Mature enough? Well, at least it is not decrepit like web forms... Why write XML when you don't have to?
I am writing a new app in MVC 3 and so far, the only issue I have had is with a couple of helpers that return void. It was easily solved, see Adapting a custom Html Helper for Razor
As MVC 3 is at the RC stage, you should be fine with your time line.
The killer for me is future proofing. I am definitely going to use Razor in future, so all new stuff is best written in what I will be using.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We are looking to use the MVC Framework in our SP Application.
This is what we are trying to accomplish...
A virtual directory within the SPSite which can host and run MVC.
for e.g., /_layouts/MVC/
Any hints on the required configuration changes (if at all this is possible) will be very helpful.
This might be of interest to you
http://www.codeplex.com/SharePointMVC
I published it about 5 minutes ago.
It is basically a library to help rendering ASP.MVC inside a SharePoint masterpage.
Still early days but you get the idea.
You're going to have a hoot of a time de-inheriting everything (modules, handlers, assemblies, namespaces) in the MVC app's web.config. I would recommend that instead of trying to get MVC working inside of the same IIS web site, why not just run your app outside of SharePoint? Joel Oleson just blogged about using "widgets" or "web parts" as a form of SharePoint integration:
Joel Oleson
I have heard from the MS MVC team that there is no plans for Sharepoint to use MVC. However MVC can be used with Sharepoint with a few tweaks
The following sharepoint site, www.themedicinecabinet.co.uk, was built using ASP.net MVC 2.
This article explains how this was done
http://vspug.com/mbailey/files/2010/04/Using-ASP.NET-MVC-2-with-Sharepoint-Publishing.pdf
We've just released an opensource project that let's you use SharePoint 2010 as the backend of a site and use ASP.NET MVC3 on the frontend. We've been using the code base for the last two years and wanted to share it with the community since we're confident others would find it useful.
Documentation is still sparse - please feel free to reach out if you have any questions or need help.
http://www.slamcms.com
I would recommend running your virtual directory in it's own app pool. I'm leveraging MVC on some other Microsoft products and the app pool's Managed Pipeline Mode must = 'Integrated' for MVC.