Error building cordova windows8 - windows

When i build current project for wp8 , everything works fine. When i build for windows8 i get following error :
: error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft
\VisualStudio\v12.0\JavaScript\Microsoft.VisualStudio.WJProject.Default.props"
was not found. Confirm that the path in the declaration is
correct, an d that the file exists on disk.
I have spend a couple of hours searching for solution on the internet but to no avail.
Anyone have any ideas ???

I have been troubleshooting the same issue, but I am building for Windows 7. However, when I searched, I found this, which is specific to Windows 8, and may be the key to your answer.
Found at http://gmc.yoyogames.com/index.php?showtopic=570925:
On that page under Visual Studio it states: "You will also need to install a version of Microsoft Visual Studio ... that supports Windows Store Javascript app creation.."
and
its Visual Studio Express for Windows 8. I had installed Visual Studio Express for Desktop which is not suitable.

In my case, the problem was that the project had VS 12.0 coded as a variable into the jsproj file while I was using VS 14.0 (VS2015). Changing the "12.0" to "14.0" fixed it for me, once I saved changes, closed and reopened the project
.

Related

Could not load UI satellite dll 'FileTracker32UI.dll'

I've run in to an issue where I can't build a freshly created C++/CLI Class Library project in Visual Studio:
Even though I haven't made any changes I get an error when I try to compile:
Severity Code Description Project File Line Suppression State
Error Could not load UI satellite dll 'FileTracker32UI.dll'. Make
sure it exists in an LCID subdirectory of 'C:\Program Files
(x86)\MSBuild\14.0\bin\'. TestProject c:\Users\abcde\documents\visual
studio 2015\Projects\TestProject\TestProject\FileTracker 1
I've created C++/CLI Class Library projects in the past on the same computer using Visual Studio 2015 without encountering this problem. Any idea what has gone wrong?
I ran into this strange issue today without making any code change. I suspect it appeared due to overnight windows update.
In my case , I copied the two files FileTracker32UI.dll and FileTracker64UI.dll
From
C:\Program Files (x86)\MSBuild\15.0\FileTracker\3082\
To
C:\Program Files (x86)\MSBuild\14.0\Bin\3082\
and it worked. My visual studio version is
Microsoft Visual Studio Community 2015
Version 14.0.25123.00 Update 2
I am hoping the info helps someone.
I had the exactly same problem, after some windows update by my IT.
According to the information (https://forum.dlang.org/post/ezuohezwuzyitjdzpfdw#forum.dlang.org), I renamed the file "FileTrackerUI.dll" to "FileTracker32UI.dll" in the latest LCID folder (latest numbered folder in same location)
Then, it worked at my PC.
Good luck
In my case it was a path issue. Using another directory (shorter path without special characters) solved the problem

Where to set RemoteRootDirectory to compile iOS C++ Shared Library in VS 2017

I get the error:
Error MSB4044 The "VCRemoteClean" task was not given a value for the required parameter "RemoteRootDirectory".
My Environment consists of a PC with Visual Studio 2017 (professional)
with the Xamarin build agent successfully linked to the MAC
My Mac has Xcode 8.3.3 and Visual Studio 2017 for the MAC
My project is a Xamarin forms with a PCL. It compiles for iOS and successfully creates an IPA file
I add a C++ cross platform shared project. If I try to build or compile the iOS project I get the error above.
I looked in the file iOS.Common.targets located at C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VC\VCTargets\Application Type\iOS\1.0
It references the environment variable RemoteRootDirectory. I am not sure where it should be set.
Thanks in advance for any help,
Scott
It seems the reason for the error is that vcremote isn't connected to a remote MacOS computer. Here is a VS developer community answer that can be found when searching for this error:
https://developercommunity.visualstudio.com/content/problem/43015/error-msb4044-the-task-was-not-given-a-value-for-t.html
The author itself answered:
I was able to set it in iOS.Common.targets to
/Users//xcremote/. After that the real error became more
clear. vcremote was not connected.
See here on how to set it up:
https://msdn.microsoft.com/en-us/library/mt147405.aspx
The article links to a VS 2015 article, though. The latest VS 2019 link is here:
https://learn.microsoft.com/de-de/cpp/cross-platform/install-and-configure-tools-to-build-using-ios?view=vs-2019&redirectedfrom=MSDN

Error MSB4057 in Microsoft.Common.targets

I have Visual Studio 2010 SP1.
I wrongly edit and save the file
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
and now I can't compile anymore.
The error I got is
1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.Targets(767,39):
error MSB4057: The target "_Xsd" does not exist in the project.
I reinstalled Visual Studio 2010, I copied the file from another computer but nothing works and I still have the same error. What can I do?
I search the solution on Internet and i found:
Copy the right target file from another machine to replace the target file.
Uninstall and re-install .Net Framework 4.0 and check if it works.
I tried to restore or install new version of the .NET framework, but other problems occured during installation maybe dued also by hardware problems (i got blue screen sometimes).
I know it isn't a good solution, but at the moment I solved the issue by formatting and reinstalling everything.

vs 2013 portable class library windows.props not found

In visual studio 2013 update 2 RTM if I do file new project, Portable Class library, asking for .NET 4.5 and Silverlight 5 targets I get this error on build
Error 1 File 'Windows.props' not found. See http://go.microsoft.com/fwlink/?prd=12395&pver=1.0&plcid=0x409&ar=MSDN&sar=PlatformMultiTargeting&o1=Portable&o2=7.0 for more information. PCL
The link is a dead link
I'm building and developing on a windows 2008 R2 Enterprise server box
The same project on windows 7 builds fine.
Any help greatly appreciated!
Did a compare with the C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1 libraries from one box to other and seems some were missing on server. sync'd them and we seem ok now. V strange as clean install.

Cannot compile .NET CF project containing Design time attributes without Visual Studio?

I'm working on a .NET Compact Framework 3.5 app. I have an automated build machine that does not have Visual Studio installed, and all has been fine.
I'm trying to a a new solution containing control projects that have DesignTimeAttributes.xmta files. MsBuild on the build machine is failing with cannot find file, C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5\Bin\genasm.exe.
I've tried manually adding this directory and it's contents from my dev box to the build machine, but now I'm getting
c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.CompactFramework.Common.targets(67,9): error : genasm.exe(1) : error There was an error reading arguments. Could not load file or assembly 'Microsoft.CompactFramework.Build.Tasks, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Done executing task "BuildAsmmeta" -- FAILED.
Before I struggle further with this, I thought I'd ask if anyone else out there has gotten a CompactFramework project with design time attributes building on a machine without Visual Studio?
Filburt: I've already installed the Windows SDK, the .NET SDK, and the CF SDK. I realize now that "all has been fine" in the original question doesn't make that clear.
None of the SDK's installed anything into the Microsoft Visual Studio 9.0 directory.
I've given up and installed VS at this point, but thanks for the answer.
You think need to install the Windows .NET Framework SDK on your build machine to obtain the tools that come with Visual Studio.
update
Since you stated you installed all SDKs you could check %ProgramFiles%\Microsoft SDKs\Windows\v6.1\Bin\SetEnv.cmd for any quirks in the PATH settings. I discovered some inconsistencies there for an x64 environment.

Resources