Tag Info

New answers tagged

1

Your scenario describes a Provider Hosted App. You can use the same application you already have, integrated with O365 through an App. The main enhancement you'll have to think about in this approach has to do with authentication and incorporating the different set of tokens and contexts coming from O365. The following article describes the App options: ...


1

You need to have the dll deployed to: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN if you want the timerjob to be able to use it.


0

Today i also faced the similar issue when i tried to import the webpart from Dev site and export to QA site. when i try to add this webpart to the page , it was giving the error."$Resources:core,ImportErrorMessage" . I could not figure out the solution for hours. I came to this stack Exchange Questions and did almost everything which has said here in other ...


2

Here are couple of points which can help you Find all custom Solutions - For this you can open Central Administration -> System Settings -> Solutions Now using PowerShell you can download those solutions from the Development Server $farm = Get-SPFarm $file = $farm.Solutions.Item("solutionname.wsp").SolutionFile ...


0

This error is due to limitation in number of variables per scope. The limit is 50. I fixed it by following this link: Detailed explanation here. Found the answer through this question


1

Backup-SPSite is full fidelity, that means all associations and id are kept the same.. its a mirror copy. Import and export are not full fidelity meaning that associations are lost and no id's are kept (new guids created). Backup/restore-SPSite is for site collection level. import/export is for site level and not full fidelity. full fidelity means you keep ...


0

I had the same error, and I just closed and reopened my PowerShell window to make it work. Hope this can help in some cases.


0

It is not a good idea to change the names of already deployed content types or fields (internal names)...Always change the GUID otherwise you can get in this trouble... Rename the CT back, redeploy, retract (and be sure the CT is removed). Then rename the CT, change the GUID! and deploy again.


1

I don't find any official documentation on that just now, but as far as I know it refers to the location within the SharePoint deployment package, that means within the .wsp file. If you open that file (for example, after changing the file extension to .cab), you can see its internal folder structure. This structure often (as long as the Type attribute of ...


0

I am not exactly sure what was wrong, but I tried again after completely deleting the app and deployed again, and it worked.



Top 50 recent answers are included