Apr 22 2014

Managing Education’s Growing Tech Needs On A Limited Budget

Tag: PodcastPaul Hillman @ 9:28 am

This episode of KT 2.o looks at how Henry Ford Community College manages the growing tech needs of its student population with limited budgets and unlimited creativity.

Community colleges hold a unique position in our education infrastructure. Entrusted with a unique educational mission and facing complex financial challenges, community colleges meet the needs of a highly diverse student population.

Podcast: Managing Education’s Growing Tech Needs On A Limited Budget


Apr 10 2014

Project Server 2013 and SharePoint 2013: SP1 download deactivated

Tag: Collaboration,Project ManagementDoug MacNEIL @ 10:46 am

As a precaution, due to a recently discovered issue, both the SharePoint 2013 and Project Server 2013 Service Pack 1 (SP1) downloads have been made  temporarily unavailable. 

The Knowledge Base articles for Project Server 2013 http://support.microsoft.com/kb/2817434 and SharePoint 2013 – http://support.microsoft.com/kb/2817429 have been updated with:

“Microsoft has recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates”. As a precautionary measure, they have deactivated the download page until a new package is published.

The April Cumulative Update is due out next week.


Apr 03 2014

Windows XP: Why Upgrading Is So Important

Tag: InfrastructureC/D/H Consultant @ 10:50 am

Support for Windows XP is ending.  While some have stated this is not really a big deal, I would beg to differ. Will your PC suddenly quit working on April 8th? No. However, security for that system will flag due to the lack of continued support. Any company running Windows XP will find its valuable data at increasing risk for each day that system remains on XP.

Here is why:

The Windows XP operating systems is only a few months shy of its 13 birthday.  Awkward teenage years aside, the one thing you of can be sure is that every single vulnerability has been discovered and exploited by those with malicious intent. Further, those exploits are readily available in pre-packaged form just ready to be deployed against vulnerable operating systems.

On a supported operating system, teams of engineers and security experts are constantly working to patch existing flaws and discover new ones ahead of hackers. These teams spend their days issuing patches and bug fixes pretty much constantly.  Once an operating system becomes “end of life” (EOL), that cycle of patching and fixing ends.

Unfortunately, the ongoing work of hacking the operating system continues. The difference is that there is no longer any counter-measure to that deterrent.  Any system running XP is in effect hanging a big “welcome criminals” sign on their front door.

With the recent high-profile security breaches at organizations like Sony, Target, NASDAQ and others, why would you take that chance? Why would you place sensitive assets like money and information on the systems of companies who have decided to take that chance?

Be smart!

Upgrade your systems and consider dealing with banks, hospitals, insurance companies, etc. who are upgrading as well.


Mar 31 2014

Azure OS Updates

Tag: InfrastructureMark Sassin @ 7:59 am

Is the application of updates to guest OS virtual machines ,which have “Automatic” updates enabled, a bit of a mystery? Let me point out a couple helpful sites:

The Windows Azure Guest OS Release and SDK Compatibility Matrix

This provides a wealth of useful background information for administrators and developers about OS releases and SDK compatibility in leveraging Azure. I have made it a habit to consult this site when updating an Azure deployment to a new version of the SDK or a new OS family.

The Official Windows Azure OS Updates RSS Feed

This announces when an update is nearing its release time. Due to a number of factors, Microsoft cannot guarantee when reboots will affect your deployments, however you may want to ensure that your web and/or worker roles are in separate update domains to ensure uptime for mission-critical applications. Being an RSS feed, it’s easy to add to your favorite daily digests to ensure you’re always up-to-date on the latest changes.

**Note: Windows Azure will be renamed to Microsoft Azure, beginning April 3, 2014


Mar 28 2014

Solution for a Sharepoint 2013 document library list view

Tag: OtherMark Jordan @ 8:09 am

I recently needed to develop a solution for a SharePoint 2013 document library list view. Normally, I would be able to get ideas from others on the Internet, if not get a complete solution from the likes of codeplex.com or stackoverflow.com. To my surprise, I could not find what I believed to be a seemingly simple solution. The solution I needed was to provide a hyperlinked title in a document library.

Normally, a document library would provide three types of document name fields: text-only, hyperlink, and edit control block menu. The title field in a document library does not have the hyperlink and menu options like a regular SharePoint list. The requirement in my case was to provide the title with a hyperlink option, and also default this column to show the file name if the title was blank. Following is an account of how I provided this solution.

The two primary strategies I employed for my solution were:

  1. Create a calculated site column declaratively.
  2. Utilize the JSLINK strategy that is new to the SharePoint 2013 environment to override the rendering of the column.

Note: I know how frustrating it can be to only see screen shots of code; we developers like code to copy. For this reason, you will find a link to a zip file of this Visual Studio solution at the end of this article.

I first created a Visual Studio solution having the project and file structure as shown in the following figure:

I first created a Visual Studio solution having the project and file structure as shown in the following figure:

 

 

 

 

 

 

 

 

 

 
The DocumentLibraryTitleLink item is a site column that I added to the project using Visual Studio’s “Add Item” menu item. The elements.xml file contains the declaration of the site column; the following is the code within this file:

    <Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<Field

ID=”{98ea9229-5598-46d6-9895-63930529b7a5}”

Name=”DocumentLibraryTitleLink”

DisplayName=”Document Library Title Link”

Group=”C/D/H Custom Columns”

ReadOnly=”TRUE”

Type=”Calculated”

ResultType=”Text”

Hidden=”FALSE”

Required=”FALSE”

ShowInDisplayForm=”FALSE”

ShowInEditForm=”FALSE”

ShowInFileDlg=”FALSE”

ShowInListSettings=”TRUE”

ShowInNewForm=”FALSE”

ShowInVersionHistory=”FALSE”

ShowInViewForms=”TRUE”

JSLink=”clienttemplates.debug.js | ~sitecollection/Style Library/CDH.SPFieldDocumentLibraryTitleLink/js/jslink.js”

>

<FieldRefs>

<FieldRef Name=”Title” />

</FieldRefs>

<Formula>=IF(ISBLANK([Title]),”",[Title])</Formula>

</Field>

</Elements>

 

A few notes regarding the attributes of the Field tag within this code:

  • This field is hidden from all forms except the list view.
  • The JSLINK attribute will load two (2) JavaScript files, one being a SharePoint out-of-the-box file and the other from my custom solution.
  • The formula for the field basically copies the title from the standard Title column. The reason for the conditional is so it will not produce a result of 0 (zero) if the title is blank.

The jslink.js file contains code that will:

  • Override the rendering of the column in the list.
  • Provide the necessary support methods for the override. These support methods are modified copies of SharePoint methods found in the clienttemplates.debug.js file.  I wanted the logic to be similar to already-existing functionality.

Following is a the beginning lines of the jslink.js file that does the rendering override logic:

  if (!CDH) {

var CDH = {};

}

if (!CDH.SPFieldDocumentLibraryTitleLink) {

CDH.SPFieldDocumentLibraryTitleLink = {};

}

CDH.SPFieldDocumentLibraryTitleLink.RegisterOverride = function () {

var override = {};

override.Templates = {};

override.Templates.Fields =

{

// For the Title field, delegate the “view” action to our method

‘DocumentLibraryTitleLink’: { ‘View’: CDH.SPFieldDocumentLibraryTitleLink.ShowTitleField }

};

SPClientTemplates.TemplateManager.RegisterTemplateOverrides(override);

};

CDH.SPFieldDocumentLibraryTitleLink.ShowTitleField = function (ctx) {

var returnValue = “”;

returnValue = CDH.SPFieldDocumentLibraryTitleLink.LinkTitleOrFilenameNoMenu(ctx.CurrentItem, ctx.ListSchema);

return returnValue;

};

The CDH.SPFieldDocumentLibraryTitleLink.LinkTitleOrFilenameNoMenu method is defined later in the jslink.js file, which is in the Visual Studio solution that is downloadable at the end of this article.

I hope this article can help someone with the same type of solution. I can see this solution being enhanced to also include rendering of the title field with the menu. If you have any questions, please don’t hesitate to email me (markj@cdh.com) or leave a comment on this blog post.

**Note: Solution file that can be downloaded: CDH.SPFieldDocumentLibraryTitleLink


Next Page »