I have install Windows 8.1 and after that I install Visual Studio Express 2013, which includes Update 2 RC.So when I run any application then it gives me the error
"File 'Windows.props' not found"
I don't know why it is happening. I search a lot about this error but can't find any solution.Please help me I have spend two days to find this solution.
Edit
Also there is not Emulator in the Device list.I think error is due to this once.I have download the 8.1 Emulator but cant find in the VS 2013 Emulator list.
Some basic checks you need to perform to get anywhere close to a resolution.
The Windows.props file is a build file that's used by MSBuild.exe when it builds a Windows Phone app. The normal install path is C:\Program Files (x86)\Windows Phone Kits\8.1\References\CommonConfiguration\Neutral\Windows.props. Use Windows Explorer to check if the file is present.
Then there is a line in the main .targets file that includes it. It tries to locate the file in the $(TargetPlatformWinMDLocation) directory. You can see the value of this macro by increasing the build verbosity. Tools + Options, Projects and Solutions, Build and Run. Change the "MSBuild project build output verbosity" setting to Detailed. Use Build + Rebuild on your project. Scroll back the Output window and locate the lines that resemble this:
1>TargetPlatformSdkMetadataLocation = C:\Program Files (x86)\Windows Phone Kits\8.1\References\CommonConfiguration\Neutral
1>TargetPlatformSdkPath = C:\Program Files (x86)\Windows Phone Kits\8.1\
1>TargetPlatformSdkRootOverride =
1>TargetPlatformVersion = 8.1
1>TargetPlatformWinMDLocation = C:\Program Files (x86)\Windows Phone Kits\8.1\References\CommonConfiguration\Neutral
Tell us if you see anything different.
This path is read from the registry. Startup Regedit.exe and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\WindowsPhone\v8.1\Install Path as well as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\WindowsPhoneApp\v8.1\Install Path.
Verify that you see a value listed in those keys with the name "Install Path" and that it contains the value "C:\Program Files (x86)\Microsoft SDKs\WindowsPhoneApp\v8.1\".
Extracts from msdn discussion:
check for the existence of a SYSTEM level environment variable called windowsSDKDir and try removing it.
For this Follow these steps:
Press Windows Key + X and select System.
In the System dialog click on "Advanced system settings" then click "Environment Variables" on the advanced tab.
Then look for the environment variable I mentioned
try removing it
If this not works for you ,you must re-install, Windows Software Development Kit (SDK) for Windows 8.1 this must solve your problem.
The issue seems to be bound to the VS2013 Update4. I had no issues before, but after this, I needed to Install the Windows Software Development Kit for Windows 8.1 as Ludwo suggested.
I used function 'Repair' in control panel -> programs and functions -> Windows Software Development Kit for Windows 8.1 ->Change and solved this problem.
In my case I had to install Windows Software Development Kit (SDK) for Windows 8.1 (Not Windows Phone SDK!) to fix it. I have VS2013 update 4
have you checked for the existence of a SYSTEM level environment variable called windowsSDKDir? and try removing it?(make a note of its value first in case you need to re-instate it at some point). For some this appears to have been causing the error. It is not clear at this stage what creates this.
Related
I want to create an upload package for the Windows Store.
The app is essentially "Hello world" for a dev express XAF Win application. I am using the Desktop Bridge.
I am following the docs to create the upload package
This created a file
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage
And an error
APPX3217 SDK folder containing 'UAP.props' for 'UAP 10.0.17763.0'
cannot be located. See http://go.microsoft.com/fwlink/?LinkID=798187 for more information
When I double click the error it goes to the following code in the Targets file
<GetSdkPropertyValue Condition="'$(AppxPackagePipelineVersion)' == '$(UapBuildPipeline)'"
TargetPlatformSdkRootOverride="$(TargetPlatformSdkRootOverride)"
SDKIdentifier="$(SDKIdentifier)"
SDKVersion="$(SDKVersion)"
TargetPlatformIdentifier="$(TargetPlatformIdentifier)"
TargetPlatformMinVersion="$(TargetPlatformMinVersion)"
TargetPlatformVersion="$(TargetPlatformVersion)"
PropertyName="WindowsSdkDir"
VsTelemetrySession="$(VsTelemetrySession)">
I am targeting WIndows 10, version 1809(10.0; Build 17763) and also have this as the min version.
The application is using .Net Framework 4.7.2
As per the Microsoft link I had to install the update for Windows 10 SDK, version 1809.
My Logs :
Error APPX3217: SDK folder containing 'UAP.props' for 'UAP
10.0.18362.0' cannot be located.
This works for me.
Go to https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/
Install SDK: Windows 10 SDK, version 1903 (10.0.18362.1)
Then, rebuild it succeeded.
I had the same issue with a CI/CD project that relied on the 1703 release. I used choco to fix it as a build-step.
choco install windows-sdk-10.1 --version=10.1.15063.468
I am getting this error while deploying or debugging windows phone 8.1 app.
Windows Phone Emulator is unable to create a differencing disk: A
virtual disk support provider for the specified file was not found.
That error means that *.vhd files must not be encrypted and must not be compressed.
Then you have to uncompress the folder that containt *.vhd files and try again.
Command line to launch emulator:
C:\Windows\system32>"C:\Program Files (x86)\Microsoft XDE\8.0\xde.exe" /vhd "C:\
Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Emulation\Images\flash.vhd
" /name WP8-SDK
According to the MS forums you might be able to get the emulator to run with the following command:
"C:\Program Files (x86)\Microsoft XDE\8.0\xde.exe" /vhd "C:\WP8\Images\Flash.vhd" /name WP8-SDK
That command might also give you more output as to why the emulator won't start.
I was able to resolve this by running up the Hyper V Manager and starting the VM manually.
I restarted the machine first, launched Hyper V Manager, then clicked Start on the VM (WVGA 4 inch 512MB). It started ok. I then closed it, and it then worked from VS2013.
It may be possible if you've enabled file compression on your disk..
Go to properties of the folder > General > Advanced
and uncheck the "Compress contents to save disk space" checkbox.
C:\ Program Files (x86)\Microsoft SDKs\Windows Phone\
I hope it will help you.
Thanks,
Suraj
http://codeblock.in
I'm trying to use the sqlite-winrt library at https://sqlwinrt.codeplex.com (cf. http://blogs.windows.com/windows_phone/b/wpdev/archive/2013/05/30/sqlite-winrt-wrapper-for-windows-phone.aspx) because I need to access an SQLite database via SQL commands in a WinRT 8.1 and a WP8 app and this library seems the only available option.
Anyway, there is no binary release and if I try compiling the source I get several link errors for unresolved externals against the SQLite DLL. I posted an issue at codeplex but got no reply yet, so I was wondering if anyone had already managed to successfully compile this lib and how (or if you know of any viable alternative for RT8.1 and WP8). Here is what I did:
downloaded the latest source from the site.
downloaded and installed 2 VSIX from http://www.sqlite.org/download.html: sqlite-winrt81-3080002.vsix for RT 8.1 and sqlite-wp80-winrt-3080100.vsix for WP.
executed the powershell scripts in each subfolder of the source code solution, which are required to update the projects with newer releases of the SQLite for WinRT extension. The current versions of the scripts refer to SQLite for WinRT 8.1 (prerelease) which is the same I downloaded above.
opened the VS2013 solution and removed the RT project (I just need RT8.1 and WP, this was for WinRT 8.0).
5) built the solution, which failed with link errors.
If I see the RT8.1 project properties, I can confirm the reference to SQLite is under C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1\ExtensionSDKs\SQLite.WinRT81\3.8.0.2.
Did anyone manage to use this lib? Thanks!
I also once had that problem. I fix it by editing the project file manually. At that time, the powershell script updating the wrong path. That's why I always failed when compiling my project. After I edit the project file using external text editor (I use sublime text), the projects are linked correctly.
You can try DatabasesCx. It is another SQLite Wrapper using Windows Runtime Component technology. It is freeware distributed as precompiled binary. You can find the details at http://www.almanacsoft.com/databasescx
I have a native dll that I'd like to use in a WP8 project that I'm working on. I've done some research and have created a C++ Windows Runtime Component (WRC) to wrap the native DLL. The WRC project uses a .lib file, and my WP8 application calls the WRC project.
My solution compiles all fine, but when my application makes a call to a method in the native DLL, I get a The specified module could not be found. (Exception from HRESULT: 0x8007007E) exception.
From reading around it seems like the dll is not being loaded. I've copied all relevant dlls to the output dir of where the .exe file is and also in various places but the error keeps showing up.
If anyone could point me in the right direction I'd be very grateful. Also if more info is required I'll post that up also.
The DLL must be included in your XAP package. Something you can see being taken care of in the Output window when you build your app, it starts with the "Begin Xap packaging" messages and then lists all the files that get added. The runtime error says it is not being included.
There is remarkably little guidance on how to ensure that a file gets included in a phone package when MSBuild cannot figure out the dependencies by itself. It certainly won't for your DLL, no way the build system can tell if it isn't a project in your solution. Seems you're operating a bit on the bleeding edge in this case :)
But this works well when I try it, going by the MSBuild output and not by actually testing it: Project + Add Existing Item. Navigate to your DLL and select it. Select it in the Solution Explorer window and look in the Properties window. Ensure that "Build Action" = Content, Copy to Output Directory = "Copy if newer". Rebuild, you'll now see the file getting added to the XAP. Which should solve this particular error. There might be others :)
Windows Desktop or Windows Store native DLLs are not binary compatible with Windows Phone, even if they are built for the same CPU architecture.
Therefore you will need to recompile your native DLL for the Windows Phone toolset.
About Windows Runtime Components:
On Windows Phone a Windows Runtime Component is itself a native DLL (.NET is not supported on the phone). The binaries of Windows Runtime Components cannot be shared between Windows Store apps and Windows Phone apps.
I'm creating installer using InstallShield 2010 (basic MSI) that is having two features.
First feature consists of:
main .NET application compiled as x86,
some native x86 third party dlls which are used by main application (x64 versions are unavailable).
Second feature contains single component which is an extension for MS Reporting Services compiled as AnyCPU.
During UI sequence I'm using InstallScript custom action to enumerate all available Reporting Services instances from both x86 and x64 registry trees.
The user is prompted to select on which instance he wants to deploy our extension.
Based on selected instance I'm quering registry for actual location of Reporting Services in file system which is usually something like "C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services" and storing this value in a MSI Property.
Then by using Set Directory action I'm setting destination directory of a component (our extension) to the value of that MSI Property.
Everything is installing perfectly fine unless you've trying to install it for x64 Reporting Services in that case extension files are installed to wrong location. Even thou MSI Property is set to correct path "C:\Program Files\MicroSoft..." (I've checked msi log) it looks like system is automatically redirecting to "Program Files (x86)".
Is there any possible solution to overcome this issue?
If you need to install to the 64-bit ProgramFiles folder, use a 64-bit MSI.
Finally solved this issue myself without creating 64bit MSI by using InstallScript custom actions.
First custom action to install:
Manually copy required files to desired location (InstallScript can access x64 Program Files)
Save this location in registry as a key component for this feature to use during uninstall
Second custom action to uninstall:
Read installed location from registry (do not use System Search to get this value due to it'll be auto translated by WindowsInstaller to "ProgramFiles (x86)")
Delete files
You can change the INSTALLDIR property to ProgramFile64 rather then ProgramFiles, this will help you to install on desired path, since you application is 32-bit so the path will be C:\ProgramFiles(x86)\Your Company Name\Your Product Name along with this have you made your components as 64-bit compatible?