What is the difference between 1) an ASP.NET application exposed in SharePoint by an IFrame
and
2) a SharePoint 2013 App exposed through an app part.
Say both use CSOM and resides in intranet on a separate server (SharePoint App is provider hosted on a server in intranet ).
When you use iframe you have to face few issues:
No current SharePoint Context
No Out of the box SharePoint Security
It is harder to maintain
App approach (this approach is recommended by M$):
SharePoint Context available
SharePoint security available out of the box
App Part can be easily maintained (added, removed)
Related
I have a sharepoint 2013 site that has access web apps on the site. I would like to be able to update the access database on a mobile device. I have not found a way to make this happen. Is there a way to be able to update the access database on a mobile device?
I am using FBA authentication model into one of SP WebApplications in our SP 2013 farm to give users outside the AD, accessibility to one of SPSite so they can access the lists & Libraries and run sharepoint apps ..
for that I installed & configured the components necessary to enable & manage the FBA users easily by following the steps in the great article made by Sean Earp
Configuring SharePoint 2013 Forms-Based Authentication with SQLMemberShipProvider
Now I am able to acess my SPsite using FBA users and see the Libraries & Apps inside the SharePoint site. and when I try to access one of the provider-hosted apps, the request redirected to the remote web using the FBA account correctly, but I didn't have any access to web-app or host-app from the remote website.
Is there any restriction to access sharepoint-hosted apps using FBA authentication model in SharePoint 2013.
You need to made some entry in your remote IIS site's web.config file.
Check below link. It might be helpful for you
http://www.sharepointpals.com/post/How-to-create-a-Provider-Hosted-Application-on-Form-Based-Authentication-WebApplication-in-SharePoint-2013
I have a requirement of a custom grid in Microsoft Dynamics CRM 2013. From a SharePoint perspective, it would have been a web part. But in CRM 2013, I don't see a similar concept. I need the custom grid to be displayed in a pane for an Entity in CRM? How could that be implemented if possible? Any ideas?
Your question is to broad, but i think what you mean is how to make a custom web page in CRM.
In Dynamics CRM 2013, you cannot add a custom aspx page, as part of a CRM,
you can only put custom Silverlight and HTML/Javascript powered web pages, the latter being the preferred way, of creating these.
However if you need to create a custom web application, you can create it as a separate web application in a separate IIS website, use the CRM web services to access data, and then embed this web application in an iframe on an entity form in CRM.
In order to connect to the crm web service, from custom apps you can use early or late binding.
Early binding sample code
Late binding sample code
Personally i use late binding as connection is easier and it seems to have better performance. The simplest way to obtain a connection to the CRM service for CRUD operations is the following code:
string connString = "Url={DynamicsCRMUrl}; Username=username; Password=password; DeviceID=AnyDeviceId; DevicePassword=AnyDevicePasscode";
CrmConnection crm = CrmConnection.Parse(connString);
IOrganizationService service = (IOrganizationService)new OrganizationService(crm);
For crm online and IFD configured CRM you must add the DeviceID and DevicePassword, for on premise it is not necessary.
Make sure you have the CRM 2013 SDK for the required assemblies.
I am answering the question with a long shot, with assumptions, as i am not sure if this is what you require, but i hope it gives you guidance.
You can add an HTML WebResource in CRM that contains the grid to be displayed.
Depending on what you want to display on the grid, the data could be populated using the Dynamics CRM SDK REST API. (see SDK.REST.js).
Once you have set-up your HTML web resource, you can then include it in your entity form as an iframe component (similar to a SharePoint web part).
This approach means you don't need to host the grid in a separate website, but can include it as part of your CRM solution.
Is it possible for a SharePoint 2010 Web Part to expose a web service (WCF?)?
I want a Web Part to send emails if a certain condition is met. The web part should be hit every 15 mins via a call initiated from a custom in-house scheduler.
Cheers
A web part is just a visual component. It can expose a web service. However, custom web services can be created and deployed to SharePoint where you can access data from a site (a list maybe) and add custom logic to send the email.
Here's a good guide on how to deploy web services to SharePoint.
So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.