Zebble VSIX insn't working. I tried to install, but it stuck. With different pc and internet. Same result. Why? Zebble was been drop?
It stuck if you don't install UWP SDK Tool before. So, you just have to install UWP SDK Tools in the visual studio installer e try again after that. :)
Related
I tried DISABLING the Spectre mitigation from the code generation in option, but i still cannot compile a simple hello world driver, why? how can i stop this message and just compile a simple hello world without needing to install these libraries? i tried to even install them using individual components, but there are 100 different versions in there.. tried installing the latest verison but didnt help..
I am using the latest version of visual studio 2019. SDK and WDK are both installed.
this is happening after i made a mistake of upgrading visual studio, everything was fine in my 2017 visual studio..
after you install those libraries( which is necessary ) you can go to project Property then C/C++ the Code Generation look down you going to find Spectre mitigation then you can enable it or disable it, this won't work if you didn't install those libraries which is necessary for the last update of visual studio
The Visual Studio does not have the G1ANT.Robot Addon Template. How to install the G1ANT SDK in the Visual Studio? What should I do? and which type of Visual Studio I had to download? Community or Enterprise or Professional?? Now I have downloaded the Community! Did any one get the G1ANT.Robot Addon Template??
You can download the community version and it should work just fine.
Use thik link to download the SDK: [https://github.com/G1ANT-Robot/G1ANT.Sdk/raw/master/G1ANT.Sdk.vsix][1]
You can try ending the process if the installation gets stuck but the sdk will be installed anyways.
Hope this helps!
I am trying to install OpenCV 3.2.0 and run CannyStill.cpp according to the following instructions.
Installation Cheat Sheet 1 - OpenCV 3 and C++.pdf
I am using VS2013 plus Win7.
I have set the Runtime Library to /MTd.
I have installed VC++ 2015 Redistributables.
but the problem is not going away.
How can I solve the issue?
The problem is that your OpenCV was compiled with another Visual Studio compiler (2015). With the redistributables you will get the release version of the dll, but not the debug one. The error is complaining about
MSVCP140D.dll
which is for debuging.
Possible solutions
You can recompile OpenCV (why is not compiled with the same visual studio in the first place?) with VS2013 and use that one.
Install VS2015 and use that one.
Compile it and run it in release mode.
Choose whichever suits you :)
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've just downloaded the ASP.MVC MSI package, but the installation fails with the "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." message.
I see that other people too have the same problem (http://forums.asp.net/p/1336453/2699267.aspx). Anybody else?
I'm running VS 2008 Professional edition with SP1 on Vista.
Some additional info: entries like Error in Template (C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\VisualBasic\Workflow\1033\StateMachineWorkflowLibrary.zip), file (StateMachineWorkflowLibrary.vstemplate). Unregistered ProjectType (VisualBasic). This can be caused by an incorrect ProjectType or because the project type package is not installed. appear in the event log.
BTW I don't have VisualBasic installed. I'm thinking about reinstalling VisualStudio ... :|
I removed all the bad templates and this didn't resolve the issue for me. I found that removing other Add-Ins I had installed let me install Beta 1. In my case the bad add-in preventing the install was Clone Detective.
I had this exact error message from a completely different MSI package - the DevExpress toolkit - turned out to be caused by one of the "defensive" packages installed on my machine.
Check your anti-virus, anti-spyware, anti-intrusion, firewall, anti-xxx etc etc packages to see if any of them might be stopping scripts from running properly.
Hope this helps.
The installer is trying to add templates to the VB package without checking to see if it exists first (ScottGuuuuuuu!).
If the rest of MVC is installed and working, forget about it. If not, you don't have to reinstall VS. A quick fix is to simply install Visual Basic (e.g, modify your installation rather than reinstall it).
Okey, like Simon said, Clone Detective addin was the troublemaker which prevented the installation of ASP MVC. I deinstalled Clone Detective and now MVC has installed without problems. Thanks guys!