I'm using an on premises version of CRM 2011, which I'm about to begin developing against.
We're using Octopus Deploy with some other sites.
It would be great if there was a way to import CRM Solutions using a powershell script or wcf service, rather then someone manually navigating to the site and go through the motions.(we have dev,test and prod environments)
I can't seem to find a non UI method of doing this online. Can anyone suggest a better solution then using the UI?
You can import solution programmatically using ImportSolutionRequest class. Check this link
Related
I'm administering a Sharepoint Online site right now. Is there a way to run Sharepoint powershell cmdlets externally from SPFX/ NodeJS. I'm trying to create a UI for disabling versioning for a document library. Seems that disabling versioning could only be achieved through powershell right now.
(Or is there an sharepoint api endpoint for actually doing it, not sure)
You cannot run powershell cmdlets from SPFx. SPFx is a framework to build applications that run in a browser.
But you can use REST API (the easiest way to use it is probably pnpjs to wrap it). You could try something like this (just update the library property):
await sp.web.lists.getByTitle("Documents").update({ EnableVersioning: false });
I have been working with SharePoint online for sometime.I have been given the task to build an app to create subsites in SharePoint 2013 online website. I prefer working with C# code. I am looking into SCOM to built the App.I want to know if this can be done or does online version only supports JavaScript COM development.
I have gone through multiple materials from Microsoft but no were its clear about autohosted app running on SharPoint online.
I have created a SharePoint App project and set it to autohost. But it throws token not found error while trying to run it against sharepoint online. Looking for advice.
Edit - I need to know if SCOM can be used to develop apps for SharePoint online site
Thanks.
Sounds like you're just starting off with SharePoint apps. SP apps use CSOM (client side object model). I personally prefer JavaScript (JSOM) MSDN JSOM Basic Tasks
If you want to develop against an online environment, then select SharePoint hosted not autohosted. If you are using the app internally then continue, if you are hoping to publish it to the app store then you can report back that this requires full control permission which you are not allowed to request in an app published to the SharePoint store.
When I first started developing SharePoint 2013 online applications I found this article on codeproject a great help.
It might be usefull for you as well: http://www.codeproject.com/Articles/690015/SharePoint-2013-Online-App-Development-Part-1.
Alternatively you could give the official Microsoft Office 365 training kit a look. It's basically the same as SharePoint 2013 online.
http://www.microsoft.com/en-us/download/details.aspx?id=14889
Are there any differences between the OnPremise and Hosted versions of MS CRM 2011 besides price/licensing? Can I deploy solutions or any other custom features to the Hosted version or is that strictly reserved for the default functionality?
We are also considering trying to mold Sharepoint into being our CRM because we are already licensed for it but I'm going to try to reject that.
You can deploy plugins that run in the Sandbox environment in the CRM Online/Hosted environments. You can also deploy custom FetchXML-based reports to Hosted. The main things you can't do in a Hosted environment:
"Normal" plugins
SQL-based Reports
Direct database access (Filtered Views)
Custom .NET Workflow activities
And yes, SharePoint shouldn't be your CRM - CRM should be your CRM! :)
With rollup 12 it is now possible to use custom workflow activities in CRM online
http://mubashersharif.blogspot.be/2013/01/custom-workflowactivity-understanding-development.html
Following the release of SharePoint 2010, there has been renewed interest in using PowerShell to manage SharePoint solutions. I'm interested in finding out how my peers are currently using PowerShell with SharePoint, either 2007 or 2010.
For example, I use a PowerShell script to determine the number of sites, sub-sites and pages that have been created in specific web applications. Can you provide details of how you make use of PowerShell?
We're developing some custom SP2010 software. We're using Powershell cmdlets to install and upgrade builds on our test machines, as well as do some initial configuration tasks such as deploying features to certain webs, and creating service apps & service app proxies.
Unfortunately the cmdlets don't seem to play well with PSRemoting, which makes automated build & deploy trickier.
I use PowerShell for installation and debugging purposes. I'm surprised that you haven't used Powershell with SharePoint 2010.
I write quite a few scripts for deploying and managing many solutions. For Example, Every time we deploy our PerformancePoint dashboards, it removes the top the global navigation. I use a Powershell script to re-insert the global navigation based on a XML File that I have created.
How can I deploy a custom authentication provider in MOSS 2007?
Is there any provided functionality to do this (like a Sharepoint feature)?
Or do I have to install it in the GAC on each box in the farm manually?
The usual approach for installing extensions like this is to use a feature, yes. However, you won't be using any specialized XML as this kind of extension is not catered for explicitly. So how can you do it? By using an essentially empty feature project that contains an Event Receiver assembly. The event receiver assembly is called automatically by sharepoint for 4 different events: install, uninstall, activate and deactivate. I suggest you hook the install and uninstall events to deploy your provider.
http://msdn.microsoft.com/en-us/library/bb862634.aspx
Make sense?
-Oisin
You can deploy a custom membership provider under minimal trust in SharePoint 2007 using Code Access Security (CAS).
Altough the author seems to not recommend using the GAC since some Sharepoint installations are on a hosted environment and you can play with GAC.
It is often easier to install the
membership provider DLL in the Global
Assembly Cache to achieve full trust,
but in cases where you're working with
a hosted SharePoint site and cannot
deploy to the GAC these instructions
should steer you right.
The detailed article is here. I hope it helps.
The Windows Live Authentication feature of the Community Kit for Sharepoint provides a nice example (with source code) of creating a solution package with a custom authentication provider. A solution package can be deployed to all servers in the farm without manually touching them