Merge pull request #2349 from iRaindrop/vbruham_sharepoint_s

Visual Studio SharePoint QA - Missing Fixes: I-V

Author: ktoliver

docs/sharepoint/importing-items-from-an-existing-sharepoint-site.md

@@ -28,7 +28,7 @@ ms.workload:
   The Import SharePoint Solution Package project template lets you reuse elements such as content types and fields from existing SharePoint sites in a new [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint solution. Although you can run most imported solutions without modification, there are certain restrictions and issues to consider, especially if you modify any items after importing them.  
 
 > [!NOTE]  
->  To import reusable workflows, use the Import Reusable Workflow project template. [!INCLUDE[crdefault](../sharepoint/includes/crdefault-md.md)] [Guidelines for Importing Reusable Workflows](../sharepoint/guidelines-for-importing-reusable-workflows.md).  
+>  To import reusable workflows, use the Import Reusable Workflow project template. [!INCLUDE[crdefault](../sharepoint/includes/crdefault-md.md)] [Guidelines for importing reusable workflows](../sharepoint/guidelines-for-importing-reusable-workflows.md).  
   
 ## Supported SharePoint solutions
  [!INCLUDE[vs_dev11_long](../sharepoint/includes/vs-dev11-long-md.md)] fully supports the importing of solutions created in [!INCLUDE[wss_14_short](../sharepoint/includes/wss-14-short-md.md)] and [!INCLUDE[moss_14_short](../sharepoint/includes/moss-14-short-md.md)].  
@@ -83,14 +83,14 @@ ms.workload:
 
  Features are containers for SharePoint items. Each feature keeps a reference to each item, such as content types and list definitions, that it contains. When you import your solution, [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] sets up features for all of the imported elements and attempts to maintain the feature-to-element relationships for the files. Any files whose references could not be resolved are put in the **Other Imported Files** folder.  
 
- For more information about features, see [Developing SharePoint Solutions](../sharepoint/developing-sharepoint-solutions.md) and [Working with Features](http://go.microsoft.com/fwlink/?LinkID=147704).  
+ For more information about features, see [Develop SharePoint solutions](../sharepoint/developing-sharepoint-solutions.md) and [Working with Features](http://go.microsoft.com/fwlink/?LinkID=147704).  
 
 ### Handle special cases
  In some cases, Visual Studio cannot reconcile an item with its dependent files. Any files that [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] could not resolve appear under the folder **Other Imported Files**. In addition, their **DeploymentType** properties are set to **NoDeployment** so that they are not deployed with the solution.  
 
  For example, if you import the list definition ExpenseForms, a list definition with that name appears under the **List definitions** folder in **Solution Explorer** along with its *Elements.xml* and *Schema.xml* files. However, its associated ASPX and HTML forms may be placed in a folder called **ExpenseForms** under the **Other Imported Files** folder. To complete the import, move these files under the ExpenseForms list definition in **Solution Explorer** and change the **DeploymentType** property for each file from **NoDeployment** to **ElementFile**.  
 
- When importing event receivers, the *Elements.xml* file is copied to the correct location, but you must manually include the assembly in the solution package so that it deploys with the solution. [!INCLUDE[crabout](../sharepoint/includes/crabout-md.md)] how to do this, see [How to: Add and Remove Additional Assemblies](../sharepoint/how-to-add-and-remove-additional-assemblies.md).  
+ When importing event receivers, the *Elements.xml* file is copied to the correct location, but you must manually include the assembly in the solution package so that it deploys with the solution. [!INCLUDE[crabout](../sharepoint/includes/crabout-md.md)] how to do this, see [How to: Add and remove additional assemblies](../sharepoint/how-to-add-and-remove-additional-assemblies.md).  
 
  When importing workflows, InfoPath forms are copied to the **Other Imported Files** folder. If the *.wsp* file contains a Web template, it is set as the startup page in **Solution Explorer**.  
 
@@ -103,10 +103,10 @@ ms.workload:
  Most items in SharePoint solutions have one or more dependent items. For example, list instances depend on content types and content types depend on fields. After you import a SharePoint solution, [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] does not notify you of any reference problems if you delete an item in the solution, but not its dependent items, until you attempt to deploy the solution. For example, if an imported solution has a list instance that depends on a content type and you delete that content type, an error might occur on deployment. The error occurs if the dependent item is not present on the SharePoint server. Similarly, if a deleted item also has a related property bag, then delete those property bag entries from the **PropertyBags** *Elements.xml* file. Therefore, if you delete any items from an imported solution and you get deployment errors, check to see if any dependent items need to also be deleted.  
 
 ## Restore missing feature attributes
- When importing solutions, some optional feature attributes are omitted from the imported feature manifest. If you want to restore these attributes in the new feature file, identify the missing attributes by comparing the original feature file to the new feature manifest and follow the instructions in the topic [How to: Customize a SharePoint Feature](../sharepoint/how-to-customize-a-sharepoint-feature.md).  
+ When importing solutions, some optional feature attributes are omitted from the imported feature manifest. If you want to restore these attributes in the new feature file, identify the missing attributes by comparing the original feature file to the new feature manifest and follow the instructions in the topic [How to: Customize a SharePoint feature](../sharepoint/how-to-customize-a-sharepoint-feature.md).  
 
 ## Deployment conflict detection is not performed on built-in list instances
- [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] does not perform deployment conflict detection on built-in list instances (that is, default list instances that come with SharePoint). Not performing conflict detection is done to avoid overwriting the built-in list instances on SharePoint. The built-in list instances are still deployed or updated, but are never deleted or overwritten. [!INCLUDE[crdefault](../sharepoint/includes/crdefault-md.md)] [Troubleshooting SharePoint Packaging and Deployment](../sharepoint/troubleshooting-sharepoint-packaging-and-deployment.md).  
+ [!include[vsprvs](../sharepoint/includes/vsprvs-md.md)] does not perform deployment conflict detection on built-in list instances (that is, default list instances that come with SharePoint). Not performing conflict detection is done to avoid overwriting the built-in list instances on SharePoint. The built-in list instances are still deployed or updated, but are never deleted or overwritten. [!INCLUDE[crdefault](../sharepoint/includes/crdefault-md.md)] [Troubleshoot SharePoint packaging and deployment](../sharepoint/troubleshooting-sharepoint-packaging-and-deployment.md).  
 
 ## Import SharePoint Server 2010 workflows
  If you import a workflow created in [!INCLUDE[moss_14_short](../sharepoint/includes/moss-14-short-md.md)], it will not run correctly after you deploy it. The workflow does not run correctly because certain assemblies are missing and  [!INCLUDE[moss_14_short](../sharepoint/includes/moss-14-short-md.md)] workflows contain InfoPath forms which are not currently supported in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] workflow solutions. However, imported [!INCLUDE[moss_14_short](../sharepoint/includes/moss-14-short-md.md)] workflows can be made to work correctly after fixing some items, such as adding references to the [!INCLUDE[moss_14_short](../sharepoint/includes/moss-14-short-md.md)] assemblies and reconnecting the InfoPath forms. [!INCLUDE[crdefault](../sharepoint/includes/crdefault-md.md)] [Importing SharePoint Server 2010 Workflows](http://go.microsoft.com/fwlink/?LinkId=182226).  
@@ -133,7 +133,7 @@ ms.workload:
  The absence of a script manager control can be a problem when you import a [!INCLUDE[winshare3](../sharepoint/includes/winshare3-md.md)] or [!INCLUDE[offshare7](../sharepoint/includes/offshare7-md.md)] project into [!INCLUDE[vs_dev10_long](../sharepoint/includes/vs-dev10-long-md.md)], because the SharePointProductVersion attribute of all new projects is set to 14.0. If you deploy an upgraded project that has a Web form without a script manager, the form will not display in SharePoint.  
 
 ## See also
- [Walkthrough: Import Items from an Existing SharePoint Site](../sharepoint/walkthrough-import-items-from-an-existing-sharepoint-site.md)   
- [Guidelines for Importing Reusable Workflows](../sharepoint/guidelines-for-importing-reusable-workflows.md)   
- [Walkthrough: Import a SharePoint Designer Reusable Workflow into Visual Studio](../sharepoint/walkthrough-import-a-sharepoint-designer-reusable-workflow-into-visual-studio.md)   
- [How to: Add an Existing BDC Model File to a SharePoint Project](../sharepoint/how-to-add-an-existing-bdc-model-file-to-a-sharepoint-project.md)  
+ [Walkthrough: Import items from an existing SharePoint site](../sharepoint/walkthrough-import-items-from-an-existing-sharepoint-site.md)   
+ [Guidelines for importing reusable workflows](../sharepoint/guidelines-for-importing-reusable-workflows.md)   
+ [Walkthrough: Import a SharePoint Designer reusable workflow into Visual Studio](../sharepoint/walkthrough-import-a-sharepoint-designer-reusable-workflow-into-visual-studio.md)   
+ [How to: Add an existing BDC model file to a SharePoint project](../sharepoint/how-to-add-an-existing-bdc-model-file-to-a-sharepoint-project.md)  

docs/sharepoint/integrating-business-data-into-sharepoint.md

@@ -33,10 +33,10 @@ ms.workload:
 ## Models in Visual Studio  
  Models in Visual Studio enable you to write custom code to retrieve and update data from back-end data sources. You can also aggregate data from multiple data sources. For example, you can display a list of customers that contains data from a [!INCLUDE[ssNoVersion](../sharepoint/includes/ssnoversion-md.md)] database and a Web service.  
 
- You can also import models that are already deployed to SharePoint. After you import a model, you can add custom code or just use Visual Studio to package and deploy the model to multiple SharePoint server farms. For more information, see [Creating a Business Data Connectivity Model](../sharepoint/creating-a-business-data-connectivity-model.md).  
+ You can also import models that are already deployed to SharePoint. After you import a model, you can add custom code or just use Visual Studio to package and deploy the model to multiple SharePoint server farms. For more information, see [Create a business data connectivity model](../sharepoint/creating-a-business-data-connectivity-model.md).  
 
 ## Design a model in Visual Studio
- You can design a model by using a designer and several tool windows. As you design the model, Visual Studio generates the model XML. For more information, see [BDC Model Design Tools Overview](../sharepoint/bdc-model-design-tools-overview.md).  
+ You can design a model by using a designer and several tool windows. As you design the model, Visual Studio generates the model XML. For more information, see [BDC model design tools overview](../sharepoint/bdc-model-design-tools-overview.md).  
 
  A model contains entities and methods.  
 
@@ -46,13 +46,13 @@ ms.workload:
 ### Methods  
  A method enables the consumers of an external content type to perform an action on the fields of an entity. For example, an Updater method might enable users to change the address, and birth date of a customer where `Address` and `BirthDate` are fields of the `Customer` entity.  
 
- Visual Studio generates a service code file for each entity in your model. When you add a method to your model, Visual Studio generates a corresponding method in the service code file. Add code to each method to perform the appropriate task. For example, if you add a Creator method to the model, Visual Studio generates a Creator method in your service code file. This method is called by the BDC service when a user clicks the **New Item** button in a list that is based on the model. Therefore, add code to the Creator method that adds new data to a data source. For more information, see [Designing a Business Data Connectivity Model](../sharepoint/designing-a-business-data-connectivity-model.md).  
+ Visual Studio generates a service code file for each entity in your model. When you add a method to your model, Visual Studio generates a corresponding method in the service code file. Add code to each method to perform the appropriate task. For example, if you add a Creator method to the model, Visual Studio generates a Creator method in your service code file. This method is called by the BDC service when a user clicks the **New Item** button in a list that is based on the model. Therefore, add code to the Creator method that adds new data to a data source. For more information, see [Design a business data connectivity model](../sharepoint/designing-a-business-data-connectivity-model.md).  
 
 ## Related topics
 
 |Title|Description|  
 |-----------|-----------------|  
-|[Creating a Business Data Connectivity Model](../sharepoint/creating-a-business-data-connectivity-model.md)|Shows you how create a new model or import a model that you export from SharePoint.|  
-|[Designing a Business Data Connectivity Model](../sharepoint/designing-a-business-data-connectivity-model.md)|Explains how to design the elements of a model by using Visual Studio design tools.|  
+|[Create a business data connectivity model](../sharepoint/creating-a-business-data-connectivity-model.md)|Shows you how create a new model or import a model that you export from SharePoint.|  
+|[Design a business data connectivity model](../sharepoint/designing-a-business-data-connectivity-model.md)|Explains how to design the elements of a model by using Visual Studio design tools.|  
 |[When to Use SharePoint Designer vs. Visual Studio When Building Solutions Using BCS](http://go.microsoft.com/fwlink/?LinkID=183448)|Helps you decide whether to use Visual Studio or use SharePoint Designer to create a model for the BDC.|  
-  
+  

docs/sharepoint/localizing-sharepoint-solutions.md

@@ -53,7 +53,7 @@ ms.workload:
  There are three areas you typically localize in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] SharePoint applications: features, ASPX page markup, and code. For purposes of illustration, the following sections assume you have a SharePoint solution that you want to localize into German and Japanese. The default language is English.  
 
 ### Localize features
- To localize a feature, you have to replace the hard-coded title and description of the feature with an expression that references the translated title and string in the localized resources file. You make this change in the **Feature Designer** in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)]. For more information, see [How to: Localize a Feature](../sharepoint/how-to-localize-a-feature.md).  
+ To localize a feature, you have to replace the hard-coded title and description of the feature with an expression that references the translated title and string in the localized resources file. You make this change in the **Feature Designer** in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)]. For more information, see [How to: Localize a feature](../sharepoint/how-to-localize-a-feature.md).  
 
  To localize your English feature into German and Japanese, you add three Resource File project items to your project: one for English, one for German, and one for Japanese. Feature resource files cannot be used to localize ASPX markup or code; separate resource files are required for them.  
 
@@ -103,7 +103,7 @@ $Resources:String ID
 <asp:literal ID="Literal1" runat="server" Text="<%$Resources:Resource1, String9%>" />  
 ```  
 
- For more information, see [How to: Localize ASPX Markup](../sharepoint/how-to-localize-aspx-markup.md).  
+ For more information, see [How to: Localize ASPX markup](../sharepoint/how-to-localize-aspx-markup.md).  
 
 ### Localize code
  In addition to localizing Feature strings and [!INCLUDE[vstecasp](../sharepoint/includes/vstecasp-md.md)] markup, you also have to localize the message strings and error strings that appear in your solution code. Localized informational and error messages are contained in satellite assemblies. Satellite assemblies contain strings that are visible to users, such as [!INCLUDE[TLA2#tla_ui](../sharepoint/includes/tla2sharptla-ui-md.md)] text and output messages like exceptions.  
@@ -120,17 +120,17 @@ $Resources:String ID
 HttpContext.GetGlobalResourceObject("<Resource File Name>", "<String ID>")  
 ```  
 
- For more information, see [How to: Localize Code](../sharepoint/how-to-localize-code.md).  
+ For more information, see [How to: Localize code](../sharepoint/how-to-localize-code.md).  
 
 #### Web part code localization
  Web parts include a custom property editor feature that includes code attributes that use hard-coded strings, such as WebDisplayName, Category, and WebDescription. To replace the string values for these attributes, create a separate class that derives from the attribute's class. In those classes, set the attribute's property. The attribute property depends on the base class. For example, the WebDisplayName attribute property is DisplayNameValue and the WebDescription attribute property is DescriptionValue.  
 
  In the derived class, reference the string ID from the resource file and the ResourceManager object to get the localized value for the string ID. Return this value to the property editor attribute.  
 
 ## See also
- [How to: Localize a Feature](../sharepoint/how-to-localize-a-feature.md)   
- [How to: Localize ASPX Markup](../sharepoint/how-to-localize-aspx-markup.md)   
- [How to: Localize Code](../sharepoint/how-to-localize-code.md)   
- [How to: Add a Resource File](../sharepoint/how-to-add-a-resource-file.md)   
- [How to: Use a Resource File to Specify Localized Names, Properties, and Permissions](../sharepoint/how-to-use-a-resource-file-to-specify-localized-names-properties-and-permissions.md)  
-  
+ [How to: Localize a feature](../sharepoint/how-to-localize-a-feature.md)   
+ [How to: Localize ASPX markup](../sharepoint/how-to-localize-aspx-markup.md)   
+ [How to: Localize code](../sharepoint/how-to-localize-code.md)   
+ [How to: Add a resource file](../sharepoint/how-to-add-a-resource-file.md)   
+ [How to: Use a resource file to specify localized names, properties, and permissions](../sharepoint/how-to-use-a-resource-file-to-specify-localized-names-properties-and-permissions.md)  
+