Thursday, December 18, 2008 9:48:39 PM UTC

It's all business again.

First: I'm going to be away from (hopefully all) computers for a while

I'll be on vacation, in a very real and non-metaphorical sense. Which is awesome.

What it means for you is, if on the offhand chance you leave a comment or email me, I won't respond. Sorry, I'll be away. Sucks for you, awesome for me.

Second: ASP.NET MVC and SharePoint, together as one

It still boggles the mind how many people are searching for this term. The only thing I want to ask you, the many people who are searching for "how do I get ASP.NET MVC running underneath SharePoint," is: why? Why do you want to do this?

I'm not here to provide any answers today; instead, I'm posting this as a kind of googlebait to lure you in. Maybe it's wrong, but whatever. Why do you want to use the still-beta ASP.NET MVC framework on top of SharePoint? I honestly don't know why anyone would do this. So please, if you search for "how do I combine SharePoint with ASP.NET MVC," and you hit this page, leave me a comment! I want to get in your brain and swim around a little.

I'm pretty sure I can get ASP.NET MVC running underneath SharePoint; the only magic will be removing pieces of SharePoint from the MVC project's web.config, and (maybe) integrating with SharePoint's security (or maybe not). Besides ugprading to .NET 3.5 SP1, which is by far the most arduous step on a production farm, it shouldn't be too tricky to get this working.

Anyway, there's a somewhat rambling teaser—it's probably possible, even if I can't imagine why it would be a good idea.

Categories: SharePoint

Technorati: SharePoint

Thursday, December 18, 2008 9:48:39 PM UTC

| Comments [8] | Trackback

Thursday, April 23, 2009 4:42:02 PM UTC

OH God, help us all. That combo would cause a nuclear explosion! first we need to get rid of SharePoint's API, and JUST USE CODE!

Dave Schinkel

Sunday, May 24, 2009 5:37:50 PM UTC

I would be more interested in integrating standard ASP.NET applications (not necessarily MVC variety) into SharePoint. This way an application vendor can have it hosted in SharePoint for clients where SharePoint is extensively used or host it on its own as an ASP.NET application.
.
Where it is hosted in SharePoint, use SharePoint's features:
* MasterPage for seamless UI integration
* Append the app's menu to the SharePoint navigation
* Use SharePoint's security (using ASP.NET MemberShip security)
.
As an ASP.NET developer/consultant I know there are clients that simply will not consider SharePoint, while others are 'experimenting'. Having the ability to run an application within SharePoint as well as on its own would be a big plus for consultants and ISVs developing ASP.NET solutions.
.
I don't ever hear about such ideas or discussions. Am I nuts???

Jay Patel

Sunday, May 24, 2009 6:26:50 PM UTC

WebForms integration is a mostly solved problem, at least for simple WebForms apps

Peter

Sunday, May 24, 2009 7:14:54 PM UTC

Can you recommend any good resources for 'WebForm' integration?
.
The WebForms apps I'm dealing with mostly use MasterPages so I'm guessing it will be not so difficult to integrate, at least from a UI standpoint.

Jay Patel

Sunday, May 24, 2009 8:52:26 PM UTC

I'm on my phone so my answer will be real short. Best advice is to investigate creating your app in the _layouts folder. T hat allows it to run almost completely independent. If you want to do better you've got to dig into sp dev and learn the best integration points for your specific scenario. There are a bunch of ways to half-integrate with sp

Peter

Friday, June 12, 2009 6:44:40 PM UTC

I don't see the point of all the MVC buzz either. Maybe it's one of those technologies we should skip for now like LINQ for SQL

Tom Resing

Friday, June 12, 2009 7:12:40 PM UTC

Whoa now, let's not get hasty :) I loooooooooooooooove the MVC, I just don't see the point of building anything large enough to necessitate MVC inside of SharePoint. I'm a big IFrame/whatever-that-webpart's-called fan, and I think that once you start reading and writing to a SQL Server database, there's no reason to be using SharePoint anymore.

But to be absolutely clear: I really, really like ASP.NET MVC, and I don't think it's hype, I think you can 'get really good' at building apps and websites of all sizes, something I don't attribute to SharePoint.

Peter

Friday, April 16, 2010 9:03:02 AM UTC

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

martin bailey

Name
E-mail
Home page

	Remember Me
Comment (Some html is allowed: `a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u`) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.
Enter the code shown (prevents robots):
Live Comment Preview

Syndication

Posts on this page

Peter Seale's weblog

Opinionated SharePoint | the Joys of PowerShell | Awesomeness

First: I'm going to be away from (hopefully all) computers for a while

Second: ASP.NET MVC and SharePoint, together as one