The project can be compiled and deployed to the Emulator and Device.
Everything works fine as long as the build configuration is set at AnyCPU or x86.
And is set to Debug.
But when build configuration is set to Release, project doesn't build.
If project is set to AnyCPU and ARM, the same problem exists.
Error 1
Files has invalid value "<?xml version="1.0"?>". Illegal characters in path.
The error doesn't point to a file.
External Libraries referenced by in this project-
- JeffWilcox.PhoneThemeManager
- Buddy
- AdDuplex
The Windows Phone 8 emulator can run only applications built as AnyCPU or x86, because it is actually running on your PC as on Hyper-V as a virtual machine.
On the other hand all Windows Phone 8 devices are ARM only, so to run your app on device, it needs to be AnyCPU or ARM.
I hope this clears some confusion in the deployment limitations.
Related
Project Type: .Net 5 MVC
I want to create an application with Electron JS so that it can work offline in case of network failure and communicate with an external peripheral connected to USB.
For this I have to communicate with a generic device driver. At this moment I can already communicate through visual studio (iis).
The problem is that for the drivers to work the main program has to be set to Platform Target x86 and I can't get Electron JS to start.
If I change the Platform Target to AnyCPU (x64) I get Electron JS to start but the drivers don't work.
Could there be some configuration in the part of starting Electron that could allow to overcome this behavior?
Electron.NET - Error PlatformTarget x86
Surface Pro X uses ARM processor.
So far, I have been publishing UWP app using x64 architecture only.
I have created ARM64 and managed to build release version successfully.
However, when I choose Publish -> Create app package, I don't see the option to select Release/ARM64 in the drop down menu.
Also, when I select x64 and ARM64, an error message says "Selecting mixed solution configuration is not allowed when generating app bundles".
Any assistance greatly appreciated.
Thanks.
Make sure you have selected Release mode before generating App Bundle. If you have different configuration(Debug x64 & Release ARM etc.,), it will show this error "Selecting mixed solution configuration is not allowed when generating app bundles". Ensure it is release configuration in all your selections(Release x64 & Release ARM).
I finally solved this by changing the the .sln and .csproj files to use arm & arm64 instead of ARM & ARM64. Windows 10 development machine is, somehow, case-sensitive.
I have a .Net project built in VS2010 compiling against .Net 4 that uses an older 32 bit dll. The project will be deployed to a Windows 2008 64 bit server where the dll used is registered in SYSWOW64 and is being used by other legacy programs. I had an issue with it that was solved by changing the platform target to X86 on the build tab in the project properties. Initially, I compiled the project and the dll in question is copied to the bin folder. To test, I copied the release folder to the server desktop and the program runs fine. However, if I set the copy local to false the dll is not included in bin - as expected, but the program no longer runs on the server. The development environment is XP service pack 3.
Why can't the program find and use the registered copy of the dll in SYSWOW64?
Having a reference to the Microsoft.Media.SmoothStreaming.dll in a Metro Style App project, then attempting to run tests from a separate Unit Test project that references the Metro Style App assembly does not work in Visual Studio 11 (Ultimate Beta Version 11.0.50323.1 QRELB), even with the processor types both set to either x86 or x64 in the Debug compilation configuration.
The platform target of the Metro Style App must be set to either x86 or x64 (Any CPU won't work with the SmoothStreaming SDK assembly). The Unit Test project target must match the setting of the Metro Style App when it contains a reference to the Metro Style App assembly, otherwise you get the following error:
"Error 1 There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "%APPROOT%\bin\x86\Debug\UVerseApp.exe", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project"
When both are set to x64, the solution compiles and runs fine but the Unit Test Explorer will not discover any of the tests from the unit test project, so you can't run them or even see them.
When both are set to x86, the solution builds fine and the Unit Test Explorer properly displays all tests. However, if you attempt to run any of the tests, you encounter an application error in vstest.executionengine.appcontainer.x86.exe every time. The Metro app will still run fine - this only happens when you attempt to run or debug tests methods using Unit Test Explorer.
Is this a known issue and/or are there any possible workarounds?
I have created a small WIN32 Console Application in Visual C++ in Windows 7.
When I try to run this application on Windows Xp it gives me an error saying
This application has failed to start
because MSVCR100D.dll was not found.
Re-installing the application may fix
this problem.
So how do I statically build this application so that it contains MSVCR100D.dll ? or
do I have to copy MSVCR100D.dll form Windows 7 and paste it some where in Windows Xp ?
Thanks.
MSVCR100D.dll isn't a Win7 DLL, it's an MSVC2010 DLL. You can use static linking by changing RuntimeLibrary from MD(d) to MT(d) in the project properties (under C/C++ -> Code Generation).