Recently, I needed to be able to parse Excel files and to output Excel files. However, I found that my old code from previous blog posts were now problematic:
Those old implementations used EPPlus which is now a commercial product. I wanted something open source.
One of the more interesting things from Build was the move to provide different databases as services. Since this opened the possibility of moving my LAMP-based WordPress instance to Azure, I decided to give it a try.
During Build, one thing that was demoed was the in-line bash shell that is available from the Azure Portal. I couldn’t get this feature, I guessed, to work due to not having a storage account configured.
Day two of Microsoft Build is slowly coming to a close. Here are a few of my impressions after two days.
A couple of weeks ago, I wrote about deploying multiple applications to Azure virtual directories from a single Git repository to Azure. That method works well. However, it by default only supports building and deploying a single .NET project. This was fine in my previously example in which only one of the deployment projects I had was .NET based. Using a custom KUDU script, it’s possible to deploy multiple .NET applications to the virtual directories from a single git repository.
Azure added support for Virtual Directories a while back. It’s easy to add a virtual directory. One issue, though, is deploying to those directories since Azure only supports a single Git (or other) source control repository for the web application.
After using OWIN for months for basic OAuth authentication, it’s apparent that Microsoft is abandoning OWIN . This isn’t necessarily a bad thing. .NET Core is built on a similar structure as that which was implemented in OWIN. Essentially, we have a familiar middleware pipeline.
Earlier, I wanted to play around with Angular CLI, but my npm and node versions were out of date. The Angular CLI npm install would fail.
Fortunately, there is a straight-forward update method.
On github, the Microsoft team has placed a method for updating node through PowerShell:
I was happy to stumble upon this on Github. After using the script in the recommended fashion, from an elevated PowerShell console, the Angular CLI npm installer worked without a hitch.
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
npm install --global --production npm-windows-upgrade
Previously, I wrote about parsing an Excel spreadsheet to a list of objects. This is a pretty useful technique, but what do you do if you want to provide the user with an Excel template to get started? Being able to provide them with an initial template based on your object model is a good starting point.
Business people love their Excel spreadsheets. Fact. As such, I work with Excel a lot to parse and manipulate data. However, from a .NET perspective, Excel in its raw form isn’t overly useful. Being able to take an Excel worksheet and build a List<T> can be extremely useful.