I am trying to publish a website in VS2019 and it fails with
The command "dotnet bundle" exited with code -2147450730.
I haven't found much on this issue.
The build output window should have detailed information on the error:
Build started...
1>It was not possible to find any compatible framework version
1>The framework 'Microsoft.NETCore.App', version '2.0.0-preview1-002111-00' (x64) was not found.
1> - The following frameworks were found:
1> 6.0.2 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
1>
1>You can resolve the problem by installing the specified framework and/or SDK.
1>
1>The specified framework can be found at:
1> - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.0.0-preview1-002111-00&arch=x64&rid=win10-x64
After I installed the missing framework it worked for me: https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.0.0-preview1-002111-00&arch=x64&rid=win10-x64
Related
I'm trying to install and run x64 Mercurial 3.8.3, but I'm getting the following error:
D:\Program Files\Mercurial>hg.exe
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
Running sxstrace.exe gives the following log:
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = D:\Program Files\Mercurial\hg.exe
AssemblyDirectory = D:\Program Files\Mercurial\
Application Config File =
-----------------
INFO: Parsing Manifest File D:\Program Files\Mercurial\hg.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\WINDOWS\WinSxS\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9177_none_acd40623e1d81331.manifest
INFO: Begin assembly probing.
INFO: End assembly probing.
ERROR: Activation Context generation failed.
End Activation Context Generation.
It seems like it's looking for C:\WINDOWS\WinSxS\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9177_none_acd40623e1d81331.manifest, which doesn't exist on my computer. I think this file comes from the Microsoft Visual C++ 2008 Redistributable Package (x64), but when I installed/repaired it I still get the same error.
I've also come across this same package from chocolatey, but its version history seems to indicate that its latest version is 9.0.30729.6161, not the 9.0.30729.9177 I'm looking for. I'm not sure where to find this version of the package.
I've already looked at these questions which seem very similar to my situation:
Side by Side configuration is incorrect error
Visual Studio 2012 Side by side configuration is incorrect
Edit: I've just reinstalled with x86 Mercurial and it works. Not ideal, but at least it's a workaround.
Microsoft Visual C++ 2008 Redistributable Package 9.0.30729.9177 doesn't seem to be publicly available, so I ended up reinstalling Windows. Now I can run Mercurial after installing it.
I cloned the drill git repository and when I run
mvn clean package -DskipTests
I get this error
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (validate_java_and_maven_version) on project drill-root: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
You need to use JDK 1.7 to build Apache Drill.
The Drill team added maven-enforcer-plugin to the build process to make sure that build gives an error if someone tries to build using an unsupported version of Java or Maven. If you scroll up you will see an earlier error message like the following:
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (validate_java_and_maven_version) # drill-root ---
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message:
Detected JDK Version: 1.8.0-51 is not in the allowed range [1.7,1.8).
A lot of people want to run Drill using JDK 1.8. There's good news on that front. While you can't build using JDK 1.8, once you've built, you can run Drill with JDK 1.8 just fine.
I am making a ActionScript library which is a Flex 4 project for my Adobe AIR Native Extension in FlashDevelop. When I build the project its successful, but when I try to build the project with ExportSWC plugin to get .swc file I get the following message:
Prebuilding config C:\Users\Osama Mohammed\Documents\AndroidSIPManager\obj\AndroidSIPManager.flex.compc.xml...
Configuration writen to: C:\Users\Osama Mohammed\Documents\AndroidSIPManager\obj\AndroidSIPManager.flex.compc.xml
Running Process:
"C:\Program Files (x86)\FlashDevelop\Tools\flexsdk\bin\compc.exe" -load-config+="C:\Users\Osama Mohammed\Documents\AndroidSIPManager\obj\AndroidSIPManager.flex.compc.xml"
Error loading: C:\Program Files\Java\jdk1.7.0_25\jre\bin\server\jvm.dll
Building AsDoc
AsDoc temp output: C:\Users\Osama Mohammed\AppData\Local\Temp\7827039c-c329-4b6d-acb7-447146a5f4fe
Start AsDoc: C:\Program Files (x86)\FlashDevelop\Tools\flexsdk\bin\asdoc.exe
-lenient=true -keep-xml=true -skip-xsl=true -output "C:\Users\Osama Mohammed\AppData\Local\Temp\7827039c-c329-4b6d-acb7-447146a5f4fe" -source-path "c:\users\osama mohammed\documents\androidsipmanager\src" -doc-classes com.innovative.androidsipmanager.AndroidSIPManager com.innovative.androidsipmanager.Main -exclude-dependencies=true -target-player=10.1
Following is the error:
Error loading: C:\Program Files\Java\jdk1.7.0_25\jre\bin\server\jvm.dll
AsDoc complete (6)
Build failed (6).
Please help me in solving this error.
I had to remove Java 64 bit & install Java 32 bit. Now it is working.
I have been working on getting some of the simple Cuda 5.0 samples to work on Windows 7 with CMake. I'm running Windows 7 64-bit and Visual C++ Express 2010.
I had this working the other day and now it fails to compile, and I'm not quite sure why. I generally do my coding in *nix environments so windows development environments aren't a strong area for me.
If anyone can help save me from pulling out more hair it'd be greatly appreciated.
The example is just the simple vectorAdd.cu file that comes with Cuda and a CMakeLists.txt file. In the interest of keeping this posting short I'll hold off on putting the source file up since it's a little long.
Here's my CMakeLists.txt file:
CMAKE_MINIMUM_REQUIRED( VERSION 2.8 )
PROJECT( vectorAdd )
FIND_PACKAGE( CUDA REQUIRED )
CUDA_INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR} )
CUDA_ADD_EXECUTABLE( ${CMAKE_PROJECT_NAME} vectorAdd.cu )
When I try to compile, I get this output:
1>------ Build started: Project: ZERO_CHECK, Configuration: Debug Win32 ------
1>Build started 2/10/2013 6:24:59 PM.
1>PrepareForBuild:
1> Creating directory "D:\Code\CPlusPlus\Cuda\example_1\Build\Debug\".
1>InitializeBuildStatus:
1> Creating "Win32\Debug\ZERO_CHECK\ZERO_CHECK.unsuccessfulbuild" because "AlwaysCreate" was specified.
1>CustomBuild:
1> Checking Build System
1> CMake does not need to re-run because D:/Code/CPlusPlus/Cuda/example_1/Build/CMakeFiles/generate.stamp is up-to-date.
1>FinalizeBuildStatus:
1> Deleting file "Win32\Debug\ZERO_CHECK\ZERO_CHECK.unsuccessfulbuild".
1> Touching "Win32\Debug\ZERO_CHECK\ZERO_CHECK.lastbuildstate".
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:00.07
2>------ Build started: Project: vectorAdd, Configuration: Debug Win32 ------
2>Build started 2/10/2013 6:24:59 PM.
2>InitializeBuildStatus:
2> Creating "vectorAdd.dir\Debug\vectorAdd.unsuccessfulbuild" because "AlwaysCreate" was specified.
2>ComputeCustomBuildOutput:
2> Creating directory "D:\Code\CPlusPlus\Cuda\example_1\Build\CMakeFiles\vectorAdd.dir\Debug\".
2>CustomBuild:
2> Building NVCC (Device) object CMakeFiles/vectorAdd.dir//Debug/vectorAdd_generated_vectorAdd.cu.obj
2>nvcc : fatal error : Could not set up the environment for Microsoft Visual Studio using 'C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/../../common7/Tools/vsvars32.bat'
2> CMake Error at vectorAdd_generated_vectorAdd.cu.obj.cmake:206 (message):
2> Error generating
2> D:/Code/CPlusPlus/Cuda/example_1/Build/CMakeFiles/vectorAdd.dir//Debug/vectorAdd_generated_vectorAdd.cu.obj
2>
2>
2>
2>Build FAILED.
2>
2>Time Elapsed 00:00:00.29
3>------ Skipped Build: Project: ALL_BUILD, Configuration: Debug Win32 ------
3>Project not selected to build for this solution configuration
========== Build: 1 succeeded, 1 failed, 0 up-to-date, 1 skipped ==========
Anyone have a suggestion? I don't think I changed any settings from the time it worked to the time it stopped working. I've tried rebooting and all that stuff.
I'm trying to install the gecko package in freepascascal using this guide: http://wiki.lazarus.freepascal.org/GeckoPort_version2#Win32_widgetset
Unfortunatly when I run C:\lazarus\fpc\2.6.0\bin\i386-win32\fppkg.exe install gecko I get:
Install dependencies An unhandled exception occurred at $004377D5 :
EProcess : Failed to execute fpc.exe -iVTPTO : 2
$004377D5
$0040F953
$00412B36
$004138D5
$00414553
$00413AE5
$0041568B
$0041E3E3
The FPC Package tool encountered the following error: [lazmkunit]
Execution of FPMake build failed
Put c:\lazarus\fpc\2.6.0\bin\i386-win32 in your PATH.
fppkg queries other FPC binaries to retrieve version and target info, and to compile the result (as fppkg downloads source, and then compiles it on host).