I am creating reusable user controls in Asp.Net MVC 3 which will be used in different MVC project.
I know We can create Helper in MVC. but i want to go with Partial view. As we can create usercontrol library in Asp.Net and use it across all application. I want to do the same thing in MVC 3.
I found below article which is neatly explain. I tried to implement it , but it looks to be outdated as
PrecompiledMvcEngine is not found in nuget.
can anybody explains me how to do it in MVC3.
Reusable UI Controls
I also used Razor Generator but it will only create my view code in class.
what about the controller in that case.
Also how to refer other assembly view in current application?
UPDATE
I think this is a more preferred and more current solution that uses built in functionality of MVC Areas that will save a lot of hassle in the future,
http://nileshhirapra.blogspot.com/2012/02/aspnet-mvc-pluggable-application.html
I think this is prefered because you can use
#Html.ActionLink("SomeAction", "SomeController", new {area = "SomePluginArea"})
Register Custom routes in your plugins using the AreaRegistration
OLD ANSWER
This is an old article but the same principle still applies I think this is what you want to achieve right?
http://www.wynia.org/wordpress/2008/12/aspnet-mvc-plugins/
Code sample:
http://www.wynia.org/download/aspnetmvc-plugin-poc/POC.MVCPluginDemo.zip
I recently joined a group that manages a Classic ASP web application. It has been working fine for our group's need. However, a decision was made, before I joined, to move to ASP .Net. Since we are mostly ASP developers, we write code in ASP .Net as we would in Classic ASP (for the most part). Would it be possible to introduce MVC to this application/project?
Thanks!
Yes, it is possible to use MVC in a traditional WebForms project. I migrated a large WebForms project to MVC 2 a couple of years ago, and here are my findings (I have updated them to reflect MVC 3)
Make sure you have .NET 4.0 installed, as well as the MVC 3 framework and VS extensions.
Create a new blank MVC project to use as a reference.
Look at the default web.config for the reference project. You basically want to use the reference web.config, and merge in stuff you need from your current project.
Look at the reference global.asax.cs. Similar to the above, you want to merge the changes in the reference .cs into your current application's global.asax.cs.
You will need to add the following references to your web project:
System.Web.Abstractions,
System.Web.Extensions,
System.Web.Helpers,
System.Web.Mvc,
System.Web.Routing
You can enable the VS extensions by changing the ProjectTypeGuids:
In Solution Explorer, right-click the project name and select Unload Project. Then right-click the project name again and select Edit ProjectName.csproj.
Locate the ProjectTypeGuids element and add {E53F8FEA-EAE0-44A6-8774-FFD645390401}.
Save the changes, right-click the project, and then select Reload Project.
Add the following standard folders for MVC content:
~/Views
~/Views/Shared
~/Controllers
~/Models (for your view models, optional)
~/Content (for CSS and images, optional)
~/Scripts (for JS, optional)
Additional notes:
If your existing WebForms relies on web.config settings for authorization (such as preventing unauthorized users), this won't be recognized by MVC actions, because routing works completely separately from the WebForms authorization. Use AuthorizeAttribute to require authorization, or constrain actions to certain roles or users. You can even specify global filters so you don't have to apply this attribute on every single controller or action.
There may be additional considerations for making MVC work with IIS versions prior to 7, or with application pools that use the Classic pipeline. Consider using IIS 7+ with Integrated pipeline.
My notes above mainly involve getting the baseline of MVC working, which uses ASPX views. ASPX views use the same markup as the ASPX files you are used to in WebForms. You can also use the new Razor syntax (primer), which I highly recommend. You can use both ASPX and Razor view pages at the same time. However, you cannot use an ASPX master page on a Razor view (or vice versa). Also, MVC will find and use ASPX views before Razor views, so if you upgrade a view to Razor, delete the original ASPX. You will need to do a little additional work to enable Razor views. I'm trying to find my notes for enabling Razor. I'll update when I find them. Once you do have Razor installed and working, you can use this tool by Telerik to convert ASPX to Razor.
Here is a question on SO about a problem I'd had while upgrading. I'm only providing it because it covered some of the points I mentioned above in more detail. However, I was upgrading to MVC 2 at the time, so some of this stuff is out of date.
The short answer is yes it is possible.
Scott Hanselman has written about this topic before.
Depending on the skills in your team, you may well find it difficult to get up to speed - it is possible to write clean MVC style code in Classic ASP but most people don't.
It is of course technically possible. However, it sounds like it would be a cultural shock, as MVC works quite a bit differently than Classic ASP or ASP.NET WebForms. I think it would be worthwhile to do - or just stick with ASP.NET WebForms if that seems more natural. But if you've not yet fully committed to WebForms, MVC seems just as easy to move to, IMO.
Yes. I worked on a project that began as plain ASP.NET and later added some ASP.NET MVC pages. Eventually we liked MVC so much more that we eventually migrated all of our WebForms pages to use MVC instead. But the whole time, the two systems worked very well together.
Here's the only real gotcha that I can remember running into: WebForms works by having the entire page encased in a big <form> tag. Since HTML doesn't allow you to have nested <form> tags, you typically can't use MVC forms inside of a WebForms page. Either keep your WebForms pages separate from your MVC content, avoid using HTML forms in MVC content that may appear on a WebForms page, or use popup dialogs for your forms that get created outside of the WebForms DOM area.
I'm fairly new to MVC 3 and and looking for a grid component that allows sorting and paging, but will also use progressive enhancement so provide fully AJAX based sorting and paging.
Ideally I'd like the generated markup to be very clean and customizable with minimal JS embedded on the page
Get a look at http://datatables.net/
There are various nuget packages and codeplex projects developped to easilyintegrate these with asp.net mvc such as this one: http://datatablesmvc.codeplex.com/
We have an existing ASP.Net Web Application. I would like to create an ASP.Net MVC Razor Application where the two applications will work together. A single Master Page would contain menu items that can call .aspx pages as well as Razor .cshtml pages.
I have seen an example using MvcContrib Portable areas utilizing Routing. This particular example has .aspx pages in both (the MVC was not Razor).
Is there an example out there that will show the two running side-by-side and the MVC is Razor? It would be best if I could download a visual Studio Solution so that I can run this.
I am not sure if the MvcContrib way is the latest and best way to achieve this.
I do not want to go Hybrid!
You don't need any other external librarry. You can always convert the existing ASP.NET web forms Project to be a Hybrid one which uses webforms and MVC. You need to add the required MVC assembly references and make some changes to the web.config and you are all set. Scott has a simple and awesome blog post about this where he explains how to do the conversion.
I scribbled a note about how to enable the MVC specific Context menu( Add Controller / Add View) in the hybrid project after conversion here
I'm asp.net mvc for my project and now I have to show a couple of reports using the ReportViewer control. I need to specify a couple of properties before rendering the report ie. ReportServer Url.
Is it possible to achieve this using asp.net mvc?
You can't use reportviewer control in asp.net mvc because it needs postbacks.
But you can use it to generate an image and show it (some googling should give you results about how to accomplish that).
Another option - you can make a hybrid application (web forms + mvc).
And another option - you can try javascript charts. Google charts looks good for example.