I have installed WDK and SDK on my Pc.. I can see them on my system.. But I am not able to get "x64 checked build environment command prompt"..My OS is windows 8.1 .. If anyone has a solution to the problem please do let me know
If you open a VS developer prompt, you should have access to MSBUILD and from there, you need to use MSBuild command line parameters to build for x64 chk project. These variables would be /p:platform=x64 and /p:configuration=Win7 Debug. WDK will pick the right cross arch compiler and build for the respective configuration.
Related
I am new to electron and trying to build a windows installer for the electron app using my mac. I am using electron-packager to package the app and then electron-wix-msi to build the installer. When the build installer steps are executed, the error Unable to read file info from exe. Falling back to packaging description. Error: spawn Unknown system error -86 is thrown. please see the full error message in the attached screenshot.
I would like to highlight that when I build an installer for macOS, it works. Should I understand that I can not build a windows installer using mac?
build_installer64.ts file:
You can't do that, you have to do this on the Windows platform.
I use GitHub Actions to build my app for each platform, code for Windows:
https://code.korbsstudio.com/KorbsStudio/electron-builder-sample/-/blob/main/.github/workflows/build.yml#L52-71
Optionally, you can also use a Windows virtual machine and repeat the same process in there.
Update, for those interested in doing this on Linux, building a EXE setup file seems to be possible. You'll need to have wine installed and use:
npx electron-builder build --win
I have a visual studio project that generates an exe file. I can run this project from within Visual Studio Community for Mac simply by clicking Run for the Release or Debug configurations.
I need to be able to do this from the command line. I've tried using wine but it throws exceptions that I never see in VSC.
Thanks #Lex Li!
The solution is to open a terminal and run
mono <path to your app> <your app's arguments>
I am using Visual studio for mac. I need to install some packages but I can't find package manager console for that.
Visual studio version: Preview 1 (7.0 build 347)
Warning:
A commenter reports this extension crashes VS Community 2019 for Mac version 8.5 (Build 3183). I haven't upgraded to it, so I can't speak to this. Anyone with information/fix/alternate approach, please chime in down in the comments.
OK:
At least in Visual Studio Community 8.4.8 build 2, you can find it under Visual Studio-->Extensions, using search term "nuget":
It took me so long to find this I hope it helps someone else find it faster!
Similar to Xamarin Studio, you have to use its dialog,
https://developer.xamarin.com/guides/cross-platform/xamarin-studio/nuget_walkthrough/
As there was no cross platform PowerShell, Xamarin Studio lacks of Package Manager Console. It might come one day in Visual Studio for Mac. We will see.
You can follow the NuGet CLI reference and install it
https://learn.microsoft.com/en-us/nuget/tools/nuget-exe-cli-reference
An excerpt from that link provided reads:
macOS/Linux
Behaviors may vary slightly by OS distribution.
Install Mono 4.4.2 or later.
Execute the following commands at a shell prompt:
# Download the latest stable `nuget.exe` to `/usr/local/bin`
sudo curl -o /usr/local/bin/nuget.exe https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
# Give the file permissions to execute
sudo chmod 755 /usr/local/bin/nuget.exe
Create an alias by adding the following script to the appropriate file for your OS (typically ~/.bash_aliases or ~/.bash_profile):
# Create as alias for nuget
alias nuget="mono /usr/local/bin/nuget.exe"
Reload the shell. Test the installation by entering nuget with no parameters. NuGet CLI help should display.
I found a good reference for mac users:
https://github.com/mrward/monodevelop-nuget-extensions
Thanks for the reference and it works for me.
I want to create an IPA file for both the release and debug for my app created in xamarin. I created the release IPA file with the following command in Bamboo:
-v build -t:Build "-c:Release|iPhone" CustomerApp.sln
This can be replicated on the terminal too by doing this:
/path-to-/mdtool -v build -t:Build "-c:Release|iPhone" CustomerApp.sln
But when I try to use the "-c:Debug|iPhone" this will not create the ipa file, when trying to use the terminal or Bamboo. I then tried different configurations like "-c:Release|iPhoneSimulator", "-c:Debug|iPhoneSimulator", "-c:Ad Hoc|iPhone" and "-c:Debug|iPhoneSimulator" but all of these will not create the IPA file. Why is this?
I know that the path to mdtool and the solution are fine because it works for the Release IPA but is it to do with the configuration in either Xamarin or Xcode?
If you are on the same Mac as the one you are running Xamarin Studio, it should mimic the provisioning profile setup you have in the IDE. If the build in Xamarin Studio builds with that combination with no drop down change on the main project, I would expect the mdtool to work. Note that now in Visual Studio 2017 for Mac it will be vstool under the /Applications/Visual Studio.app folder.
My build line looks like this:
/Applications/Visual\ Studio.app/Contents/MacOS/vstool --verbose build --f --target:Build --configuration:"Debug|iPhone" --buildfile:my.sln > $BuildResults
Update January 2019, I have found very little guidance on the web about what exactly vstool can do and how to use it. I believe it to be the Microsoft version of the mdtool, which is part of the Monodevelop project at Github (mono/monodevelop). The mdtool source code is under monodevelop/main/src/tools folder. It appears to be a runner for a variety of tools available in the Monodevelop / Visual Studio installation. Running
/Applications/Visual\ Studio.app/Contents/MacOS/vstool -q
will list out the available tools. There is also a man page as part of the Monodevelop build process, at monodevelop/main/man which provides a bit more enlightenment. I was shown how to use the specific command by someone who was very familiar with the project.
when I try to issue the build command from visual studio command prompt, I get the following error message:
Querying enlistment to find matching Build Definition tools path
ERROR. Tools download failed. Failed to find client workspace for
given current path e:\code\DisplayApps\Services\InsightsMediator\Dev.
Please make sure your current path is mapped into your workspace.
What could be wrong?
Update : this turned out to be a version mismatch problem..the workspace was created using VS 2012 and I as trying to use VS 2010 Command prompt to build. Using VS 2012 command prompt resolved the problem