Created a new fsharp project from Visual Studio Code (Version 1.12.2) while trying to build it with FAKE it is showing this error
"Cannot open assembly '.paket/paket.bootstrapper.exe': No such file or directory."
I checked the .paket folder of my project the paket.bootstrapper.exe is missing in there.
I using ionide 2.25.14, ionide-fake 1.2.3 and ionide-Paket 1.6.3.
I tried building the project with msbuild and it is building without any errors.
EDIT
This is how the build target is defined in the build.fsx.
Target "Build" (fun _ ->
// compile all projects below src/app/
MSBuildDebug buildDir "Build"
appReferences |> Log "AppBuild-Output: "
)
Downloading paket.bootstrapper.exe from github and adding in to the .packet folder resolved the issue.
The simplest, and maybe the best thing to do is to download paket.bootstrapper.exe if it didn't get generated along with your project.
Your build script is trying to run paket.bootstrapper.exe, but can't find it, likely because your project was generated without one. If you already have a folder named .paket, then your project was likely generated with a paket.exe, instead.
The only thing paket.bootstrapper.exe does is download the latest version of paket.exe. Your build script is just trying to automate keeping your package manager up to date.
Related
I'm using Atom as a latex editor, with packages build, language-latex, and latextools installed. Now when I try and build using Ctrl-Alt-B, the latex file compiles and gives a pdf output, but when I build using f9, an error is thrown that says:
No eligible build target.
No configuration to build this project exists.
Also, when I press f7 to show the build targets, it says "no targets found."
Could someone enlighten me as to what I'm missing in the setup for latex?
The build package is an unopinionated base package that requires the installation of separate service providers. In the case of LaTeX, you likely want to use build-latex.
you need a base branch or a template theme to include hot keys for your specific thread or template...
I recommend using sphinx
https://www.sphinx-doc.org/en/master/contents.html
https://www.sphinx-doc.org/en/master/py-modindex.html
I am getting the following error when building the android project generated by Zebble for Xamarin.
I followed the steps in -READ-ME-NOW!!!!!!!!!!!! text file. When I did build the android project, this is error I got:
The command "Zebble" update-schema auto" exited with code -1.
Some additional error log I found from Build output:
EXEC : error : Failed to update the xml schema for intellisense: Failed to find the UWP exe file. Searched all EXE files inside: E:\Labs.NET\Xamarin\TestZebble\TestZebbleApp\Run\UWP\bin
Could you please tell me what has gone wrong.
Hope this helps:
Remove all zebble folders from nuget packages folder.
Remove the Run\Android\Zebble.exe file.
Update the zebble nuget to latest version.
Set the Android project as startup project.
From Build > Configuration Manager be sure that Build and Deploy are enabled for android project.
Rebuild the solution.
We have implemented Continuous Integration with Jenkins to help perform our builds for faster deployment. We have reviewed the documentation provided through the Xamarin website, and have come to an issue. In the walkthrough it describes how to use various plugins to perform the process, we use build scripts to perform our builds because we have some post-actions that we execute after the build, such as submitting the ipa to the TestFlight. The problem is that for iOS it is has been documented that we need to use xbuild instead of mdtool when building from the terminal/command line.
We followed this portion of the guide to construct our xbuild within the build script. It appears that the xbuild command works and creates the project reference dlls and even generates an exe, but does not generate an ipa file even if we set this /p:BuildIpa=true on the xbuild to ensure the ipa generation. We also have provided a location for the ipa to be generated within to ensure we are not missing the file with this /p:IpaPackageDir=$BUILD_PATH. Here is the whole xbuild command that we are currently using, is there something that is incorrect or we are missing?
/Library/Frameworks/Mono.framework/Commands/xbuild $PROJECT_FILE / t:Build /p:BuildIpa=true /p:IpaPackageDir=$BUILD_PATH /p:Configuration=”Release” /p:Platform=”iPhone” /p:OutputPath=$BUILD_PATH
($BUILD_PATH) -- The build path is just “%WORKSPACE%\bin\iPhone\Release\”
I did find this resource as well, which states that xbuild requires the solution file for iOS to build correctly, is that correct?
If this is correct, how do we resolve these errors because I have not been able to find any documentation that explains how to properly define the solution and project files for xbuild deployment, or even how to exclude particular projects during the build:
/Users/developer/.jenkins/workspace/Mobile3_Branch_3.20/ServicePro/iOS/Mobile3.Forms.UWP/Mobile3.Forms.UWP.csproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/WindowsXaml/v14.0/Microsoft.Windows.UI.Xaml.CSharp.targets, to import. Ignoring.
/Users/developer/.jenkins/workspace/Mobile3_Branch_3.20/ServicePro/iOS/Mobile3.ServicePro.UWP/Mobile3.ServicePro.UWP.csproj: warning : Could not find project file /Library/Frameworks/Mono.framework/External/xbuild/Microsoft/WindowsXaml/v14.0/Microsoft.Windows.UI.Xaml.CSharp.targets, to import. Ignoring.
Project "/Users/developer/.jenkins/workspace/Mobile3_Branch_3.20/ServicePro/iOS/Mobile3.sln" (Mobile3.ServicePro.iOS target(s)):
Target ValidateSolutionConfiguration:
/Users/developer/.jenkins/workspace/Mobile3_Branch_3.20/ServicePro/iOS/Mobile3.sln: error : Invalid solution configuration and platform: "“Release”|“iPhone”".
Task "Error" execution -- FAILED
Done building target "ValidateSolutionConfiguration" in project "/Users/developer/.jenkins/workspace/Mobile3_Branch_3.20/ServicePro/iOS/Mobile3.sln".-- FAILED
Done building project "/Users/developer/.jenkins/workspace/Mobile3_Branch_3.20/ServicePro/iOS/Mobile3.sln".-- FAILED
Here is the xbuild command we used to build the solution:
/Library/Frameworks/Mono.framework/Commands/xbuild /p:Configuration=”Release” /p:Platform=”iPhone” /p:OutputPath=$BUILD_PATH /p:BuildIpa=true /p:IpaPackageDir=$BUILD_PATH /t:Build $SOLUTION_FILE
We are not concerned with building the UWP projects when building the iOS project because we have a separate build script that generates the appxbundle file correctly.
You can build an "individual project/app" by setting the SolutionDir and building a .csproj, all the referenced projects will be built and an .ipa created, something like:
xbuild
/p:SolutionDir="./src"
/p:OutputPath="$PWD/artifacts/"
/p:IpaPackageDir="$PWD/artifacts/"
/p:Configuration=Release
/p:Platform=iPhone
/target:Build
src/iOS/XamarinForms.iOS.csproj
Note: This assumes your provisioning profiles are setup on this Mac.
I try to use Realm database(version 0.74.1) in Xamarin.Android project. When I do build all is ok, but when I try to run project i get error
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Error executing task BuildApk: /{SolutionPath} /packages/Realm.0.74.1/lib/MonoAndroid44/arm64-v8a/libwrappers.so.
what I can do in this situation?
The APK is not built during the default build phase so you only get verification that libraries are in the right place when you run the debugger, or explicitly build an APK.
Can you check if the libwrappers.so file is actually in that location in the packages directory? It should have been put there by NuGet.
Also, is there just one Android target in the solution or have you created a PCL and Android target. The NuGet needs installing into both.
I am trying to run sample code "MyHierarchicalUI" from section 4.2 from "book of vaadin" and this code refers to TreeExample and TableExample classes which can be found at
http://dev.vaadin.com/svn/doc/book-examples/
I downloaded the book example code from mentioned svn link and imported it as existing eclipse project,however when I try to compile / run this project in eclipse I get the following error.
Errors occurred during the build.
Errors running builder 'Integrated External Tool Builder' on project 'book-examples'.
The file does not exist for the external tool named Copy sources.
The file does not exist for the external tool named Copy sources.
book-examples project is not valid vaadin project so can not be imported directly, we can not build it directly as vaadin project due to missing artifacts like ivy.xml and ivysettings.xml.
To use any code from book-examples project you will have to bring the code to your project manually (copy/paste), however a support ticker to make book-example project import-able / build-able and run-able has been created and can be tracked using this link Ticket # 13078.