VS2013 Find in Files not showing any files / search results

Recently, VS2013 started omitting the file names in the search results when I did a “Find in Files”

The output was similar to:

Find all “Phone”, Subfolders, Find Results 1, Entire Solution, “*.*”
… where are my file names?? …
Matching lines: 637    Matching files: 84    Total files searched: 821

The following post fixed it:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/40c9ad4a-8cee-4f3f-b420-c7cc0463942a/visual-studio-2012-find-in-files-not-displaying-files?forum=vsx

The Default value in this registry entry was not there (it was just an empty string).

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32]
@=”C:\\Program Files (x86)\\Common Files\\microsoft shared\\MSEnv\\TextMgrP.dll
“ThreadingModel”=”Both”

 

Thanks interwebs!

Top 10 SharePoint 2013 Features Cheat Sheet

REPOST: From SharePoint Pro

http://sharepointpromag.com/sharepoint-2013/top-10-sharepoint-2013-features-cheat-sheet .

Top 10 SharePoint 2013 Features Cheat Sheet

1. Authentication

  • OAuth support. This web authorization protocol means that a user or web app can request authorization to get temporary access to specific network resources.
  • Default claims-based authentication for new web apps. A new Windows PowerShell cmdlet, Convert-SPWebApplication, helps you migrate from Windows classic-mode authentication to claims-based authentication.
  • Distributed Cache Service for login tokens. A dedicated cache helps avoid the need for additional configuration and makes for less memory utilization in the web front-ends.
  • Enhanced logging.

2. Business Connectivity Services (BCS)

  • OData support. With this web protocol, you can now connect to an external data source.
  • Event listener. This includes an event subscriber, enabling SharePoint users and custom code to receive notifications of events that occur in the external system.
  • Support for apps for SharePoint. Lets you add self-contained apps for SharePoint that don’t make any changes to the underlying code on the computer running SharePoint Server, enhancing safety and easing installation and removal.
  • External list enhancements. Users can now filter, sort, or export external lists that display content from BCS content types; performance improvements reduce the load on SharePoint farm database servers.

3. eDiscovery

  • SharePoint eDiscovery Center. Site template creates a new portal for managing holds and cases, including abilities to search, place holds, and export content.
  • Improvements to in-place holds. Includes site-level preservation, Exchange mailbox preservation, ability to set permissions for users to access original versions of preserved content.
  • eDiscovery export. Ability to export the results of an eDiscovery search for later import into a review tool.
  • Enterprise-wide eDiscovery. Ability to manage eDiscovery across multiple SharePoint farms, Exchange servers, and file shares.

4. Mobile

  • Optimized viewing across different mobile platforms.
  • One site, multiple renderings. Ability to render a single published SharePoint site in multiple designs to accommodate different devices.
  • Push notifications. Works for Windows Phones.
  • Geolocation field type. For mobile app development.
  • Ability to view business intelligence content.
  • Office Web Apps. Ability to view Word, Excel, and PowerPoint documents.

5. Records Management

 

Site-level retention policies. Ability to create and manage retention policies in SharePoint Server 2013 that apply to SharePoint sites and any associated Exchange Server 2013 team mailboxes.

6. Business Intelligence

  • In-Memory BI Engine (IMBI) or Vertipaq engine. Near instant analysis of millions of rows.
  • Power View Add-in for Excel. Visualize and interact with modeled data via visualizations, animations, and smart querying.
  • PivotChart reports. Create them without having to include a PivotTable report on the same page.
  • Ability to explore and analyze data in Excel Services reports. For reports that use SQL Server Analysis Services data or PowerPivot data models.
  • View and display items in PivotChart and PivotTable reports. Support for users in Excel Services to view and change display of items in Excel Services-published PivotChart reports and PivotTable reports.
  • Calculate measures and members. Support for Excel-created calculated measures and members in Excel Services.
  • Timeline controls. Improved Excel Services timeline controls.
  • Dashboard migration. PerformancePoint Services dashboard migration.
  • PerformancePoint Services filters. Enhanced PerformancePoint Services filter UI and filter search.
  • Cleaner BI Center.
  • Support for Analysis Services Effective User.
  • PerformancePoint support on Apple iPad.
  • Visio Services Maximum Cache Size.
  • Updated Visio Health Analyzer rules.
  • Windows PowerShell cmdlets. Updated PowerShell cmdlets for Visio.
  • Visio commenting. Ability to add comments to a Visio drawing on the web in full page rendering mode.

7. Social Computing

  • New and updated policy settings. For the User Profile service application and My Sites in Central Administration.
  • Privacy and people. New privacy settings and updated people settings.
  • Microblogging. New microblogging ability on Newsfeed page in My Site.
  • My Sites. Improved My Sites saving, synchronization, sharing, and moving of content.
  • New site templates. Community Site and Community Portal. Community Site offers a forum-like experience. Community Portal is a page that surfaces SharePoint site collections and sites.

8. Web Content Management

  • Word to HTML. Ability to copy content from Word, paste it into a Web Part, and obtain an HTML-correct display.
  • Drag and drop. Ability to drag and drop menu items directly to a page.
  • Video upload. Improved video upload process.
  • Dynamic content. Ability to insert an iframe element to embed dynamic content from other sites.
  • Support for image renditions. Allows display of different-sized versions of an image on different pages.
  • Integrated translation service.
  • Language detection. Ability to redirect visitors to a site in an appropriate language based on the language setting of their web browser.
  • Cross-site publishing. When you make changes to content, those changes are displayed on all site collections that are reusing this content.
  • Catalog. Designate any library or list as a catalog. Enables content to be reused on publishing site collections.
  • Managed navigation. Ability to define and maintain navigation on a site by using term sets, in addition to site structure-based navigation.
  • Category pages. Page layouts that are used for displaying structured content such as catalog data.
  • User-friendly URLs.
  • New Web Part. Content Search Web Part displays crawled and indexed content.
  • Refiners and faceted navigation. Enables users to refine and narrow searches while browsing different pages.
  • New analytics processing component. Ability to analyze user actions for content managers. Ability to make recommendations and offer choices to users.
  • Branding changes. SharePoint Designer or Visual Studio knowledge no longer necessary. Can design a site by using HTML, CSS, and JavaScript, in tools such as Adobe Dreamweaver, Microsoft Expression Web, or other HTML editors.
  • Device-specific publishing. Ability to create channels that allow a single publishing site to be rendered in multiple ways on multiple devices.

9. Workflow

New SharePoint Designer 2013 workflow functionality includes the following:

  • Visual workflow. Develop workflow visually using Visio 2013 add-in.
  • No-code web service calls. New action enables no-code web service calls from within a workflow.
  • Task actions. New actions for creating a task and starting a task process
  • Coordination actions. New coordination actions between workflows built on SharePoint 2010 and SharePoint 2013
  • New dictionary type.
  • Stage, Loop, and App Step workflow building blocks.
  • New enterprise features in Workflow Manager.
  • New PowerShell cmdlets.  Cmdlets that manage workflow via Workflow Manager service.

10. Search

  • Search UI improvements.
  • Search result relevancy improvements.
  • Continuous crawl.
  • Improved flexibility of search schema.
  • New search architecture.

For more information on SharePoint 2013, see Asif Rehmani’s article ” Installing SharePoint 2013.”

Boot to VHD

boot to vhd — i always forget the commands!

thanks: http://www.johnpapa.net/bootoffmetal/

Shift+F10 in windows setup…

  1. I start by creating a new VHD on the metal where the OS will be installed. It allows me to choose a fixed size or expandable virtual disk file.The advantage of using fixed is that it will always consume X amount of space and be able to boot. Expandable VHDs take up much less space when not used, but they need to have room to expand when they are booted into. I generally use expandable.
    create vdisk file=c:\win7.vhd maximum=50000 type=expandable
  2. Now I select the VHD, attach to it, create a partition on it, and format it. Then I marked it as an active system drive and assigned it a drive letter.

    select vdisk file=c:\win7.vhd
    attach vdisk
    create part primary
    format fs=ntfs label=”Win7″ quick

    active

    assign

FIX: SSMS 2012 Object Explorer hangs when expanding Databases node on a server with many DBs

GOLDEN!

REPOST FROM:

http://connect.microsoft.com/SQLServer/feedback/details/768124/ssms-2012-object-explorer-hangs-when-expanding-databases-node-on-a-server-with-many-dbs

Posted by _rod_ on 11/2/2012 at 4:09 AM

 Found this workaround here. http://stackoverflow.com/questions/10970989/sql-server-management-studio-2012-hangs
Can confirm it has fixed the problem for me.
Content as follows:
I experienced this same problem: when accessing a remote server with the Object Explorer, SSMS would hang indefinitely. The Windows System Event Log would show DCOM error 10009 (“DCOM was unable to communicate with the computer MACHINE_NAME using any of the configured protocols.”).
The solution was to clear the MRU history and other settings from my profile. To do that:
Close any open instances of SSMS 2012     In Explorer, open “%AppData%\Microsoft\SQL Server Management Studio”     Rename the “11.0” folder to something else, like “11.0.old”     Open SSMS 2012
You’ll see that your MRU list has been cleared. You should then be able to re-enter your credentials and use SSMS as normal.
If everything works, you can delete the renamed folder. Otherwise, delete the new “11.0” folder that was created and rename the original one back to “11.0”.
I have no idea whether it’s actually the MRU list that’s causing this problem or if it’s some other profile data.
We were able to discover that SSMS is trying to make a DCOM connection over port 135 to the SQL Server (perhaps for SSIS, T-SQL Debugging, or something else). Our firewall was configured to block port 135. By opening the port in the firewall we were able to use SSMS (hence the reason it worked against local databases but not remote ones). Unfortunately, an open port 135 is an invitation for a lot of attacks, so that wasn’t a practical solution for us.

“Sideloading of apps is not enabled on this site” Publishing SharePoint App directly from VS2013

I was playing with VS2013, my SharePoint online site, and uploading an app w/o any intervention on the browser (and without SharePoint installed locally).  My first attempt yielded this error:

“Sideloading of apps is not enabled on this site” – SharePoint Online Development.

Through various searches found these steps (thanks http://blogs.msdn.com/b/kaevans/archive/2013/10/05/enabling-the-developer-site-collection-feature-in-sharepoint-online.aspx)
1) Install SharePoint Client Browser (http://spcb.codeplex.com/releases/view/114743)
2) Open SharePoint PowerShell from SP Client Browser
3) Run this script (activates the hidden Developer feature):

$ctx.Load($ctx.Site);
$ctx.ExecuteQuery();
$guid = [System.Guid]”e374875e-06b6-11e0-b0fa-57f5dfd72085″
$ctx.Site.Features.Add($guid,$true, Microsoft.SharePoint.Client.FeatureDefinitionScope]::None)
$ctx.ExecuteQuery();

4) Publish right from VS

Error using “Open in Explorer” for SharePoint Sites

After some frustration with Office 365 “Open in Explorer” giving these unhelpful errors:

Your client does not support opening this list with Windows Explorer
We’re having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.
We’re having a problem opening this location in File Explorer. To open with File Explorer, you’ll need to add this site to your Trusted Sites list and select the “Keep me signed in” check box when you sign in to the SharePoint Online site. For more information, see http://support.microsoft.com/kb/2629108.
I found a KB Article that has a hotfix to fix this issue:
Woo!

SQL Tables by Size

Get SQL Tables by Size

SELECT
t.NAME AS TableName,
s.Name AS SchemaName,
p.rows AS RowCounts,
SUM(a.total_pages) * 8 AS TotalSpaceKB,
SUM(a.used_pages) * 8 AS UsedSpaceKB,
(SUM(a.total_pages) – SUM(a.used_pages)) * 8 AS UnusedSpaceKB
FROM
sys.tables t
INNER JOIN
sys.indexes i ON t.OBJECT_ID = i.object_id
INNER JOIN
sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id
INNER JOIN
sys.allocation_units a ON p.partition_id = a.container_id
LEFT OUTER JOIN
sys.schemas s ON t.schema_id = s.schema_id
WHERE
t.NAME NOT LIKE ‘dt%’
AND t.is_ms_shipped = 0
AND i.OBJECT_ID > 255
GROUP BY
t.Name, s.Name, p.Rows
ORDER BY
t.Name

Reference: http://stackoverflow.com/questions/7892334/get-size-of-all-tables-in-database

Sweet.

Quick & Dirty — setting up SQL Server Mirroring

on Primary and Failover servers:
create endpoint endpoint_mirroring
state=started
as tcp (listener_port = 7022)
for database_mirroring (role=partner);
go

on witness server:
create endpoint endpoint_mirroring
state=started
as tcp (listener_port = 7022)
for database_mirroring (role=witness);
go
make sure the SQL service account that is running has CONNECT permissions
make sure the ports are open (no firewall, etc…)

create backup of the main DB to be mirrored
restore it as WITH NORECOVERY on the mirror
on the primary, go to Tasks -> Mirror -> and configure the mirroring

If a certificate is wrong, or the service account does not have permissions it will
give a misleading network error saying it cant reach the host (“The server network address TCP://developer02.dev.com:7022 cannot be reached or does not exist”, Alter <dbname> failed). Check the event log for what the real error is.

The connection string for mirrors is:
SERVER=DEVELOPER;FAILOVERPARTNER=DEVELOPER02;network=dbmssocn

Apparently the dbmssocn makes it so that it automagically switches to the failover – I dunno.

If necessary, you can create a linked server that behaves normally even when failed-over.  I tried with a default SQL Native Client but it didn’t work. SQL OLEDB seemed to work.

Querying it from a linked server uses the following syntax:
select * from developer.sandbox.dbo.person

Bing bang boom.