windows-10-universal

I download a Console Application on GitHub and works fine. But I want to translate this C# Console Application to a Universal Windows 10 Application. The error on Visual Studio : Web Request does not contain a definition for... This is the code: private AccessTokenInfo HttpPost(string accessUri, string requestDetails) { //Prepare OAuth request WebRequest webRequest = WebRequest.Create(accessUri); webRequest.ContentType = "application/x-www-form-urlencoded"; webRequest.Method = "POST"; byte[] bytes = Encoding.ASCII.GetBytes(requestDetails); webRequest.ContentLength = bytes.Length; using (Stream

I download a project on Gitgub Basically is a Console Application. But I want to translate this C# Console Application to a Universal Windows App. I want to use HttpUtility.UrlEncode in a windows 10 universal, but I can not find System.Web in .NET (Add Reference) How can I add this assembly to my project? Error: The "HttpUtility" Does not existin the current context. Im using Visual Studio 2015 I try with this question: How Add System.Web Reference To A Windows Form Application But doesnt work for the Universal 10 app. Thanks in advance! The System.Web assembly is a huge monolith that

I have created a simple application using Delphi 10.2 Tokyo (using FireMonkey) that displays images and allows you to set the desktop wallpaper for a selected image. The main code that sets the desktop wallpaper is: class procedure TUtilityWin.SetWallpaper(AFileName: String); begin SystemParametersInfo(SPI_SETDESKWALLPAPER, 0, pChar(AFileName), (SPIF_UPDATEINIFILE OR SPIF_SENDWININICHANGE)); end; While this works great when the application runs on the desktop (as a standalone install), it fails when run as an APPX (during the certification process) of submitting to the Windows 10 App Store.

I have a UWP app that compiles successfully if I have UseDotNetNativeToolchain off. But when I turn it on, it gives me the cryptic error: Internal compiler error: Object reference not set to an instance of an object. UWPApp C:\Program Files (x86)\MSBuild\Microsoft.NetNative\x86\ilc\IlcInternals.targets 887 Build This is all it gives me. What could be causing this? How can I drill down on this. Using VS2015 Here is the full build output in case that helps: https://gist.github.com/shannah/e24fe8456313fb9ad98577c9a812f357 The solution to this problem was to disable optimization in a few

Just updated to VS2015 Update 3 RC and now can't build UWP solution in Release configuration because of the following error: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\AppxPackage\Microsoft.AppXPackage.Targets(2194,5): error MSB4044: The "GenerateAppxPackageRecipe" task was not given a value for the required parameter "AppxManifestXml" . It was fine a few minutes ago with VS2015 Update 2 and no any code changes since then. Anyone experience something like this after update (or with fresh VS2015 Update 3 RC installation)? OK, repairing VS2015 Update 3 RC fixed the build issue.

Full error log: C:\Users\user\Development\Tutorials\cordova-tutorial\hello\platforms\windows\CordovaApp.Windows.jsproj(70,3): error MSB4019: The imported project "C:\Program Files(x86)\MSBuild\Microsoft\VisualStudio\v14.0\Microsoft.VisualStudio..Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe: Command failed with exit code 1 While doing Create your first app tutorial from official Cordova website, when building the helloworld app, I got the error I've posted

Understanding why it's not recommended to detect the device type to perform run-time functionality, best practices dictate detecting which APIs are present instead. This way, users running their tablet in desktop mode, for instance, will not experience undesired behavior. Also, since hardware is so dynamic, checking for user interactions like touch capability is not a good approach either. On our project, we have decided to identify the APIs we'll need for three different screen widths - small, medium, and large. Microsoft has listed these APIs here . But this list is rather long and checking

I would like to have a more descriptive name (for discoverability) in the Microsoft app store, but use a shorter name for the app when it is installed. I have reserved both names. I am thinking I set the App Manifest to have the short name in the Application -> Display name, and the more descriptive, store name in Packaging -> Package display name, but I don't understand the way these two names are used so I'm just guessing. Before I try this with an actual submission, I'm wondering if someone already knows if this will work. Yes, you're right. "Application -> Display name" used as a name of