Upgrading Magenic/MAQS from V4 to V5

If you get an error like this while upgrading Magenic/MAQS from V4 to V5:

Severity Code Description Project File Line Suppression State
Error Could not install package ‘Microsoft.Extensions.Configuration 2.1.1’. You are trying to install this package into a project that targets ‘.NETFramework,Version=v4.5’, but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Tried clearing the NuGet cache in VS 2017 but that didn’t help.

Solution

Troy Walsh suggested this solution…

Unfortunately, there is no clean upgrade path from V4 to V5.
The team has made several big changes, such as moving to .Net Standard 2.0, lazy initialization of the web driver, support for multiple web drivers in a single test, slitting of the config file sections and adding support for .Net Core to name just a few.

So there are 2 ways to upgrade

The hard way:

  1. Make sure you are using VS2017 or above
    https://marketplace.visualstudio.com/items?itemName=NuGetTeam.NuGetPackageManagerforVisualStudio2015#review-details
  2. Update your projects to 4.61 or above – https://docs.microsoft.com/en-us/dotnet/standard/net-standard

  3. Update your using statments
    using Magenic.MaqsFramework to using Magenic.Maqs
  4. Use the system under test configurations
    Config.GetValue(“WebSiteBase”) to SeleniumConfig.GetWebSiteBase()
  5. Remove any project references to Microsoft.VisualStudio.QualityTools.UnitTestFramework
  6. Use nuget to add the MSTest.TestAdapter package
  7. Update your app.config so it has a Selenium specific section
  8. Set the App.config to copy always

The easy way:

  1. Install the latest MAQS templates. – https://marketplace.visualstudio.com/items?itemName=vs-publisher-1465771.MAQSOpenFramework
  2. Create a new project

Copy your code into the new project
Note* You will need to update your using statements and any place you use the config settings

SOURCE: https://github.com/Magenic/MAQS/issues/5#issuecomment-407429302

Cortana on Band 2 can’t reach your Phone

One of my favorite features of the Microsoft Band 2 is the voice link to Cortana – without having to un-pocket my phone.  Unfortunately, when I tried that, I got the following message.

Cortana: Sorry, I couldn't reach your phone...

Fortunately, a brief chat with MS Band Support led me to this elaborate but effective solution.

  1. Unregister the Band from within the Microsoft Health app (under My Microsoft Band in the hamburger menu [≡]).
  2. Remove the Band from your Bluetooth settings screen (tap and hold to Delete)
  3. Uninstall the Microsoft Health app
  4. Restart your phone (on Lumia 950 XL, press and hold power button until the phone vibrates – then release the power button and phone will re-start)
  5. Reinstall the Microsoft Health app
  6. Reset the Band (swipe to the Settings tile [⚙], swipe right to Power [⏻], swipe right to Reset Device and confirm your selection)
  7. Go through the Band set-up process

After this, I was able to issue voice commands to Cortana through my Band 2 again.

Update: I used the voice command feature at about 6p after resolving the issue around 1p, but by 10p when I tried to use it, the feature had failed again, displaying this message.

Update #2 (2016-04-07): I put some feelers out on common support sites for Band 2 and the Lumia 950 XL. 

Cortana on Band 2 can’t reach your Phone (answers.microsoft.com)

Cortana on Band 2 can’t reach your Phone (forums.windowscentral.com)

How often are you able to successfully use Cortana via Band 2? (Straw.pl)

How often are you able to successfully use Cortana via Band 2? (Reddit)

All I was able to learn, after several weeks, is that it’s a very common problem (which is an understatement).  At this time, here’s what we seem to have learned:

Band 2 Cortana works fine with iOS, Android, and Windows Phone 8.1 devices.

Band 2 Cortana doesn’t work with Windows 10 Mobile devices.

I took my fully updated Lumia 950 XL and Band 2 to my local MS store after scheduling an Answer Desk appointment.  I was told that this has been a known issue since November and that there seems to be very little discussion on it since then… it seems to have stalled.

Also, since my initial post, Band 2 and Microsoft Health apps have been updated and installing these updates have not resolved the issue.

It’s troubling to me that such core functionality of flagship products has gone unrepaired for six months!

Make Sure Bluetooth is on and your phone is close by

Update #3 (2016-06-09): Even though there have been several updates to Windows 10 Mobile (I’m now on Fast Ring), the Health App, and the Band 2 firmware, the problem still persists.  Rod Trent over at WinSuperSite.com has written the following article about the situation though:
Constant Problems with Windows 10 and Lumia 950 Make for Irate Microsoft Band Owners