windows-10

For UWP, it is easy to get all files in the app local folder as: IReadOnlyList<StorageFile> files = await ApplicationData.Current.LocalFolder.GetFilesAsync(); You can now iterate on the files list and even get further info on individual files. I would like a similar all-file-getter for an app folder, for instance, consider the /Assets folder where app *.png files are stored. Single file with a known name is no problem; I can refer to it quite easily as: StorageFile.GetFileFromApplicationUriAsync(new Uri(@"ms-appx:///Assets/StoreLogo.png")) My question is, therefore, is there a similar thing

Since time immemorial, most web browsers have been able to open a local file if you ran the web-browser executable, for example just execute iexplore.exe file:/c:/temp/file or via the IShellDocView interfaces. I am trying to do this from within my own program, in Windows 10, with Microsoft Edge, and am unaware of how to do it. The executable appears to be completely undocumented, does not respond to /? or /help, and simply crashes no matter what I pass to it, and given that the path appears to be likely to change, is probably not the correct approach to invoke this executable directly: C:

I am setting up my previously working vagrant environment in Windows 10. I've updated to the newest version of both VirtualBox ( https://www.virtualbox.org/ticket/14040 ) and Vagrant. When I vagrant up I get an error: Cannot rename this connection. A connection with the name you specified already exists. Specify a different name. I've since tried deleting all of my boxes, deleting the .vagrant and .virtualbox directories, reinstalling both virtualbox and vagrant. Yet, I always get the same error. Here is the error message from my console: The guest machine entered an invalid state while

I'm trying to install WinDbg from this page , just under the Debugging Tools for Windows 10 (WinDbg) section. However, when I download the executable and run it, it tells me that You must uninstall the Windows Software Development Kit - Windows 10.0.10586.15 before you can install the latest version of the kit. I'm guessing this probably has to do with the fact that I already have VS 2015 (and the Windows 10 SDK) installed. However, when I go to the Developer Command Prompt and type in > where windbg it tells me that it can't find WinDbg. How, then, do I install it without doing anything

I tried to use MVVMLight in our Windows 10 Universal app, but it seems like that it totally can't work. I've seen this blog Nuget downloaded and added a reference to the MVVM Light assemblies Nuget also added the ViewModelLocator in the Application.Resources. Can't see the Locator in Application.Resources You need to create the ViewModelLocator manually, please follow these steps: Create a new Windows 10 Universal app, for example: MVVMLightUWPApp1 Add reference to MVVMLight using NuGet Package Manager Add a folder for your UWP app, for example: ViewModel Under the ViewModel folder, add two

A bit of context: Sciter (pure win32 application) is already capable to render UWP alike UIs: in dark mode: in light mode: Windows 10.1803 introduces Dark/Light switch in Settings applet as seen here for example . Question: how do I determine current type of that "app mode" in Win32 application? VTT Well, it looks like this option is not exposed to regular Win32 applications directly, however it can be set / retrieved through the AppsUseLightTheme key at the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize registry path. EDIT: Calling out that this works in all

I followed the instructions in Laravel docs to install Vagrant and Homestead on Windows 10, but now I've decided to move the whole development stuff to another dedicated server running Debian. I need to fully remove Vagrant, Homestead, Composer as well as AMPPS (old stuff) from the Windows 10 desktop. It should be easy to simply uninstall Vagrant and AMPPS, but how do I go about cleaning up the remaining things? I don't need to keep any of the code etc. I've already got that in a different location. Virtual Machine Remove the homestead VM by running vagrant box remove laravel/homestead

Machine: Window10 (64bit). I downloaded the latest VirtualBox, Vagrant and initialized CentOS 6.7 64bit image/url. The following worked successfully in Git-Bash session. 1. vagrant box add "centos67x64" " https://github.com/CommanderK5/packer-centos-template/releases/download/0.6.7/vagrant-centos-6.7.box " 2. vagrant init 3. Updated Vagrantfile (and turned vb.gui option i.e. uncommented that config section in the file). config.vm.provider "virtualbox" do |vb| # Display the VirtualBox GUI when booting the machine vb.gui = true # Customize the amount of memory on the VM: vb.memory = "2048" end