Get InfoPath to display lookup column value, not ID

If you have ever used a SharePoint list containing lookup columns as a data source in your InfoPath forms, you may have been disappointed to see the value of the lookup is not displayed. Instead of the value, the list ID of the item containing the value is displayed.

Below link has the detailed post.

http://sharepointsolutions.com/sharepoint-help/blog/2011/11/get-infopath-to-display-lookup-column-value-not-id/

 

What is Solution, Sandbox?

Solution:

  • solution is a deployable, reusable package that can contain features, site definitions, and other functionality.
  • Solutions can be enabled or disabled individually.
  • You can deploy a solution directly onto your SharePoint Server farm, or you can deploy the solution into a sandbox.

Sandbox:

A sandbox is a restricted execution environment that enables programs to access only certain resources, and that keeps problems that occur in the sandbox from affecting the rest of the server environment.

Sandboxed Solution:

Solutions that you deploy into a sandbox, which are known as sandboxed solutions, cannot use certain computer and network resources, and cannot access content outside the site collection they are deployed in.

Farm based Solution Sandboxed Solution
A solution package is deployed to the farm’s solution store, it is called a ‘farm solution’. A solution package is deployed to the solution store of a site collection, it is called a ‘sandboxed solution’.
The components in a farm solution generally run with full trust, although it is possible to deploy an assembly in a farm solution with a custom CAS policy that gives it less than full trust. The components of a sandboxed solution run under several significant code execution and resource access restrictions.
Only a farm administrator can install a farm solution. A site collection administrator can deploy a sandboxed solution.
Less resource restriction. Each sandboxed solution must conform to certain hard limits on the system resources that it can use.

Autonumber repeating table rows in InfoPath 2010

Thanks to S.Y.M. Wong-A-Ton (www.bizsupportonline.net)

You can in InfoPath autonumber repeating table rows as follows:

  1. In InfoPath Designer 2010, create a new Blank Form template.
  2. On the Home tab under the Controls  group, click Repeating Table and add a repeating table with 3 columns to the form template.
  3. Right-click the first field (field1) in the repeating table and choose Change Control and then Calculated Value from the context menu that appears.
  4. With the first field (field1) still selected, click the Properties tab or double-click field1 to bring forward the Properties tab.
  5. On the Properties tab under the Properties group, click Default Value.
  6. On the Field or Group Properties dialog box on the Data tab under the Default Value section, click the formula button behind the Value text box.
  7. On the Insert Formula dialog box, select the Edit XPath (advanced) check box.
  8. On the Insert Formula dialog box, type the follow formula into the Formula text box:count(../preceding-sibling::*) + 1
  9. On the Insert Formula dialog box, click Verify Formula to ensure that the formula does not contain any errors. Click OK to close the message box that says whether the formula contains or does not contain errors. Correct any errors if necessary.
  10. On the Insert Formula dialog box, click OK.
  11. On the Field or Group Properties dialog box, ensure that the Refresh value when formula is recalculated check box is selected, and then click OK.
  12. Save the InfoPath form template and publish it for example to a SharePoint form library.

Sorry, apps are turned off. If you know who runs the server, tell them to enable apps.

Enabling SharePoint 2013 ‘Apps’

After installing and configuring SharePoint 2013, if you try to visit the SharePoint App Store you will notice a warning message ‘Sorry, apps are turned off. If you know who runs the server, tell them to enable apps.”. Well lucky for us, we run this server so it’s time to configure it to run Apps.

Basically SharePoint apps can be deployed in three ways –

– Provider-hosted (Developer or IT department provides the hosting infrastructure) – Autohosted (Uses Windows Azure or SQL Azure for hosting) – SharePoint-hosted (Hosted inside existing SharePoint infrastructure)

In order to install an App from the App Store you must setup an isolated App Domain, this is because Apps from the store deploy to their own app domain and run under a separate process from your SharePoint sites. If your SharePoint site uses the DNS alias http://sharepoint.contoso.com you could have *.apps.contoso.com as your app domain. I’m going to walkthrough the process required to set-up your environment for Apps but at a high level, if you need more details for each step then head on over to the MSDN documentation.

Pls visit below url to configure further info

http://www.sharepointalex.co.uk/index.php/2012/11/enabling-sharepoint-2013-apps/

AppFabric Caching and SharePoint: Concepts and Examples

SharePoint 2013 utilizes Windows Server AppFabric to maintain an in-memory cache of frequently-used data. While this in-memory cache achieves its goals and does improve scalability, it also adds another service to maintain to SharePoint’s long list of supporting elements.

Josh Gavant [MSFT] provided a well explained article about in the below link.

http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-1.aspx

Design Patterns: Basics of Dependency Injection

What is Dependency Injection?

It is very common that you will instantiate an objects properties or internal members to some value other than null within the objects constructor; thus setting up the object for use when it is created. These values are considered “dependencies” since the object depends on them in order to function. The pattern at its most basic is just passing in these dependencies to the objects constructor instead of instantiating them directly within the objects constructor. By doing this you can change the objects dependencies without needing to modify, refactor or inherit the class. Also, dependency injection doesn’t rely on IoC and can be used without it.

Thanks to Chris Pietschmann(http://pietschsoft.com). Pls visit the below url more details.

http://pietschsoft.com/post/2012/04/13/Design-Patterns-Basics-of-Dependency-Injection.aspx