Saturday, September 17, 2016

Tuesday, August 30, 2016

Things I need to write about

Converting Office documents to archives and using Agent Ransack to pick the document apart.  Comment below if want more info.  This will be a growing list.

Saturday, June 11, 2016

Win32 Error Browser & Search

image

Straight from WINERROR.html:

image

Search includes progressive F3 search.

Small break between SharePoint/Project Online projects.

If you want it, contact me

Wednesday, May 25, 2016

Reminiscing

Skating to blood, tears, exhaustion and civil arrest,listening to Skinny Puppy and remembering playing Bubble Booble at the Student Union Building at Central Washington State University circa 1987-1989:

 

Back to work…

Monday, April 11, 2016

A Comparison in Brevity Between Straight CSOM and OSoFx

I am working with SharePoint and Project Server CSOM (Client-Server Object Model) for both SharePoint and Project Server for some months now.  This API is a replacement for the traditional XML/WCF web services exposed by both products for years now.  The APIs are rational, consistent, and do not require the usual rigging for a web service (endpoint configuration, proxies, and the various other scaffolding required to consume the web services).  These are all great improvements.

Note that the CSOM for both SharePoint and Project Server, to date, implement a subset of the functionality of the traditional web services—and performance work is ongoing in the product groups.  Like anything new out of these SDKs, it takes investment to reach parity in feature completeness and performance.  That being said, get on it Microsoft!

I found CSOM is repetitive and while vastly less costly in terms of key strokes, it is nonetheless bulky and disjointed.  Also, because I tend to use both the SharePoint CSOM and the Project Server CSOM in the same project, I decided I was ready to put something together like mpFx.  The term “mpFx” means “Microsoft Project Effects” or, what I prefer “Microsoft Project Feature eXtensions”, which is more descriptive.

I set out to design a single API for accessing SharePoint and Project Server through a single library, with the ability to request services from Azure such as Cloud Storage, Cloud Services, DocumentDB, Managed Cache Services, and others through a “late-bound factory”, so as not to burden the basic API.  In addition to CSOM, the library will expose oData from both SharePoint and Project Server.

This new API is call OSoFx, pronounced OH-SO-FX—Office Server Online Feature eXtensions.  OSoAFx maybe, as in Office Server Online and Azure Feature eXtensions—pronounced OH-SO-A-FX?

A combined API allows for myriad benefits, but in today’s post I want to demonstrate the differences in syntax and the brevity of the API. 

The following operations are performed by both straight CSOM and OSoFx (both servers are Office Online):

1.) Setup credentials

2.) Create a connection to Project Server

3.) Create a connection to SharePoint Server

4.) Present the version numbers for both servers

5.) List the projects

6.) List the sites

7.) Show how long it took to do this

Here is a side-by-side, the first straight CSOM and the second OSoFx

Straight CSOM

image

OSoFx

image

There is a bit of work behind the scenes in OSoFx to make this work, but the fruits of labor can be used by others.  More on this later!

Chief Technology Architect @ DeltaBahn LLC


I recently moved to DeltaBahn LLC, a Texas-based company specializing in Microsoft Office Online, including Project Server and SharePoint, in addition to Microsoft Project Server and SharePoint Server on-site.  We also provide solutions to integrate and enrich project data with connectors to external systems.  We also offer general software development services,

The majority of our employees are former Microsoft employees with decades of experience working both at Microsoft or with Microsoft partners.  Not only do we have the experience, but we love this industry.

"Your success and satisfaction is what matters most. We listen and understand, we know what works, and we follow time-proven methods that have been adopted as Microsoft best practices"

I encourage you to visit our site and learn more about us. I am excited to be here (there are a lot of smart people working here, which you know I like).

I have some availability right now to provide custom development services if you have a Microsoft-based project. I work primarily in Azure, ASP.NET, SharePoint, Project Server, Windows Apps, Microsoft SQL Server, Exchange, oData, CSOM/JSOM or anything else .NET-related (C# and JavaScript are my primary languages). Let me know if you need any help!

Additional information on LinkedIn.



DeltaBahn LLC Logo
Copyright 2015 DeltaBahn LLC | All Rights Reserved | Email: success@deltabahn.com | Contact us: 1.281.344.0437

Monday, February 29, 2016

Continuing the Tradition… Coming Soon OSoFx

In 2007, with the advent of Project Server 2007, I started the mpFx project to provide a simplied API for the Project Server Interface.  That work has taken me a long way, including landing me a job in Microsoft Consulting Services and further down the road, a lead role at forProject Technologies.  These days, I am focusing most of my technical effort on SharePoint/Project Server Online and Azure.

In the tradition of mpFx, I have started a new project called OSoFx, pronounced “oh-so F X”, which provides a single interface into SharePoint Online, Project Onine (including CSOM, oData, and PSI) and Azure.

More to come!

Monday, February 01, 2016

Project Server CSOM, REST, oData, and Deployment (2013 & 2016

CSOM, Rest, and oData Support

Starting with SharePoint 2010, a new integration technology was introduced called CSOM, or Client Side Object Model.   The API is an alternative to using web services.  It is a much cleaner API.  Not only can you utilize CSOM in a .NET application such as WinForms or WPF, you can use it in your browser-based apps.  If you prefer REST, you are in luck as it too is supported.

When Microsoft released Project Server 2013, the product group embraced the CSOM model .  It is important to understand what it is capable of and its limitations.   In Project Server 2013, many of the PSI web services you are accustomed to programming against are still available.  Visit this page for the full set of types and examples to get you started.

Project Server 2013 supports both online and on-premise implementations.  Using oData is really the best way to get at data which was once stored in the Reporting Database.  Project Server’s oData reference can be found here.

One thing you will notice right away is that Project Server 2013 ships with a single database.  The drafts, published, archive, and reporting database are combined and schemas are used to separate the various content containers.

The introduction of the Project Calculation Service puts the server-side scheduling engine to closer parity with the scheduling engine implemented in Project Professional.  This a great new feature.  For an overview of Project Server 2013’s architecture, visit this page.

In Project Server 2016, which is heading toward RTM, introduces even more changes.  You can download Beta 2 here.

Project Server 2016 Deployment

In 2016, Project Server is included in the SharePoint install by default—much like the Visio, Excel, and Access services.  You still have to purchase a server license.  Install SharePoint and run the configuration wizard just as you normally would.

To enable Project Server use the SharePoint PowerShell commandlet enable-projectserverlicense Y2WC2-K7NFX-KWCVC-T4Q8P-4RG9W.  This will give you a fully featured 180 trail.

The PWA site provisioning UI is mostly gone.   To create a PWA site, follow the steps below:

  1. Create a site collection for PWA
  2. Using SharePoint PowerShell, execute this command: New-SPSite http://ps2016/pwa –OwnerAlias [DOMAIN]\[USER_NAME] -Name “PWA 2016” -Template “pwa#0”  (note that the server and site collection may be different—that part is up to you.
  3. Also using SharePoint PowerShell, run this command: Enable-SPFeature pwasite -Url http://ps2016/pwa
  4. Optionally, you can enable the security UI in PWA.  Again PowerShell: Set-SPProjectPermissionMode, which will prompt for the PWA URL and the Mode, which is ProjectServer

Credit for the PowerShell commands: https://binoeder.wordpress.com/2015/12/19/deploy-pwa-in-project-server-2016-beta-2/

 

Disclaimer

Content on this site is provided "AS IS" with no warranties and confers no rights. Additionally, all content on this site is my own personal opinion and does not represent my employer's view in any way.