We currently are running moss 2007 for an enterprise internet facing site. The site's main functionality is surfaced using FAST search with MOSS 2007 used for the cms aspects. We find that the performance and development experience inside of MOSS to have been quite painful.
We are planning to migrate to MOSS 2010 but the plan is to use this as a data store only and to seperate the architecture into an MVC web application front end, with MOSS being used as a repository for the data. MOSS administration will continue to be the same but our front end rendering/logic will be a lightweight aspnet mvc site.
Would really appreciate others views on this as an idea?
As answered on SharePoint.SE
This can of course be done, but with some changes to Sharepoint app. You can check this out that does exactly what you're intending to do and may help you lots while doing it because it has a step by step tutorial how to achieve it.
End product (www.TheMedicineCabinet.co.uk) is an Asp.net MVC application running inside Sharepoint context and using Sharepoint as the backing store.
Related
I am a developer with .net.mvc, angular background. We have some application developed in mvc, angular.
My question is
1. Recently my company want to do the development on share point online(not on premise). I want to develop an app either in angular\MVC which can be deployed and accessed from share point. The app basically calls one of our on premise database displays in a grid. It also involves some crud operation.
Can anyone suggest any ideas for this.
Tried reading through some sites but doesn't helped.
Create SharePoint provider hosted add-in so you could use MVC project web template(a .net MVC project), so you could develop based on your existing .net knowledge.
get started
You could host provider-hosted add-in(MVC web) in azure.
https://www.dmcinfo.com/latest-thinking/blog/id/9543/how-to-create-a-sharepoint-online-provider-hosted-app
Hey Sorry Your question is getting attacked but I believe I have an approach for you.
Normally youd be able to just create a server side webpart but since you are online you wont be able to use MVC and will need to leverage front end solutions or the SPFx Framework.
If you want to go a more pure javascript route you can create an Angular Application like SPJEFF has done. He has built an Angular App that leverages the SharePoint API and runs inside a content and media webpart that you can embed into the page. Please see his blog post for more info. https://www.spjeff.com/2018/12/25/video-angular-2-cli-todo-list/
Your next option is the SPFx route. Its pretty mature for the online community and constantly updated. Heres a quick read on why you should use it. https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview
Please message if you have any questions.
I am in the process of developing several data entry forms that the client has asked to be accessible through the SharePoint interface (2007 WSS version).
The forms will, among other requirements, consist of multiple drop downs that have to be loaded from tables in SQL Server. These lists of data are updated frequently through a process that sucks data in from Great Plains.
My inclination is to create a Web Part Page with a Page Viewer Web Part and go full screen like this: http://blogs.msdn.com/b/malag/archive/2008/09/15/story-of-a-mischievous-page-viewer-web-part.aspx
...and then to do the pages in ASP.NET MVC3. Is there a better story than this? The integrated SP development paradigm seems like waaaay more overhead.
This sounds like a common issue with developers new the SharePoint paradigm, especially for 2007. The short answer is that your solution will be the quickest way to get to where you want to go but isn't the "cleanest".
The other option is to create a SharePoint Solution and publish an application page to the _layouts directory. A quintessential "hello world" example can be found at http://msdn.microsoft.com/en-us/library/bb418732(office.12).aspx.
New SP developers will find the hardest transition with deployment. The WSPBuilder codeplex project http://wspbuilder.codeplex.com/ has become the industries default solution for doing this. An example of using this can be found at http://www.greggalipeau.com/category/sharepoint/wspbuilder/.
For you I would say the key words are Application Pages and WSPBuilder.
I am kind of new to SharePoint and have so far mostly worked with WebPart development. After two week or so i will have to work on an assignment where i need to know InfoPath and workflow
can some one point me to some articles or help to get me started on that ? Also ,It would be good to know which topics I should cover while i am on the learning path ?
thanks,
Nikhil
How to: Design InfoPath Workflow Forms
There are several basic steps to
designing a Microsoft InfoPath 2010
form for use with a Microsoft
SharePoint Server 2010 workflow
Introduction to using workflows with InfoPath forms
What are workflows? Ways to use
workflows with InfoPath forms;
Workflows that are included in
SharePoint sites; Support for custom
workflows in SharePoint
When I started workflow development, the book 'Workflow in the 2007 Microsoft Office System (Apress)' was a great help. Since you have two weeks left, reading that book might help you a lot.
It covers SharePoint Designer workflows, workflows developed in Visual Studio (2005 but 2008 is not that different) and workflows with custom initiation/assocation forms.
I have a need to add business reporting for an application I am working on. I have found very little in the way of support for MVC natively. I would like to get a feedback on tools that people have used, how they used it (native or hybrid) and if possible links to examples demonstrating integration.
I'd like to get feedback on use of
Crystal Reports
SSRS
Telerik
MVC Reporting Solutions
SSRS - requires hybrid application with winforms page hosting the report
Telerik - ???
Crystal Reports - requires hybrid application with winformats page hosting the report
FASTREPORT®.NET - has asp.net support but vendor has not tried and does not support MVC.
Here's what I did a couple years ago to get a SSRS report to run in MVC.
http://dvdtracker.livejournal.com/1810.html
Sorry for late reply, but I've found it when searching for the documentation regarding my project. Currently I use Perpetuum SharpShooter and it works in my MVC application well (after I spent some days to make it work as I need). Maybe it will be helpful for someone.
Telerik says their report viewer in the web forms product does actually work in MVC (they have a statement on their web site that the ASP.NET AJAX framework works in MVC with some special components, and I have used it in an MVC app and with what I've used, it does all work for me).
SSRS does work in MVC if you use web forms and do not use an MVC view; this is still a possibility. You have to setup the form as ASP.NET does for you, use a form with runat="server", etc. But I did get this to work.
I don't know about Crystal.
I'm evaluating the options for a CMS in ASP.NET MVC. I'm currently working on a multi-tenant app that requires CMS functionality. I've been looking at N2, Mojoportal etc, but I'm also interested in what SharePoint Services could bring to the table. Specifically I don't want a SharePoint site but rather I'd like to potentially use the sharepoint object model, db tables, etc. to form the core of the CMS.
Is this possible with SharePoint or am I going down the wrong path? I've not had much experience with it.
SharePoint is not an ASP.NET MVC application, it's all web forms. There is the SharePointMVC CodePlex project that attempts to bring MVC to SharePoint.
At the end of the day you are very likely to need to follow the 'web forms' way of doing things sooner or later with SharePoint. So if MVC is a requirement I would not use SharePoint. However your requirements should probably be around what the customers want, not what technology to use?
I also wouldn't take the approach of using SharePoint's back end only. See this question for some good reasons why.