Office Development – Word.RequestContext vs Word.run

MinimalCode 2

Yesterday we’ve seen the minimal code running to insert a bit of text at the selected Range using Word.RequestContext:

(() => {

   async function MinimalWordmethod() {

      // Create the client request context. You’ll do this for all Word add-ins.

      var ctx = new Word.RequestContext();

      // Do your things here, such as ..

      var range = ctx.document.getSelection();

      range.insertText("Test MinimalWordMethod", "After");

      await ctx.sync();

   }

   MinimalWordmethod();

})();

If you look however at the boilerplate code that is generated with a clean Yeoman project you find that RequestContext is never used, but instead of this you see Word.run(async (context) => { … });

Why is this and what is the difference? Well, I looked into this and found the answer on a piece of documentation from Michael Zlatkovsky, member of the Office Extensibility Platform team, here:

http://buildingofficeaddins.com/run

Michael explains it in his documentation but is written for Excel, however as you can read on the same page it is fully compliant with Word.run.

Here is a quote from the page:

You can think of the Excel.run as a boiler-plate preamble; it is the batch function that is the star of the show, but it needs a request context in order to start off the chain of OM calls. The Excel.run call is simply a means to that end, as it creates a new request context that it passes into the batch function.

Reading this quote explains that by using the <host>.run function you start a batch process, without the trouble of creating your context by yourself. The run function will take care of this for you. So instead of the code where you create your own context object as seen in the snippet above you should be able to run the following code:

(() => {
   async function MinimalWordmethod() {

         // Create the client request context. You’ll do this for al Word add-ins.
         await Word.run(async (context) => {

         // Do your things here, such as ..
         var range = context.document.getSelection();

         range.insertText("Test run MinimalWordMethod", "After");

         await context.sync();
      });
   }
   MinimalWordmethod();
})();

How to get the new minimal code running

Go back to the Yeoman project from yesterdays post, open the project folder and open the file app.ts in the src source folder.

Replace all the code from this file as seen in the top snippet with the code from the second, new snippet above. Save it and start your Add-in ‘server’ by running npm start in the root of your project.

Opening Word, with the installed Add-in will still show you the Add-in button:

addin7_thumb

By clicking the button the Taskpane is showing, just like we’ve seen before, but now you should see the words “Test run MinimalWordMethod” in your document:

MinimalCode3

Without creating your own context the Word.run function created its own context and the code still works. As you can see this helps you to take some effort out of your hand.

To be continued …

Office Development – Minimal Code in practice

MinimalCode

Returning on my last ‘minimal code’ blog post, I promised to get back on this to see how this works in practice. One of my question marks I added to the post was that I wondered why the Yeoman boilerplate was using run instead of RequestContext where run passed a context parameter as opposed to the RequestContext where actively a context is requested before accessing the Word object model.

I think I found an answer to that, but will save this to a later date as I first want to make sure the minimal code I provided would work and I found some issues in the original posted code that didn’t seem to be correct.

Here is the updated code that should work in real life:

(() => {

   async function MinimalWordmethod() {

      // Create the client request context. You’ll do this for al Word add-ins.

      var ctx = new Word.RequestContext();

      // Do your things here, such as ..

      var range = ctx.document.getSelection();

      range.insertText("Test MinimalWordMethod", "After");

      await ctx.sync();

   }

   MinimalWordmethod();

})();

How to get the minimal code running

If you go back to the Yeoman project instructions in this post (and fixed the certificate issues in post Office Development – Fixing Trusted Authority – Word Client and https://maartenvanstam.wordpress.com/2017/08/07/office-development-fixing-certificate-issue-with-openssl-certificate/) you should already have a working Word Add-in.

Open the project folder (or if you already deleted it quickly create a new one following my instructions from my earlier blogposts) and open the file app.ts in the src source folder.

Replace all the code from this file with the code above, save it and start your Add-in ‘server’ by running npm start in the root of your project.

Opening Word, with the installed Add-in (again, if you already dropped it follow my other blogposts earlier this month to install it) will show you the Add-in button:

addin7

By clicking the button the Taskpane is showing, just like we’ve seen before as we haven’t changed the Taskpane ‘web’ code, but now you should see the words “Test MinimalWordMethod” arriving in your document:

MinimalCode2

As you can see the code worked! Here is how:

MinimalWordmethod();

This line is automatically triggered when the code is running on startup of the Add-in. By doing so inside the MinimalWordmethod a context is requested in this line:

var ctx = new Word.RequestContext();

If the context is returned correctly you now can access the Word object model to access parts of the document. In this case we access the selected Range object and insert the text right after the Range:

var range = ctx.document.getSelection();
range.insertText("Test MinimalWordMethod", "After");

Instead of having this executed immediately like we’ve seen in VBA or VSTO, the text is only inserted after calling the sync method on the context. In the JavaScript APIs for Office calls to Office are handled asynchronously and to work with that the await and async keywords can be found in the code.

Very simple and basic code, but there are some drawbacks you need to keep in mind. For instance, because things are async, how do you know what the right order is how things are processed. And what about batch processing of boatloads of instructions? Will this all be handled correctly, and what if there are dependencies between the batched instructions? All of these questions arise when looking at this little piece of code, and we need to address all of that in later posts.

To be continued … It’s a never ending story Smile

SDN Cast 63 – New SDN magazine and .NET Standard 2.0

SDNCast 63-800

Theme of the week in our Dutch SDN Cast was .NET and .NET Standard. .NET Standard 2.0 was released this week, you could already read about it in my ‘special’ post earlier this week. There was a whole set of releases: .NET Standard 2.0, .NET Core 2.0, Entity Framework Core 2.0, Visual Studio 2017 Version 15.3 and more …

We discussed not only the new releases but also other news like adding VB to the .NET Core CLI, new Apple betas, Xbox Live Creators Program and more. Despite the holidays low season, a lot of news to talk about!

Also, this week the release of our new Dutch SDN Magazine, ready for download. The download links are in the show notes below. Dutchies, go ahead and download it today!

Where can you find our 63th episode of our Dutch SDN Cast?https://youtu.be/KNFnlgRkjzA

Did you subscribe our Dutch SDN Cast channel already?

Subscribe your YouTube channel if you don’t want to miss a single broadcast. Usually we will broadcast on Thursday evenings at 8 PM but there can be a change of plans where we need to move to another time or day. So to be sure Subscribe to our channel on YouTube or go to http://www.sdncast.nl to see when the next episode is due.

Other news:

Announcing .NET Core 2.0
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/

Announcing .NET Standard 2.0
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-standard-2-0/

Announcing Entity Framework Core 2.0
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-entity-framework-core-2-0

Visual Studio 2017 Version 15.3 Released
https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/visual-studio-2017-version-15-3-released/

Accessibility improvements in Visual Studio 2017 version 15.3
https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/accessibility-improvements-in-visual-studio-2017-version-15-3/

F# and .NET Core Roadmap Update
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/

New for Visual Basic: .NET Standard Class Libraries and the dotnet CLI!
https://blogs.msdn.microsoft.com/vbteam/2017/08/14/new-for-visual-basic-net-standard-class-libraries-and-the-dotnet-cli

Xbox Live Creators Program Is Now Live!https://blogs.windows.com/buildingapps/2017/08/10/xbox-live-creators-program-now-live

New Apple Beta (6) Downloads Now Available
https://developer.apple.com/news/?id=08142017a

Over 500 extensions in the VSTS/TFS marketplace
https://blogs.msdn.microsoft.com/bharry/2017/08/16/over-500-extensions-in-the-vststfs-marketplace/

Dutch SDN Magazine 132
https://www.sdn.nl/MAGAZINE/ID/1292/SDN-Magazine-132
http://www.sdn.nl/portals/1/magazine/SDN_Magazine_132.pdf

Events

Upcoming events

Agile 2017 – August 7-11 2017, Orlando FL
ttps://www.agilealliance.org/agile2017/

MvvmCross .NET Summer Hackfest, August 21-September 2, Amsterdam Closing Event
https://www.mvvmcross.com/hackfest

Google Developer Days Europe – September 5-6, Krakow, Poland
https://developers.google.com/events/gdd-europe/

Wazug – September 7 2017, Hilversum
https://www.wazug.nl/Event/Details/2059

Microsoft Edge Web Summit 2017 – September 13, Online
https://summit.microsoftedge.com/

MixUG – Development Event – 13 September, Gouda
https://www.eventbrite.nl/e/tickets-mixug-development-evenement-34890959800

Xamarin Dev Days – 16 September – Amsterdam
https://ti.to/xamarin/dev-days-amsterdam-2017

.NET Conf – 19-21 September
http://www.dotnetconf.net/

Microsoft Envision – September 25-27 – Orlando
https://www.microsoft.com/en-us/envision/default.aspx

Ignite 2017 – September 25-29 – Orlando
https://ignite.microsoft.com
https://myignite.microsoft.com/sessions

Hybrid IT Event – September 26 – Maarssen, NL
http://www.fujitsu.com/nl/microsites/hybrid-it/event/index.html

Xamarin Event – September 28, Nieuwegein
http://events.4dotnet.nl/xamarin-event/

4DotNet Events – Xamarin Event – 28 September, Nieuwegein
https://events.4dotnet.nl/xamarin-event

MixUG – End-user Event
https://www.eventbrite.nl/e/tickets-mixug-eindgebruikers-evenement-34890983872

SDN Event 3 – 6 October 6, Zeist, NL
https://www.sdn.nl/EVENTS/6-oktober-2017

TechDays October 12-13, 2017 RAI Amsterdam 
http://www.techdays.nl/
https://techdays.msnlevents.net/content/eventselection.aspx?eventid=26152

SharePoint Saturday Belgium 2017, October 21, Brussels BE
http://www.spsevents.org/city/brussels/brussels2017

SharePoint Unite – October 24-26, 2017, Haarlem
https://sharepointunite.com/

Web Summit – 6-9 November 2017, Lisbon, Portugal
https://websummit.com/

Visual Studio Live! November 12-17 2017 Orlando, FL
https://live360events.com/events/orlando-2017/vslive.aspx

As usual we are always looking for presenters for our own events and Meetup’s so if you want to share something about hot technologies or just about something you implemented at work or in an App that could be interesting to our audience let us know so we can schedule you for one or our next SDN events or Dutch .NET Group Meetups.

This off course also goes for if you want to write a great article for us to publish in our SDN Magazines or at our SDN Website. The downside of publishing a magazine article is that there can be sometime between writing the article and publishing the magazine. So, if it is time critical sometimes the best option is to publish it on the www.sdn.nl website to get more speedy attention to the article.

As you see, options enough to address your audience with top notch information. You can even, if you like, be our guest in our SDN Cast shows to discuss the projects you are working on or other topics you master. We will instruct you how to connect with us and what it is you need to join the show.

Hopefully we will see you at our weekly web cast, for the schedule go to www.sdncast.nl for next week’s announcement to find out the day and time of our next broadcast or go to www.sdncast.nl/youtube to watch old episodes and videos that we recorded at our events. Don’t forget to subscribe our YouTube channel www.sdncast.nl/subscribe or go directly to YouTube not to miss any of our shows!

Office Development – Word Add-in, minimal code

So far it has been fairly complex, installing lots of components and doing all sorts of things before you get things to work. But what do you need for code to do just the minimal thing in a Word Add-in?

Initially it is said that a context is required by requesting a new context:

var ctx = new Word.RequestContext();

With this context you can do things the things you’d like to do.

function MinimalWordmethod() {
  
// Create the client request context. You’ll do this for al Word add-ins.

   var ctx = new Word.RequestContext();

   // Do your things here, such as ..
   var range = ctx.document.getSelection();

   ctx.executeAsync()
     
.then(function () {})
     
.catch(function(error){
        
console.log("ERROR: " + JSON.stringify(error));
     
});
}

Interesting part is that this RequestContext is not to be found in the Yeoman boilerplate, so it looks like it is initialized by the framework these days …

I want to find out where this happened in the Yeoman boilerplate. As far as I can tell the documentation is not all too clear about this.

To be continued too Winking smile

.NET Core 2.0 Released!

dotnetcore20released

Usually I share the news of the week after our weekly Dutch SDN Cast but I really didn’t want to wait for this as it is just great news that you should hear immediately (if you haven’t already heard from in the social web).

Well, let’s have it:

Announcing .NET Core 2.0
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-core-2-0/

Announcing .NET Standard 2.0
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-standard-2-0/

Announcing Entity Framework Core 2.0
https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-entity-framework-core-2-0

Visual Studio 2017 Version 15.3 Released
https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/visual-studio-2017-version-15-3-released/

A whole lot of releases, all more or less related to each other but still, great news!

With .NET Core you get:

  • Fasted version of .NET
  • More (a lot more!) APIs
  • More project templates
  • More distros
  • Simplified packaging
  • New and improved Visual Studio tooling
  • Visual Studio for Mac support

It is way too much to put in one blog post so start with watching the video by Scott Hunter and his team:

[youtube https://www.youtube.com/watch?v=Q2mMbjw6cLA] Have fun and enjoy the new bits!

Office Development – Coding in Script Lab

clip_image002

One of the nice things in Script Lab is that you can connect it to GitHub allowing you to share your code snippets or import code snippets from other people. If you opened the Script Lab Task Pane you will notice this little person icon with an even smaller plus sign.

clip_image004

With this button you can authorize Script Lab to access your GitHub account where it needs read and write access to read or write Gists. According to GitHub:

Gists are a great way to share your work. You can share single files, parts of files, or full applications. You can access gists at https://gist.github.com.

A great option to either store your scripts that you created by Script Lab for your own use but even better: to share the code with others. Get feedback, or simply make someone happy by providing the code to the community!

Clicking the button will ask you for your permission on your GitHub account. The permissions are not all that shocking, you just give permission to create, edit and get Gists from your account to be able to show it in Script Lab.

clip_image006

After providing your authorization you can go into your GitHub account and see the permission you just granted to Script Lab:

clip_image008

From there you can also revoke the permissions if you think they shouldn’t need the access anymore. In general, it is a good idea to go in there every now and then to evaluate who can access your code and are they still in the position where they need access. Over time the number of permissions can grow while maybe you don’t use many of the services anymore. If so, time to clean up while you are at it!

Now that you provided access to your Gists you’ll notice the little person icon changed into your profile icon:

clip_image010

Clicking the little profile icon will allow you to see the attached GitHub account and if you like, just to sign out of your account. Cancel will bring you back into Script Lab (I probably would have titled the button “Close” instead of “Cancel”, not it gives you the impression that Cancel will disconnect the GitHub account from Script Lab, but it doesn’t).

clip_image012

Now, your GitHub account is connected to Script Lab you can share your code snippets to Gists on GitHub. This is done through the “ Share” button. The share button has options to:

Publish a new Public Gist (for everyone to see), a new Private Gist (for your eyes only), Copy to Clipboard or to export the snippets:

clip_image014

Using the option “New public gist” will push the content you created in Script Lab to GitHub. Make sure that before you do this the title property of the Script Lab project is what you want to call it. This will be adopted by GitHub as you’ll see a bit further down in this blogpost. The confirmation looks like this and will provide you the URL of the Gist that you just created. With this URL you can import the Gist at a later time.

clip_image016

If you take the URL and open it in the browser you’ll see your code on GitHub:

clip_image018

It created a new Gist, nicely formatted on GitHub and the menu changed into “Update existing gist”. If you edit your code, push the “Update existing gist” option Script Lab will go out to GitHub again and save the changes.

clip_image020

This is how it looks like on GitHub. Going into the revisions tab you can see that the line where I changed the color was updated. The line with color red was removed and replaced by the line with the color blue in it.

clip_image022

How to restore your gist?

On GitHub if you navigate to your gist you can find on the top right the URL that comes with the gist. Obviously you can also just use the URL you just used to navigate, but GitHub will provide you several other options such an embedded url to put it on your website or clone the code. Here we copy the URL:

clip_image024

Next you go into the Script Lab menu (the ‘hamburger’ menu top left) to show you the Import option. Clicking the Import option provides you with a new dialog where you can enter the snippet URL or GitHub Gist ID:

clip_image026

Enter the URL and import the snippet. Now your Script Lab is filled with the code from the Gist, ready for you to continue your coding.

In follow-up blogposts, I will use this to test and experiment with some of the JavaScript for Office (aka OfficeJS) APIs. I really like this export option to gists. Maybe I will build a small collection of snippets for all the tested APIs for later reference.

Office Development – Installing Script Lab

Yesterday in my blog a short introduction to Script Lab, the Microsoft Garage project to work in some sort of a playground to develop your JavaScript for Office scripts so you can test-drive your code that you plan to use in your Add-in.

Today I will go over the installation process of Script Lab. Step by step I’ll follow the instructions and see what this looks like. How hard can it be ‘ey?

To start installing navigate to https://aka.ms/getscriptlab. It looks like this:

clip_image002

Click the Add button to arrive at the guided installation page:

clip_image004

To stay in the mood, we select Word again. I’ll will be using other clients like Excel or PowerPoint soon, but to be consistent I’ll select Word again. This will provide you with a comparable environment and maybe you get used to it. Now, to open in Word click the “Open in Word” option. This will ‘warn’ you that you are about to switch applications:

clip_image006

As this is the plan, you want to move into Word instead of staying in Microsoft Edge. Select ‘Yes’ to go on. This will launch Microsoft Word 2016 (assuming you have Office 2016 installed):

clip_image008

A document is opened, but not without warning. Because you open the document from the dark and dangerous Internet you are provided with a warning and start in the Protected View of Office:

clip_image010

In this case we tend to trust Microsoft in this we continue our journey by pressing “Enable Editing” but now we run into a second warning because the document also contained a Task pane that wants to run the Script Lab Add-in.

clip_image012

Again to make you feel safe, you don’t want any add-in to kick in without your confirmation, you get the option to “Trust this add-in” or “See Details”.

clip_image014

If you click “See Details” they bring you back to base. The installer page is provided where you can read information about the add-in. I guess you already did that, otherwise you wouldn’t get this far in the installation process (unless you just trusted my simple introduction and went ahead ). For now, not all that interesting, so we close this and leave it for what it is.

clip_image016

We go ahead, and decide to trust this add-in. This will bring us the Script Lab tab:

clip_image018

Showing you a balloon with the text “Code, Run and share your Add-in snippets directly from Office” and a “Got It” button to confirm:

clip_image020

Click the Script Lab and you’ll see a ribbon appear with the options:

Code, Run, Tutorial, Help, Reference Docs and Ask the Community

clip_image022

The most obvious thing to do would probably be to go through the Tutorial, at least that was what I picked as a starting point. The interesting thing is however that the Tutorial brings you to an Excel environment to explain you what you can do with the Add-in:

clip_image024

You basically go through all the same steps again, but ending up in Excel showing you all the same options. Open a script-lab-tutorial.xlsx from script-lab.azureedge.net :

clip_image026

This is an Excel starter document with more information about the Add-in and guiding you through the options:

clip_image028

Again the little Protected View warning and the Enable Editing button.

clip_image030

It didn’t provide me with the Script Lab Add-in tab though, only the instructions that you also saw when running the Word installer, except now for Excel.

clip_image032

This wasn’t really what I was looking for, probably useful if I just started from Excel but I didn’t. I went through the GitHub issues and noticed that getting a Word Tutorial is still in planning. Some patience here.

For now, at least the Word Script Lab Add-in is installed and ready to use.

To be continued

Office Development – Microsoft Garage Script Lab

clip_image002

Up to now we researched creating and deploying a simple Office Add-in in Word Online and Word on your local machine. We still need to see how this Add-in can be deployed to a so called production environment, maybe even with a dev and staging level.

We also didn’t do much development so far. We just generated a boiler-plate project using Yeoman but we need to dive in some more and look at some real code to learn how your JavaScript for Office solutions would work.

To do so Microsoft released an interesting tool as a Microsoft Garage project called Script Lab. With this tool you can code, write your test scripts and interactively test the outcome of your work. Based on the Monaco editor, yes … the one that also powers VS Code, you get a lightweight editor with in-editor-help like IntelliSense inside your Office client application. Your code snippets can use a wide variety of options such as JavaScript, TypeScript, HTML, CSS and more.

The code can run from another pane giving you options to interact with the UI, address the JavaScript for Office API and providing monitoring options such as output to a console

When you are done coding, tested it and added all the comments you now can share your snippets to GitHub right from the tool ready to share to your peer developers. With the Import function, you can do the same with code you got from shared snippets that you received from others.

Microsoft Garage Script Lab lived for a long time internally starting off a simple personal project under a different name but eventually matured by a hackathon and many other improvements to the tool you see today. The list of supported environments is huge:

The add-in works in:

Excel 2013 Service Pack 1 or later, Excel 2016 for Mac, Excel 2016 or later, Excel Online, PowerPoint 2013 Service Pack 1 or later, PowerPoint 2016 for Mac, PowerPoint 2016 or later, PowerPoint Online, Project 2013 Service Pack 1 or later, Project 2016 or later, Word 2013 Service Pack 1 or later, Word 2016 for Mac, Word 2016 or later, Word Online.

Remember that (we’ve discussed this a couple of blogposts earlier) each of the Office versions support their own subset of the APIs. When using Office 2013 your options obviously are much more limited than when using Office 2016.

How to get the tool:

You can get the tool, or look at the code by browsing to GitHub:
https://github.com/OfficeDev/script-lab

clip_image004

Install the tool:
https://aka.ms/getscriptlab

clip_image006

Demo video:

[youtube https://www.youtube.com/watch?v=yt6os8zPUKc]

In follow-up blog posts, I’ll show how to install the Add-in and hopefully try to use and build some sample code to experiment with the JavaScript APIs for Office.

To be continued …

Yes! 100 SDN Cast Subscribers

SDNCast 100 Subs

After fifteen months of hard work, creating a weekly live webcast called SDN Cast Marcel Meijer (@marcelmeijer), Fanie Reynders (@faniereynders) and I (@aafvstam) we reached the milestone of 100 subscribers of our YouTube channel. That may sound as a low number and sure, compared to some popular YouTube celebs this is, but our webcast is a bit of a niche product.

First, our webcast in general is Dutch except if we have guests in the show not speaking Dutch. In that case we obviously switch to English. Most webcasts are however in Dutch.

Second, the subject of Software Development is not the most popular subject on the interwebs for ‘normal’ human beings outside our little group of developers. And because we target the even smaller group of -Dutch- developers the number of potential subscribers is even lower.

Third, the number of Developers watching YouTube webcasts (especially live) is even lower.

We discuss news and events of the week and try to push in some demos or guests. Sometimes we do specials on location, we always try to be live on Thursdays 8 PM UTC+1.

So why are we doing this?

Well, first of all … it is fun to do!

Second, it keeps you focused. We are forced to monitor what is going on in the market and keep ourselves up to date. Everyone knows the feeling that you have to catch a deadline to do something, and just because the deadline is there you are forced to get your behind out of your lazy chair and get something done (in this case, we need to get into the chair to do some real computer stuff).

Third, we try to get in touch with authors, presenters or other potential guests to show us what they have an can do to writer articles, do presentations at our events or simply share thoughts in our webcasts.

Anyway, I’d like to thank all 100 subscribers to our YouTube Channel for your trust and let’s work on the next 100 subscribers! If you want to share your comments please do so, let us know what we can do better or if you want to join us in our show as a guest: Ping us, leave a Tweet or Google us, I’m sure you can find us.

Subscribe

If you haven’t done so already: http://www.sdncast.nl/subscribe !

SDN Cast 62 – Release flavors

clip_image002

In our Dutch SDN Cast 62 we discuss several releases of frameworks and tools. But things tend to get confusing these days. We see RTM, Release to Manufacturer or is it Release to Market. Candidates for Release with RCs – Release Candidates, Early Access, (General) Availability, Beta or Final. And then there are the Insider Programs with their release flight rings. The Xbox release flights are called Preview Alpha, Preview Beta, Preview Delta and Preview Omega …

Does it get weirder than this? We’ll see … at least there is something released.

Where can you find our 62th episode of our Dutch SDN Cast?
https://youtu.be/dcnzI2BxmTE

Did you subscribe our Dutch SDN Cast channel already?

Subscribe your YouTube channel if you don’t want to miss a single broadcast. Usually we will broadcast on Thursday evenings at 8 PM but there can be a change of plans where we need to move to another time or day. So to be sure Subscribe to our channel on YouTube or go to http://www.sdncast.nl to see when the next episode is due.

Other news:

Rider 2017.1 – JetBrains .NET IDE hits RTM
https://blog.jetbrains.com/dotnet/2017/08/03/rider-2017-1-jetbrains-net-ide-hits-rtm/

SQL Server 2017 Release Candidate 2 (RC2) is now available
https://blogs.technet.microsoft.com/dataplatforminsider/2017/08/02/sql-server-2017-release-candidate-2-rc2-is-now-available/

Welcome to the .NET Framework 4.7.1 Early Access!
https://blogs.msdn.microsoft.com/dotnet/2017/08/07/welcome-to-the-net-framework-4-7-1-early-access

Small Basic 1.3 available now!
https://blogs.msdn.microsoft.com/smallbasic/2017/08/07/small-basic-1-3-available-now
http://smallbasic.com/about.aspx

Creating Materials and Lights in the Visual Layer
https://blogs.windows.com/buildingapps/2017/08/04/creating-materials-lights-visual-layer

Xcode 9 beta 5
https://developer.apple.com/news/?id=07102017a

.NET Standard 2.0 is final
https://github.com/dotnet/announcements/issues/24
https://github.com/dotnet/standard/blob/master/docs/versions/netstandard2.0.md

Xbox Insider Program
https://news.xbox.com/2017/08/09/fans-can-join-xbox-insider-program

Nuget Fall 2017 Roadmap
https://blog.nuget.org/20170809/NuGet-Fall-2017-Roadmap.html

Web Applications with ASP.NET Core Architecture and Patterns guidance
https://blogs.msdn.microsoft.com/dotnet/2017/08/09/web-apps-aspnetcore-architecture-guidance/

Events

Upcoming events

Agile 2017 – August 7-11 2017, Orlando FL
https://www.agilealliance.org/agile2017/

MvvmCross .NET Summer Hackfest, August 21-September 2, Amsterdam Closing Event
https://www.mvvmcross.com/hackfest

Google Developer Days Europe – September 5-6, Krakow, Poland
https://developers.google.com/events/gdd-europe/

Wazug – September 7 2017, Hilversum

Microsoft Edge Web Summit 2017 – September 13, Online
https://summit.microsoftedge.com/

MixUG – Development Event – 13 September, Gouda
https://www.eventbrite.nl/e/tickets-mixug-development-evenement-34890959800

Xamarin Dev Days – 16 September – Amsterdam
https://ti.to/xamarin/dev-days-amsterdam-2017

.NET Conf – 19-21 September
http://www.dotnetconf.net/

Microsoft Envision – September 25-27 – Orlando
https://www.microsoft.com/en-us/envision/default.aspx

Ignite 2017 – September 25-29 – Orlando
https://ignite.microsoft.com

Hybrid IT Event – September 26 – Maarssen, NL
http://www.fujitsu.com/nl/microsites/hybrid-it/event/index.html

Xamarin Event – September 28, Nieuwegein
http://events.4dotnet.nl/xamarin-event/

MixUG – Eindgebruikers Evenement
https://www.eventbrite.nl/e/tickets-mixug-eindgebruikers-evenement-34890983872

SDN Event 3 – 6 October 6, Zeist, NL
https://www.sdn.nl/EVENTS/6-oktober-2017

TechDays October 12-13, 2017 RAI Amsterdam
http://www.techdays.nl/
https://techdays.msnlevents.net/content/eventselection.aspx?eventid=26152

SharePoint Saturday Belgium 2017, October 21, Brussels BE
http://www.spsevents.org/city/brussels/brussels2017

SharePoint Unite – October 24-26, 2017, Haarlem
https://sharepointunite.com/

Web Summit – 6-9 November 2017, Lissabon, Portugal
https://websummit.com/

Visual Studio Live! November 12-17 2017 Orlando, FL
https://live360events.com/events/orlando-2017/vslive.aspx

As usual we are always looking for presenters for our own events and Meetup’s so if you want to share something about hot technologies or just about something you implemented at work or in an App that could be interesting to our audience let us know so we can schedule you for one or our next SDN events or Dutch .NET Group Meetups.

This off course also goes for if you want to write a great article for us to publish in our SDN Magazines or at our SDN Website. The downside of publishing a magazine article is that there can be some time between writing the article and publishing the magazine. So, if it is time critical sometimes the best option is to publish it on the www.sdn.nl website to get more speedy attention to the article.

As you see, options enough to address your audience with top notch information. You can even, if you like, be our guest in our SDN Cast shows to discuss the projects you are working on or other topics you master. We will instruct you how to connect with us and what it is you need to join the show.

Hopefully we will see you at our weekly web cast, for the schedule go to www.sdncast.nl for next week’s announcement to find out the day and time of our next broadcast or go to www.sdncast.nl/youtube to watch old episodes and videos that we recorded at our events. Don’t forget to subscribe our YouTube channel www.sdncast.nl/subscribe or go directly to YouTube not to miss any of our shows!