Visual Studio Code – Clearly a New Direction

I use Visual Studio Code for simple things – because its fast!  I am a die-hard full version Visual Studio IDE user, VS Code seemed to be just another “text” code editor – nothing more.

I obviously had not given it a real opportunity.  This week I have had to jump back into client-side web development; the full gambit: CSS, JQuery, Bootstrap, HTML, JavaScript.  I really don’t have any passion for this type of coding.  I prefer deep framework/platform development where we “hardcore” programmers like to dig into problems that nobody else wants.

I was covered in “client code-rust” not having touched this type of coding in several years.  I still don’t like it.  HOWEVER.  Visual Studio Code made the re-introduction to web code development actually pleasant.  I figured out that you must install extensions for pretty much anything you want to do beyond text editing.  To be honest that is about all I did until the “fun” started.  Orchestrating all the moving parts (libs) is no trivial exercise.  Things have changed quite a bit in the last several years on the client-side of the code world.

Once I figured out the Visual Studio Code debugging environment things began to move more smoothly and the pace picked up.  It is really a fairly serious tool and it seems to be improving constantly.  There are lots of extensions out there for VS Code sure to make your development process easier.

I will be using it more to be sure.  I recommend that you give it a chance too.


Reaction to Microsoft’s Inspire from a Gold Microsoft Partner

Intact is focused on Microsoft Cloud services.


It has been a week since returning from the Inspire 2017 conference.  My staff had several days to digest the input and to have informal office discussions before our company planning meeting.  We have also gathered input from other partners.

To cap it off here is my take-away:

  1. Microsoft is a different company; in a different world with a different vision.
  2. If you are not on par with Microsoft corporately, align your company vision with Microsoft’s or be well positioned with multiple companies in this space.
  3. Be prepared to invest in new people, new products, and new thinking.
  4. Make new “friends” inside Microsoft. Cultivate strong partner relationships with Microsoft.
  5. Microsoft has determined that “partner sellers” is the future which I think means developing very strong partner-to-partner alliances.

Our strategy is simple, be indistinguishable from Microsoft to customers. We are an extension of Microsoft, integrating our “PowerLine on Azure” product suite into every opening we can in the new Microsoft 365.

To customers there is an impact because of the, new Microsoft.  There must be adjustments on the part of customers.  The customer is like Intact or “in the same boat” as the saying goes.  Our realization is the world of technology changed allowing the iPhone to come into existence.  The arrival of the iPhone “event” is commonly pointed to as the pivotal moment when the “consumer” became aware of the “cloud”.  There is no going back!  Nor does anyone really want to.

I heard the most important statement (advice) a business owner could possibly hear from an employee this week, “Hire college students.  They have no knowledge of the past.”  The conversation sparking this statement came from a business analysis 20 years my junior having 20 years’ experience.  She understood people holding jobs/positions will not admit their talent is no longer necessary.  These entrenched/experienced workers will thus, “fight you and your new Code-Robotics.”

Intact is aggressively marketing Microsoft 365, while understanding that we must allow the old to pass-away with dignity and grace.  We understand that technology change is a process not an event.  We must assist customers through the death process of their trusted and beloved old systems.

At Intact we know that the future belongs to the children and we must help them achieve their place in this world while we assist those who hold it now to let go.  Life-spans of technology products is more like that of your pet than a building, just a few years.  We made the decision with conviction, in 2014 to follow the Microsoft re-invention and are already very well aligned and are improving alignment daily.

Inspire didn’t really launch anything new or demonstrate any new technology breakthoughs.  As large events go it was almost “ho-hum” – almost.  Microsoft Inspire 2017 will likely be the event where your company itself starts the process of dying or catches the real message of inspiration; become new.


DevOps and Why You Need a Managed Code Team

Cloud Computing is complex.

I have focused on cloud computing since 2007, nearly 10 years.  I write a lot of code myself for Azure Cloud and I also pay the bills giving me a real perspective.  Whoever told you or intimated that cloud computing would make your life easier as a developer, ISV, systems integrator, failed to tell you the truth.

My company Intact, is dedicated to your success. Cloud is not easy.  Read on to learn more…

If you want or expect to have it easy in a cloud world then you need to use “Software as a Service” (SaaS) apps where somebody else owns, maintains, and supports your IT needs.

If you are an IT Pro, developer, or IT manager that has mission critical applications that you support for your customers and you are already “saturated” at the team level then expect a long day when shifting to cloud.

EDIT: Azure has more than 50 individual services and growing.  There are at least 5 different ways to configure each of the majority of those.  That means that there are more than 5 million combinations to configure Azure.

Cloud over the past ten years has expanded exponentially in its service offerings.  The number of different items to contend with in porting workloads, developing new services, and maintaining control simply overwhelms whole teams.  I wrote several years ago, “No jobs would be lost due to cloud.  The jobs would change and the responsibility would change but it will still require people with new skills to run cloud applications.”

My friend (let’s call him Joe), is an IT Pro and manager who wants to learn cloud computing for his team.  I admire Joe for his desire to make the transition.  Joe’s problem is the team skills deficit in general.  Joe desires to learn cloud and implement it as he would have past projects.  My company and my team are immersed 100% in Azure Cloud.  We don’t do AWS or any other cloud for a very simple reason.  Being an expert means focusing on one thing.  Intact is focused on business applications for Azure Cloud – nothing else.  Believe me when I tell you, there are too many moving parts to cloud to think that you can “tinker” with it.  Obsolesces is measured in months not years.  You must have a continuous integration mindset about your applications.

DevOps – development and operations.  In raw form this means that the developers are responsible for the operation.  In my experience very few teams are configured for this type of computing model.  Currently responsibilities are spread across many different teams: developers, testers, security, administration, release management, maintenance, network, systems and so forth.  I have been in the hundreds of meeting where all the team leads discuss the weekly and monthly issues list.  The structure of organizations is wrong for cloud services.  You still need all of those skills but the “who” is responsible and delivering is completely different.

Intact helps teams through automation reach cloud application maturity in DevOps by supplying the missing skills.

Should you Develop in Access 2016

Should you develop or reengineer your old Access or FoxPro desktop applications in Access 2016?

NO, has been my answer for the past 10 years for any Access development. Read on for a more through explanation and considerations. Microsoft does not include Access 2016 in any of its Office 365 business packages. HINT!

Access 2016 continues into the age of cloud as an add-on purchase application in Office 365.  But Access 2016 is not the Access that most users think it is.  On the Microsoft site this statement is made:

“Access 2016 has all the functionality and features you’re used to with some added enhancements and the best new features from Office 2016.
Note: For Access 2016, no existing features or functionality from previous versions were deprecated in this release.”

This statement is completely true. BUT… as the late Paul Harvey would famously say, “now the rest of the story.”

The very short answer is that prior to Access 2013 to which the statement refers Access has been systematically stripped of functionality.  There have been “new features” added, true.  When Microsoft removed the ability for later versions (2007 >) to open older database structures they introduced “new features” to replace the functions. (see this article: )

So should you develop a new application or reengineer an old one in Access 2016?  The answer is a solid maybe.

I might be oversimplifying some but this should give you some sense of how to approach the problem.

  1. Who is going to be doing the development?
    • Business users
    • Professional developers
  2. Will the resulting project be a critical business application?
  3. Will the database be on a managed SQL Server?
  4. Do you or your organization have any database reporting tools?
  5. Who is responsible for the application maintenance and updates?
    • Business users
    • Professional developers

Generally, if any of the above is answered “Yes” or a developer is expected to be involved then Access is not the way to go.

For line of business applications Access requires the same amount of development effort that any other professional development would require.  Access now requires a per-user subscription and it requires a SQL-Server database subscription or on-premises license.  Yes, SQL-Express license is free.  If you are a professional developer, there are other tools that are very effective for line of business solutions.

Why change if what you have works?
There may be no reason particularly if you upgraded your systems over the years and your current implementation is in Office 2013 and your data is already on a SQL-Server.

As you read this remember Access was developed for Windows desktop computers.  It depended on Windows and plethora of Windows drivers installed on a specific computer to work.  It was not a server application.  In the workplace it was very limited by design to run in a desktop with limited memory and disk-space.

Most Access database implementations are Windows “desktop” applications.  Over the 25-year history of Access it slowly morphed from a database engine with an application frontend for desktop to now just a fancy web site development tool that hooks to a SQL Server.

Up through Access 2007 you could create a database separate from your Access Application.  That was considered a great feature.  Application developers commonly would develop for Windows computers applications in programming languages such as Visual Basic, C/C++, Delphi, and many others.  These applications could use Windows installed drivers to connect to an Access database engine.  In many cases a copy of Access was not required to use the Access database.  During these years many companies sold third-party “controls” made for Windows desktop computers.  Access allows these to also be used in an Access desktop application.  There is a major problem with controls in modern applications, they mostly don’t work anymore.

Microsoft has discontinued many drivers because they do not meet modern security standards and many were targeting Windows desktop clients that are no longer supported such as Windows XP, Windows 7 (at end of life), Windows 8.

If you are moving to Windows 10 then you are very likely to have issues with Access applications or applications that used the Access database engine.  Consider moving to a different platform that is better suited for line of business.

If you have a small application that is not critical to your business, you should seriously consider a cloud software as a service (SaaS).  You get high reliability and professional software maintenance that you don’t have to worry about.

Reporting is the one use of Access that might make sense but only in a limited sense.  The reason is simple; Microsoft is making its Office 365 apps programmable.  Word and Excel are clearly the cornerstones of the Office 365 product line.  Both now have very advanced development API capability that integrates with all Microsoft products.  Access will continue to be part of the Office 365 product line for years to come but its use is quickly becoming a niche market.  The original purpose for which it was created in now a thing of the past, the desktop database.

I would only recommend Access as a solution for trivial applications, training, or for a very specific needs case.  The number of variations introduced over the years makes understanding what you really have in Access very difficult.  So much of Access was dependent on the specific version of Windows and its installed drivers it is very difficult to predict if it will work in new modern environments.

Below are links to Microsoft documentation to substantiate my assessment.

Deploy .NETCoreApp to Azure Service Fabric

Should be obvious how to do this.

Either it is not obvious or I am really slow (yep, left myself open).  So you can’t wait to use the .NET Core 1.0.x platform and you are a glutton for punishment like me.  You want to get your brand new .NETCoreApps up on Azure Service Fabric.  Well it is not exactly clear how to do this and the Visual Studio templates don’t help here.

Note: Visual Studio 2015 Update 3 with latest tooling as of this post date do have an ASP.NET Core template for Azure Service Fabric.  But ASP.NET Core is not a .NETCoreApp.

Why do you want to do this? In my case, my company has been steadily porting our aging .NET Framework libraries to the new .NET Core.  I do not want to go back to the old .NET Frameworks.  Microsoft just informed we developers about the new .NET Standard 2.0 here.  If you were around back in the late 1990’s and very early 2000’s you likely struggled with the transition from ASP Classic to .NET 1.0/1.1.  If that wasn’t enough .NET 2.0 quickly followed.  There was no direct port from the 1.1 to 2.0 back then.  It seems that we should have learned by now that 1.x anything is just a trial run.  So we all have deja vu with .NET Standard 2.0.  Yeah this time its going to be better…  My fingers are crossed.

The Nitty Gritty

So I promised to tell you how to deploy your .NETCoreApp to Azure Service Fabric.  The first thing to know is this is a “guest executable” in service fabric. Read this article for background here “Deploy a Guest Executable to Service Fabric”.  I expect that you have a working .NETCoreApp that you want to run in Azure Service Fabric ready and tested locally.  The best way to do the deployment is to use Visual Studio as the article describes.  But you must do a little prep-work first for the .NETCoreApp to make it work.

It is utterly simple. In Visual Studio with your desired .NETCoreApp, right-click the project.  From the context menu click “Publish…” and use “File System” as the target location.  Make a note where you put your output.  The default is bin/release.  This causes Visual Studio to gather all the files necessary to run your application into a single folder.  The current Visual Studio tooling does not do this for .NETCoreApp when publishing to the fabric.

Now that you have a complete package you are ready to create your Azure Service Fabric guest executable.  From Visual Studio create a new Service Fabric project and select the guest executable template.  A configuration dialog appears. In the required Code Package input field browse to the folder discussed above and select it.  If you are still developing your .NETCoreApp select the “link” to your code and also choose “CodeBase” for your work folder. From here you publish your .NETCoreApp to your Azure Service Fabric (cloud or local).

Parting Shots:

If you are still developing your .NETCoreApp you will have to repeat the publish cycle every time you want to test in the fabric.

The clue to the problem was found in the Microsoft documentation article mentioned above.  The tip off was this statement:

Service Fabric does an xcopy of the content of the application root directory…

That simple statement and the word “xcopy”.  The ah-ha! moment.  All the reference libraries are not present in the bin folder!  Visual Studio keeps all the standard libraries in a common location on the local computer.

I hope this saves you a bunch of time.

New Microsoft .NET Core Changes Many Application Responsibilities

My company is devoted to the Microsoft .NET platform and the Azure cloud services.  Cloud services are not simple even though the hype seems to indicate such.  Cloud applications are different (or should be) to take advantage of cloud services.  Writing cloud applications is not an extension of yesterday’s coding methods.  Supporting and release management of cloud applications is also different from prior systems.

Intact Partners produces software application platform services and development automation software called PowerLine with Compose. The major advantage of PowerLine platform is performance and cost enhancements at development and with on-going application maintenance.  PowerLine can reduce development coding effort by as much as 80% through its robotics.  Below I hope to show you why PowerLine with Compose is a sound decision.

It seems to me many people like the “New Microsoft” and its new open source .NET model for application development.  The old .NET Framework is now 15 years old and still tied directly to Windows OS’s.  The new .NET Core is a ground up rewrite that separates .NET from Windows making a cross platform development environment for other competing OS’s such as iOS and Linux and other languages such as Node, PHP, Java and more.  That is generally great news to the non-Microsoft community.  I happen to agree even though I am a .NET/C# developer.


So things have changed and .NET Core is now the shining light as the centerpiece of the .NET development effort at Microsoft.  If you are a developer or a business person with applications written with the .NET Framework you should take heed.  Your job is changing.

Lets quickly review Microsoft official position, CEO Satya Nadella continues to declare “Mobile First, Cloud First World”.  This simply means that Microsoft is committed to Azure and Windows 10 with its money.  Azure is Microsoft’s “open cloud platform” meaning Azure will run other operating systems non-Windows.  Microsoft wants apps to run on Azure supporting Windows 10 regardless of the OS.  Solution: create a single code base supporting Microsoft’s goals.  This code base is .NET Core.

Even though the company promised over a year ago support for .NET Framework 4.6.2 in Azure it still is not available.  Now, the older Azure services supporting .NET Framework are listed as “classic”.  One likely should conclude, Microsoft is not “innovating” with .NET Framework anymore (no investment in new features).

Read this 12/2014 quote from Microsoft , “The .NET Framework is still the platform of choice for building rich desktop and .NET Core does not change that” [emphasis added].  This same statement was repeated in 7/2015.  A discerning developer should quickly see that mobile, server, web, and cloud were not mentioned in the statement.  If you are a Windows desktop developer only then you are OK with .NET Framework.  The rest of us should be developing .NET Core.


I will not cover .NET Core in detail, ample coverage is being done by Microsoft on MSDN and the community at large.  What I want to impress upon you is the shift in responsibilities occurring with .NET Core implementations.  There are many structural changes in .NET Core.  Development is similar but it is different significantly enough that old development habits will have to be broken.  Update and release patterns are significantly altered.  The alterations are subtle if you are not tuned-in to Microsoft’s release pattern changes.

Microsoft release pattern changes. All operating system updates are now only released as cumulative updates.  Immediately this affects all applications impacted by system patches which also includes security and compliance patches.  In the past where applications were dedicated to Windows servers the patches were generally applied by the server administrators. Microsoft fixed a real issue with this method where .NET Framework updates broke existing applications in 2010.  The .NET Framework 4.0 release allowed side-by-side installs of the framework on the same machine.  The problem is not the .NET Framework.  The issues going forward for applications is .NET Core does not depend at all on Windows Server and any of the installed frameworks.  In fact .NET Core does not depend on Windows OS of any kind and .NET Core does not need .NET Framework installed on the server as in the past.

What this means.  The responsibility to update/patch your application shifted from the server administrator to the developers or vendors.

With no framework how does this update stuff work?  Simply put you need PowerLine with Compose.  PowerLine is a managed set of cloud services that are maintained as part of the system services powering your application.  Compose is a development and maintenance tool.  Running your application in Compose regularly automatically imports updates and security patches from Microsoft and tests those as part of its operation.

The tide is out, the ballgame is over, cat is out of the bag – however you like to describe things you really can’t control; the fact is every application including most desktop ones are now legacy.  It is not a matter of if you adopt, it is when will you.  A person in my office asked me, “What are they [application owners] going to do?  There are too many applications at risk now.”  I hope you get started with PowerLine with Compose quickly.

Cloud Business and Florida Hurricane Hermine

Eleven (11) years since the last hurricane hits Florida!  My company, Intact Partners, is an “all-in” cloud business.  Office 365 Enterprise, Microsoft Azure, and Visual Studio Online (TFS) its business as usual, almost.  The “almost” is just related to the fact that employees are working from their homes using Skype for Business.  All of our work, applications, and files are safely stored away on the cloud.  We haven’t missed a beat!

So last night hurricane Hermine rolled into Tallahassee, Florida.  We lost power at our house at 1:32 AM. No electrical power, no cable, and no Internet. (No Internet is caused by the wide area power outage taking down backbone services.)  No worries here.  The backup generator is powering the house, Windows Phone is providing Internet service and my Surface Pro 3 is providing all my normal services.  Business as usual for Intact Partners.

When you think you business continuity is better in your local datacenter, my experience says you are wrong!  This in not the first time I have experienced Microsoft Azure coming through in a hurricane.  When I was CIO at Florida Department of State during the 2012 presidential election I had moved the election system to Azure.  Hurricane Sandy rolled over Virginia where one of the Azure datacenters is located.  It happened on the first day of early voting in Florida that year.  To prove the disaster recovery ability of the system we constructed on Azure I “failed-over” our service from the San Antonio Azure center to the Virginia center just after Sandy.  Florida’s election 2012 was run on our Azure disaster site and was a total success.

This morning as I compose this blog, I am at home with my family as are my employees are with theirs, not worried about business interruptions for my company and more importantly I am not fretting about my customers.  Their services are safely and securely operating in Azure.  The people I am praying for this morning are the more than 100 thousand people without power and the crews working hard to restore power and save lives.  I will continue to pray for those who are still in the path of Hermine as it rolls on north up the east coast today.

Larry Aultman, CEO
Intact Partners