Tag Info

Hot answers tagged

2

I would strongly recommend not using SharePoint at all in this scenario, because: backup and restore is more challenging because you have to consider recovering the SharePoint boxes as well as SQL databases (and getting that right can be hard) you have to consider SharePoint's various restrictions on list sizes, file upload sizes, site collection sizes, ...


2

Take a look at this post. Since SharePoint 2013 is built around the app model you have the option of using MVC4 MVC3 ASPX Web Forms or Silverlight. On SharePoint 2013 application pages or websites will not be integrated with the SharePoint Site as in 2010. You can read the below related post and see how you can do your mvc app. ...


2

Your business requirements should dictate the technologies you use on this or any project. To make the right decisions on this you really need an experienced SharePoint architect. Building a SharePoint project of any complexity without one will almost certainly end in tears. That said, SharePoint is a huge product, and your team will almost certainly have ...


2

As a .Net developer, you can get an idea of SharePoint using the following links, http://msdn.microsoft.com/en-us/library/ff829215.aspx http://sharepoint-tutorial.net/post/2013/01/21/sharepoint-2010-development-overview.aspx http://www.c-sharpcorner.com/uploadfile/dhananjaycoder/architecture-of-sharepoint-for-Asp-Net-developers/ ...


2

ASP.NET MVC is a completely different animal from SharePoint. For a start, SharePoint is built on ASP.NET WebForms. If you want to migrate an app from MVC to SharePoint, your only option is to rebuild the app from scratch, using things SharePoint has to offer, such as Features, Lists, Workflows, etc. If you have to merely host the MVC app on the SharePoint ...


2

Any list you deploy as part of you App will be added to the AppWeb (yes such a web is created when you add SharePoint items to your App, even though the App is Autohosted) not to the HostWeb


2

Ok so I found Microsoft.Identity.Extentions here: http://download.microsoft.com/download/0/1/D/01D06854-CA0C-46F1-ADBA-EBF86010DCC6/MicrosoftIdentityExtensions-64.msi That's needed for http://nuget.org/packages/AppForSharePointWebToolkit/ which creates TokenHelper.cs file. I still don't know why it didn't appear automatically when creating new project for ...


2

As Daniel says, if you are building an App, Provider Hosted or Auto Hosted which both have components that run off your SP2013 server, that remote part can be MVC (e.g. ASP.Net MVC4 or 5). If what you want to use is the concept, then yes you can definitely do that too. You can do SP2010 webparts (farm solutions) with a MV(C/VM) architecture, if you're ...


1

You need to have app web for that. In provider hosted app, app web is not present by default. Create an empty module or list in your app web; basically in SP project which gets created when you create a provider hosted app and then you will have context. Besides that, why do you need context of app web of you don't have anything in there?


1

Here's an update to the provider I posted earlier that supports basic crud operations against a sharepoint 2010 (and probably 2013) List // SharePointListService.js (function () { "use strict"; var module = angular.module('sharePointList', []); module.provider('SharePointList', function () { var clientCtx; var web; var ...


1

Here is a provider I created to get data from sharepoint lists: (function () { //// SharePointListService.js "use strict"; var module = angular.module('sharePointList', []); module.provider('SharePointList', function () { var clientCtx; var web; var configuration = {}; this.$get = ['$q',"$log", function ($q,$log) { var contextLoaded ...


1

This is what we are supposed to do. public ActionResult Upload(HttpPostedFileBase file) { var hostweb = HttpContext.Request["SPHostUrl"]; Uri hosturi = new Uri(hostweb); using (var clientContext = new ClientContext(hosturi)) { using (var fs = file.InputStream) { var ...


1

As I've understood it, it is possible to implement MVC into your SP2013 Apps but not into any SharePoint solutions or the like.


1

You can access SharePoint data using an App, you just cannot use SharePoint Server-Side Object Model code. But you could easily access and manipulate data using the SharePoint web services or client object model. If you really want to use Razor within SharePoint, it looks like all you need to do is use NuGet to add Razor to your project. You then build your ...


1

I am presuming that your app doesn't have the proper "read" permissions to see this list. Add the read permission to the AppManifest for the list service. This should then work.


1

You will need to use SharePoint web services unless a new feature is introduced in SharePoint 2013 and am not aware of it. For what you want you can use Rest API for CRUD operations on a list, Get started with the SharePoint 2013 REST service OR SharePoint 2013: Use the cross-domain library and REST for CRUD operations OR How to: Complete basic ...


1

What John said is true. You ought not directly interact with the SharePoint databases. However, when you state "Now I was asked to have all the data available in a 2007 Sharepoint Server" what it sounds like you actually need here is the Business Data Catalog service available in SharePoint 2007. It allows you to surface and interact with the data in your ...


1

SharePoint 2010 already exposes most of its content through its REST interface, implementation the ODATA protocol. Prior to develop something custom from scratch, I would seriously look into what's available, even in the free foundation edition. http://msdn.microsoft.com/en-us/library/ff521587.aspx I've built heavy client side applications nearly solely ...



Only top voted, non community-wiki answers of a minimum length are eligible