We Keep Coding

Hololens 2 - Deployed scene understanding sample app from Microsofts, no virtual representation of the real environment is seen

I read through the scene understanding SDK overview by Microsoft and was trying to deploy its sample app. I followed through the instructions here, and everything got built and deployed successfully to my Hololens2. However, when I was trying out the application on my Hololens2, there is 1 major problem: The menu doesn't render smoothly, it seems to be continuously covered by black blocks. Neither does the virtual representation renders smoothly, everything seems to lag. It should be looking something like this from Microsoft's documentation.
I have seen this post but not sure if the problem is similar. May I ask if anyone has successfully used the scene understanding sample app and has any idea what caused the issue?

I believe you have followed these steps to create app package and deploy on your Hololens 2: Running on HoloLens 2.
To solve your issue that unsmooth scene objects rendering experience, you can create a ARM64 Release package instead of Debug one. Then you will find the issue will disappear and rendering will be smooth. The main reason is the debug mode build will have additional performance consumption. See the seventh point in this doc.
Verified on HoloLens 2 with the latest 21H1 OS (10.0.20346.1002)

UWP Xbox One difference between running in Retail to Dev Mode

I am having severe problems getting an app working in Retail Mode on the Xbox One.
The app works fine in Dev Mode, I have uploaded to the store and it passes certification fine but when the app is then installed via the store onto a Retail Xbox One it refuses to run.
Firstly it was crashing whilst on the splash screen, no error message just returning back to the Xbox homes screen, Due to now being in Retail mode I cannot connect a debugger to the app. I've setup my own exception handler to send errors to my backend server and it was crashing with the exception:
Cannot create instance of type 'Microsoft.Advertising.WinRT.UI.AdControl'
It's using the latest Microsoft.Services.Store.SDK and therefore Microsoft.Advertising SDK for XAML.  I've took out the AdControl from MainPage.xaml and now we have a UI come up on screen! Not ideal as the ads are needed for monetization.  
Unfortunately that's not the end of the problems, during the app initialisation it copies files from the Data folder of the solution to localstorage, for some reason it's now hanging on the following:
StorageFile anjFile = await localCacheFolder.GetFileAsync(App.AbilitiesFileName);
What's so different running apps on the Xbox in Retail Mode compared to Dev Mode? The app also functions fine on mobile and desktop so I know there shouldn't be any problems. The only way to try and find out what's causing problems is to comment out lines, or put placeholders in the app to change a debug textbox on screen to see what part of code is running and rebuild and submit to the store again, wait for certification and then redownload from the store to the Xbox, a very slow and time consuming task and I'm now up to Submission 12 of an app I'm getting very frustrated with!
Update: Seems like the AdControl issue started around 9th Feb and is affecting several apps on Xbox One and is possibly due to a framework update to the libraries involved. Not sure why it isn't affecting Dev Mode as well.

Thanks a lot for reporting this issue out on the forum and helping us with investigations. The root cause of the issue has been identified and fix has been rolled out. The framework update will take a couple of days to reach most devices as and when any new app or updated ad-enabled app gets updated on the Xbox device.
Dev Mode only: The issue doesn't affect Dev mode and only Retail mode since Retail mode actually is the most secure and most strict environment and requires that all binaries involved are signed and certified. If anything is missing, Retail mode is the only one which will surface the issue in this fashion - not loading the libraries.
Fix and roll out process: You could reach out to the users who reported problems for your app and ask them to re-install your app. The other option that you (as a developer) have is to push an update to your app (only version change) and push it to your users. This will get the framework updated on the end user devices and speed up the fix roll out. Those developers who had taken off the ad control, please put it back and push the update for your apps.
Please feel free to reach out to us (msft-aia-help#microsoft.com) in case of any issues or queries regarding this topic. Thanks for the patience and sorry for the inconvenience caused during this period.
-Vivek.

Seems like the AdControl issue started around 9th Feb and is affecting several apps on Xbox One and is possibly due to a framework update to the libraries involved. Not sure why it isn't affecting Dev Mode as well.
I have got a update from our engineering team, this issue has been fixed. But you may need to uninstall and reinstall any of the affected apps in your XBOX, after that it should work fine.
Please let me the result after you reinstall all the affected apps in your XBOX.
Thank you.

How do I add to my c# Selenium Webdriver suites to incoporate native iPhone app testing, using Windows

I already have a Windows PC that I program all my C# Selenium Webdriver suites in. From there, running tests will open up the appropriate browser and I can either debug or run the tests as required. Could someone please let me know a suitable native iPhone app equivalent of this development and debugging environment? As far as I could tell, iOS driver can be used from a programming side but does not have an attached simulator that can be used - it's purely an API. I checked out Appium website, but it looks like it can only run on Mac (correct me if I'm wrong) and I'm not sure it is designed for 'black box testing' or whether I have to load the full iPhone app project into it first and build up the test suites from there. Difficult to tell just from the website. So, any help would be appreciated - particularly if you have worked with iOS driver or Appium before.

So here's the bad news:
You will need a machine with OSX to run the "iPhone Simulator". Here's the general consensus on running the emulator on a hackintosh
That's the bad part. Here's the good part:
From there, running tests will open up the appropriate browser and I can either debug or run the tests as required.
Appium's Inspector will help be your debug tool, while the iOS Simulator is your "browser"
As far as I could tell, iOS driver can be used from a programming side but does not have an attached simulator that can be used - it's purely an API.
You're 1/2 correct.
There is no attached simulator - it's purely a REST server.
This is why you can write your tests in any language.
They have various client libraries which make it easier to work with. Here's the one for C#
I'm not sure it is designed for 'black box testing'
One of Appium's philosophies is "You shouldn't have to modify your app to test it" so yes, you shouldn't need to know anything about the system's internals to test it.
or whether I have to load the full iPhone app project into it first and build up the test suites from there.
If you want to run it on the simulator (you do), you do need a developer version of the app (compiled full iPhone app project)
So either your CI system (Jenkins, etc) gives you the .ipa or .app file, or you can have a client developer make one for you, or you can check out the source code and build & run with XCode.
Here's the setup guide on how to run your app with Appium, which covers the above two points.
Difficult to tell just from the website.
It's a bit of a learning curve to start -- and the documentation is a bit scattered around. I would suggest reading this first, and then starting out with running the inspector on a sample iOS project (like this Paint app) and then the app you're actually trying to automate.

VTK and Remote Desktop

I'm using the Kitware VTK library to display 2D images. I've recently begun work using the vtkWindowToImageFilter to output images in various formats. Everything was looking great until I worked at home today and I began to realize that VTK rendering doesn't seem to work when you are running software on your work machine through Remote Desktop.
When I output an image while NOT running in Remote Desktop, the image that gets output only consists of the VTK window. But when I run this same process while using Remote Desktop, the output image comes out in the correct size, but does just a normal screenshot basically, and other UI elements outside of the VTK window are showing up.
Question:
What is it about Remote Desktop and VTK that causes the differences I'm seeing? Is there anything that can be done to support outputting images from VTK windows while using Remote Desktop?
Thanks in advance!

From the VTK mailing list, I received the following response:
Remote desktop swap the video card driver hence the issue you are seeing. But if you use VNC instead, you should be good.
Hope this helps someone make the decision I had to make: whether or not to go forward with development on this feature knowing that if used remotely, the results would be unusable. I decided to go ahead with development with the assumption that our users who are in the phase of their workflow where this feature will be used are normally going to be in the office sitting in front of their work machines.

Mobile or PDA on which I can have IDE (integrated development environment) like Visual Studio, Net-beans

I just like to code when i travel,but i can't carry my laptop while travelling so i thought of a mobile in which i can create apps in C#, .NET or Java but for that i need an IDE,Compiler,etc.
Basically I am looking for a phone / mobile / PDA (far more handy than a net-book or a laptop) in which i can code the way i can do it normally in Visual Studio installed in a machine.
So are there any such devices ?

Let's take a look at what you need to overcome to get this to work.
1) oomph
Smart phones are designed to give you the ability to stay in touch, and have a rich experience on the move, but within the confines of a device that can be put in your pocket. Storage isn't really an issue these days, but processing power on small devices are. Sure we can run calendar, 3D games (though nowhere near the complexity of what you'll see on a fully-fledged operating system), fart-applications and plug-ins for you-tube so we can watch idiots break their ballsacks on railings, but there's a reason you don't see a fully-fledged rich-desktop application, or Grand Theft Auto IV on these devices. Oomph. Now bring in the Visual Studio development environment (and database server, if that is what you're application is doing), with potentially 100s of source files in your language of choice. Assuming we put a severly cut-down version of your IDE on to your pda, I hope you brought some spare batteries or the power-cord because you're going to need it.
2) input
It's probably not difficult to change your predictive text input to cover all the keywords of your chosen language so that you don't end up typing pubic instead of public. Once we've solved that we then need to go through the agonizing process of the fact that computer code contains a lot of symbols and identifiers, meaning we'd have to switch our input mode every other word or two to facilitate it:
for(int i(0); i < _vector.length(); i++)
Takes a few seconds on a keyboard. Probably about one train journey on your PDA. To solve this, we must assume the PDA has the facility for an external keyboard to prevent suicide.
3) display
Ok, we've solved our oomph problems with a power-chord and/or 50 batteries and we've plugged in our external keyboard. We're ready to code!! We'll have to adjust the font-size on the display so that we can get more than 20 lines of code (vertically) or 10 (horizontally). I enjoy my comfort when I code, so I don't want to be squinting at a small screen as I type on my plug-in keyboard. I'd have to prop it up against some books or something (so I don't have to hold the PDA and the keyboard). Now I can't see what i am doing. So, I need a bigger display.
4) Target code
What platform are you targeting? Remember the PDA is designed to run software for the PDA in question. You won't be able to write fully-fledged win32 applications on Windows Mobile 7. There are differences in the API. What if it's a web app you're developing? We're going to have to add a web server to the phone too, unless that is deployed elsewhere and we can rely on an internet connection to upload the changed files to.
Have we solved the problem? Did we get more oomph? A keyboard? A bigger display? Yes we did.
It's a laptop.

It's impractical, as Moo-Juice mentioned. However, you could try using online compilers that work through web browsers, such as Compilr.com. Perhaps this could work well enough through a mobile device's web browser. This way you could write snippets of code and verify that it compiles. Otherwise, you'll be stuck getting a netbook or laptop.

Use a VNC client or Remote Desktop client or something.
Obviously your experience will not be very good on a phone/PDA, but I also don't have an IDE installed on my laptop -- I just use remote desktop (and a wireless modem if I'm desperately bored and can't find wifi).