During the COVID-19 pandemic, I was one of the lucky ones who was able to keep my job and work from home. At least, so far... It's one of the benefits of working in computer programming: you can often work from anywhere, so long as you have a functioning VPN. One of my tasks over the quarantine period was to try to configure an application to support automatic updates. These applications are UWP apps built for a Windows IoT installation on a Raspberry Pi (RPi). It's an internal application that is still in a Beta stage, so it's not suitable to release over the Microsoft Store (at least, not yet). We had been manually updating the handful of devices in the field for the past two years, and as the number of deployed devices has grown, having to send someone out to manually update them was becoming a pain. Even moreso in this new era of social distancing.
Many Windows apps can be built in Visual Studio to support automatic updates.
Windows IoT has not been the best of environments to work in. It lacks a lot of functionality built-in to other Windows environments, and documentation for it is spotty, at best. Back in 2018 (shortly after we had started deploying the apps in the field), Microsoft released an update for Windows and Visual Studio that allows UWP apps to be built such that they automatically periodically check a specified server location for new updates. Awesome! It sounded like there would be a simple solution!
Be sure to update the version number.
I built the app with auto-updates enabled for every hour, deployed it to my test RPi over the Windows Device Manager, and deployed the update package and .appinstaller file onto our test server.
Then I waited.
Select an appropriate frequency to check for updates. I set it to check every hour while testing.
And nothing happened.
... [More]
987de5bf-7e9f-4a18-848c-701585ac3fb6|1|5.0
Tags:Windows, Internet of Things, Raspberry Pi, Universal Windows Platform, MS App Installer, .appinstaller, Visual Studio, programming, C#, COVID-19, social distancing, work-from-home
Blair Witch, as an intellectual property, is in a frustrating place similar to the Alien franchise. Both were innovative horror films that set numerous standards and conventions within their sub-genres, and which have been copied and ripped-off numerous times. Sci-fi games from Starcraft, to Metroid, to System Shock, to Dead Space have all taken heavy inspiration from Alien and Aliens. So much of the iconography of Alien and Aliens have been borrowed by these games, that when someone comes along with a game based on the Alien intellectual property, it's hard for that game to not feel like it's derivative of one (or all) of the myriad Alien impersonators.
the Blair Witch Project has similarly left a mark on the horror landscape. It single-handedly popularized the "found-footage" genre against the backdrop of a creepy, supernatural forest. Games such as Outlast, Alan Wake, and even Resident Evil VII all have a little bit of Blair Witch in their DNA. So when a game comes out that actually bears the "Blair Witch" name, it's kind of hard for it to stand out in the larger horror landscape.
Plenty of games (such as Outlast [LEFT]) have used tropes inspired by The Blair Witch Project.
This is the case with Lionsgate and Bloober Team's new Blair Witch game, exclusive to Microsoft platforms. Nothing that Blair Witch does feels particularly new or creative, even though most of the game's ideas are competently executed. Using a camcorder as a tool for navigation, exposition-delivery, and puzzle-solving feels pulled straight from Outlast or Resident Evil VII. Wandering through the woods and defeating monsters by pointing a flashlight at them gives me flashbacks to Alan Wake. Navigating the forest and occasionally picking up other people's trash also reminded me of Firewatch. Eventually, the whole game descends (rather predictably) into P.T. territory -- but, you know, without all the nuance or careful pacing that made P.T. so unnerving.
Who's a good doggy?
Blair Witch's most innovative feature is probably the dog companion (named Bullet), but even that feels pulled straight from Fallout 4. I probably would have been a bit more impressed if not for the fact that Bullet seemed to lose relevance as anything other than a monster compass, for a large chunk of the middle of the game. Without having healing items or ammunition or any other consumable supplies, the ability to send the dog out to find things feels like a sorely under-utilized mechanic.
Bullet is very well-introduced, and is integral to the early levels of the game. He finds clues for you, fetches key items, guides you to the next objective, and warns you of potential danger, all completely organically and without breaking immersion. But after a couple of hours, he just runs out of things to find and things to do. The puzzle shift away from using the dog, and more towards using the camera to do everything from manipulate the environment, to navigate mazes and looping paths, and even spotting monsters.
Your emotional support dog, Bullet, serves an integral role throughout the game.
... [More]
7a3b2c59-d35b-424f-a1cd-ecf04d6332bb|1|5.0
Tags:Blair Witch, Bloober Team, Lionsgate Games, The Blair Witch Project, Microsoft, XBox, windows, XBox Live, Steam, Good ol' Games, indie gaming, horror, found-footage, camera, forest, post-traumatic stress disorder, dog
It's tax season, which is not something that I ever write about on this blog. But this year, I had a very irregular experience. It wasn't with my taxes; rather, it was with my dad's attempts to use this year's TurboTax software. He'd been using TurboTax for years with no problem, but this year, the program wouldn't install. He's not exactly tech-savvy, so he had to call me to help him troubleshoot.
TurboTax fails to install due to some unspecified issue with the .NET Framework.
Upon attempting to install the program, he gets a very un-descriptive error message that simply states there was a problem installing TurboTax. Then a dialogue pops up stating that TurboTax is attempting to fix the problem by checking the file system, registry, and .Net framework. It's the .Net Framework step where TurboTax fails with yet another very un-specific error.
We tried updating Windows, disabling anti-virus software, and even opened up the registry to make sure that all the requisite versions of .Net Framework were installed. No luck.
Unable to resolve the problem itself, TurboTax referred us to a troubleshooting web page.
TurboTax referred us to this troubleshooting page, which includes instructions for downloading and running various .Net Framework repair tools and other system file integrity tools. In my dad's case, none of this stuff worked. As a last resort, the troubleshooting guide referred me to a blog post by Microsoft developer Aaron Stebner, who wrote about a .Net Framework cleanup tool that could potentially be used to resolve the issue... [More]
90a849db-87db-4a02-a5e5-9c7105a6911c|3|5.0
Tags:Intuit, TurboTax, Microsoft, Windows, Windows 7, Windows 10, .Net Framework, PC, taxes, troubleshooting, customer support, Aaron Stebner
|
12 | | | | | | | 60 | 11 | | | | | | | 55 | 10 | | | | | | | 50 | 09 | | | | | | | 45 | 08 | | | | | | | 40 | 07 | | | | | | | 35 | 06 | | | | | | | 30 | 05 | | | | | | | 25 | 04 | | | | | | | 20 | 03 | | | | | | | 15 | 02 | | | | | | | 10 | 01 | | | | | | | 05 |
|