Archive | Uncategorized RSS for this section

SQL Server 2016 – JRE Update 51 or higher required

For those SharePoint folks that are installing SQL Server 2016 (CTP) and you get an error regarding the JRE, then you’re installing the Polybase Query Service.

oracle_jre

If you remove it from installed features, the error will go away.

oracle_jre_remove_polybase

 

Installing SQL 2016 CTP2.2 – Quick Tips

Don’t be worried about the ISO/DVD label being incorrect. While it shows SQL 2014, it really will be SQL 2016!

And before you do any of it, go into Server Manager, Add Features, and add .NET 3.5.  Ugh.

Mislabelled_SQL_ISO

TechEd North America Slides Download Script

So the download script only gets the videos. A quick adjustment and I was able to get the slide decks as well!!!

Here’s the code:

 

[Environment]::CurrentDirectory=(Get-Location -PSProvider FileSystem).ProviderPath
$rss = (new-object net.webclient)

$a = [xml]($rss.downloadstring(“http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/RSS/slides”))

$a.rss.channel.item | foreach{
$code = $_.comments.split(“/”) | select -last 1

$url = New-Object System.Uri($_.enclosure.url)

$file = $code + “-” + $_.creator + “-” + $_.title.Replace(“:”, “-“).Replace(“?”, “”).Replace(“/”, “-“).Replace(“<“, “”).Replace(“|”, “”).Replace(“‘”, “”).Replace(“`””, “”).Replace(“*”, “”) + “.pptx”
$file = $file.Replace(“â”, “”);
$file = $file.Replace(“¬”, “”);
$file = $file.Replace(“€”, “”);
$file = $file.Replace(“œ”, “”);
$file = $file.Replace(“‘”, “”);

if (!(test-path $file))
{
$file
$wc = (New-Object System.Net.WebClient)
$wc.DownloadFile($url, $file)
}
}

TechEd North America MP4 Download Script

Here is the download script for TechEd NA. Save it to the directory you want to download the files too. 

I copied this from the SPC14 script, but I modified the URL and the Replace code.

 

[Environment]::CurrentDirectory=(Get-Location -PSProvider FileSystem).ProviderPath
$rss = (new-object net.webclient)

$a = [xml]($rss.downloadstring(“http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/RSS/mp4high&#8221;))

$a.rss.channel.item | foreach{
$code = $_.comments.split(“/”) | select -last 1

$url = New-Object System.Uri($_.enclosure.url)

$file = $code + “-” + $_.creator + “-” + $_.title.Replace(“:”, “-“).Replace(“?”, “”).Replace(“/”, “-“).Replace(“<“, “”).Replace(“|”, “”).Replace(“‘”, “”).Replace(“`””, “”).Replace(“*”, “”) + “.mp4”
$file = $file.Replace(“â”, “”);
$file = $file.Replace(“¬”, “”);
$file = $file.Replace(“€”, “”);
$file = $file.Replace(“œ”, “”);
$file = $file.Replace(“‘”, “”);

if (!(test-path $file))
{
$file
$wc = (New-Object System.Net.WebClient)
$wc.DownloadFile($url, $file)
}
}

 

TechEd NA Sessions are on Channel 9 already

TechEd isn’t but a day old and Channel 9 already has the sessions posted!

http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014

SharePoint 2013 training for developers

SharePoint 2013 training for developers

http://msdn.microsoft.com/en-US/sharepoint/fp123633

 

Note: Thanks to Brian Bedard for sending me this link.

SharePoint Server 2013 Download

Some valuable SharePoint 2013 links

SharePoint Server 2013 Download

SharePoint 2013: presentation: IT pro training

SharePoint 2013 Software Requirements

Eric Harlan’s Installation blog post

Downloadable eBook: Deployment guide for SharePoint 2013 Preview

SharePoint 2013 training for developers

Please note: If you’re building a new VM, be sure to check out the requirements. For instance, you’ll need SQL Server 2008 R2 SP1.

And get used to building new machines for your upgrades. The only way to upgrade to SharePoint 2013 is via content database migration. In other words, you need a new 2013 farm. No more in-place upgrades (for those of you who’ve actually done one).

SharePoint 2013 Beta was just announced

If you haven’t already heard, SharePoint 2013 has been announced. If you want to play with it, log on to msdn and download the img file.

I’m looking forward to using the new application deployment model with Windows Azure.

I wonder if MS will have improved upon the Managed Metadata Service. If not, I may just take it upon myself to do so!

Deploying Custom Help with SharePoint 2010

Custom help in SharePoint 2010 is not difficult to install, once you’ve been through it. I found some helpful blogs for using the SharePoint utility HCInstall. However, I didn’t want to use a command-line utility on a FeatureActivated receiver. So I decided to dig into it and see if I couldn’t just do in code what it does. If you intend to install help thru an install script, use the utility provided by Microsoft. If you intend to install help thru features (ie, install help on demand as needed), then this post is for you.

If you haven’t used HcInstal, no worries. I’d like to walk thru what the HCInstal.exe code does. It’s not a lot, actually. You can use it as a stand-alone utility. Or, you can drop it in your project with a Reference.

By doing so, you’ll need a using declarative, namely Microsoft.SharePoint.Help.HcInstaller.

 

Hcinstall has one public class (HcInstaller_Main) and one internal (HiGovernor). Here’s an adjusted view from Reflector.

The real work is done in ParseArgs and StartIt().

* ParseArgs() does just that, parses the command line arguements, or your arguements if you’ve referenced the EXE in your project and utilized the HcInstaller_Main class’ Main() method.

* StartIt() then uses the SharePoint help object model. Did you know that it existed? In the online SharePoint 2010 SDK, found on MSDN here SharePoint help, there is little reference to it. [Notice it’s found in the Administration section. However, the namespace is not within the Administration namespace, and the dll containing the namespace is not the Admin dll, either, it’s just the Microsoft.SharePoint.dll.  Back to our work…]  So StartIt() then does the work based on the arguments. If you chose to install a help file, then it calls the Microsoft.SharePoint.Help.SPHelpMerge() method. The SDK content is here, SPHelpMerge. Notice there is no SP2010 version of this SDK helpfile, which is a bummer. But that’s okay, it appears that nothing has changed in it.

The SPHelpMerge class has 4 main methods.

  1. InstallOneHelpCollection
  2. InstallAllHelpCollections
  3. UninstallOneHelpCollection
  4. UninstallAllHelpCollections

In my current testing, I have not found UninstallOneHelpCollection to work. So, on my vm, I’m using UninstallAllHelpCollections for removing the help collections. I’ve noticed this carries thru to hcinstal.exe ( hcinstal.exe /act uninstallonehelpcollection) as well. If anyone has any info on this, I’d appreciate it.

For now, however, I’m using the SPHelpMerge.InstallOneHelpCollection() and it’s working great. If you need a sample help collection to install, you can start with this one from Code Project

Using the SPHelpMerge class, you’ll have code like this:

Using the SPHelpMerge class to install an HCCab file. Do NOT include the .HC.cab in the parameter as it is for namespace not filename.

The parameters are hardly documented. Changing most of them did not affect my install.

And there you have it. It only takes a couple of lines of code to install your help content file! Now you can include these lines into a Farm-scoped feature wrapped up in a Visual Studio SharePoint Feature project, and viola!