I have successfully got "google test adapter" v 0.11.1 working on a laptop with vs 2017 community.
However, on my desktop (much preferred machine for coding), also running vs 2017 community, despite being able to install it (apparently flawlessly) the option for Google tests in the new project menu is just simply not there.
I have uninstalled and re-installed "google test adapter" several times.
Each time the install appears successful (because I can find it to uninstall it) in extensions and updates. However, never does it appear as a project option.
I cannot see what more to do to solve this inexplicable conundrum.
I would appreciate some help...
I have an update:
There was a one version difference of google test adapter between the two computer systems - v 0.11.1 and v 0.10.1.
Version 0.10.1 works properly and version 0.11.1 does not!
So the latest version is somehow problematic - what the issue is I have no idea...
If you are still having that problem, please open an issue on the Google Test Adapter GitHub page.
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
I'm hoping that WSL2 solves these problems and makes this question obsolete in the next 6 months or so, but in the meantime, I don't feel comfortable running bleeding edge or other preview releases of Windows on my primary laptop.
Sometimes, when I'm installing Ruby gems (bundle install or bundle install --path=vendor/bundle) inside of WSL, I get Permission denied errors when installing a gem with a native extension.
The most recent incarnation of this error was this:
Permission denied # rb_file_s_rename - (./.gem.20191006-12131-11th7ub/byebug, /home/thomasowens/project/vendor/bundle/ruby/2.6.0/extensions/x86_64-linux/2.6.0-static/byebug-11.0.1/byebug)
To resolve it, I simply deleted /home/thomasowens/project/vendor/bundle/ruby/2.6.0/extensions/x86_64-linux/2.6.0-static/byebug-11.0.1/byebug, reran the bundle command, and it succeeded. Sometimes, I need to do this multiple times, but it usually works.
In the end, I can get all of the gems installed properly, but it's hard when setting up a new project and there are many gems with native extensions. Same when I'm introducing a new gem or updating a gem that causes the native dependencies to need to be updated.
I haven't found much about this issue, but I'm wondering if there is something that I can do to alleviate the pain of needing to run bundle install multiple times to get a project set up and running under WSL.
The problem that I'm experiencing may be related to Visual Studio Code's file watching. It is reflected in two GitHub issues against WSL - 1956 and 3395. Visual Studio Code has remote.WSL.fileWatcher.polling, which can be enabled which works around this issue. However, the documentation states that there is a performance impact for large workspaces and it may be necessary to also adjust the remote.WSL.fileWatcher.pollingInterval setting. WSL2 will resolve these issues.
Since enabling this flag, I haven't seen the error while working with VS Code running.
Now that WSL2 is out, I was able to disable this flag and the issue has not reappeared. It appears that if you can upgrade to WSL2, that may be a preferred solution. However, for anyone who hasn't yet upgraded or can't upgrade, toggling the remote.WSL.fileWatcher.polling and remote.WSL.fileWatcher.pollingInterval should be good.
Since I updated Chrome, my tests don't work anymore.
I get this error:
Selenium::WebDriver::Error::SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 76
So I replaced
# Currently I have Chrome 78 installed
Webdrivers::Chromedriver.required_version = Webdrivers::Chromedriver.current_version.to_s
by
Webdrivers::Chromedriver.required_version = '76.0.3809.68'
But I got the exactly same error.
I also tried with the 76.0.3869.25.
As you can see here: https://github.com/titusfortner/webdrivers/blob/master/lib/webdrivers/chromedriver.rb#L76
The required version exists.
My tests are working on Travis. Any idea?
I got this problem today, and was able to fix it....
System: Windows10 Enterprise Desktop, Visual Studio Pro 2017
Used the VS Nuget UI to update the Selenium.WebDriver.Chrome package
Normally, this works, but I continued to get the same error as above
To fix:
- I went to where my Chromedriver.exe file was located and removed it.
- Then I re-built my application that uses Selenium
- My VS app then loaded a new Chromedriver.exe
3. Re-ran my Selenium test: Problem solved.
I am trying to deploy a HTML/CSS/JS Apache Cordova application from a windows machine to a Mac. I believe they are communicating properly through the remotebuild agent but when I attempt to build a blank project to deploy on the Mac this error is thrown at the very beginning of the build:
MDAVSCLI : error : The edge module has not been pre-compiled for node.js version v4.1.1. You must build a custom version of edge.node. Please refer to https://github.com/tjanczuk/edge for building instructions.
I have followed the link and have searched for the solution as to how to fix this error but the link does not seem to apply to what I am doing at all. I am not using any node.js functions in my code so I am confused as to why this error is occuring. I am only trying to build a nearly blank HTML page and I still get the error regardless of how simple I make the page.
How can I go about fixing this solution? what is the best way to get rid of this error or to as the error suggests pre-compile edge to work with node.js version 4.1.1?
There is an issue with Cordova 5.3.1 and Node v4.
https://github.com/Microsoft/cordova-docs/blob/master/articles/known-issues/known-issues-ios.md#building-for-ios-hangs-when-nodejs-v40-is-installed
I fixed by uninstalling Node v4.1.1 and installing Node v0.12.7
https://nodejs.org/en/download/releases/
#Dustin,
you have a misconception about how Cordova works. You say you want to deploy to a Mac, but I think you mean iOS. If so, you should read:
What's needed for iOS Development?
https://groups.google.com/forum/?fromgroups=#!topic/phonegap/bf1Hgkel3W4
I Quote
The short and sweet of it is as follows:
You need OS X + Xcode
You need several iDevices
You need $99/year for Apple Developer program (which you've already indicated is not a problem)
All of the above = cost-of-doing-business.
If you read the entire thread (especially the part from Kerri Shotz), you will get more information and more options.
Best of Luck
After losing a fair bit of hope and following a lot of posts, blogs and bug work-arounds with no luck I decided to click on the 'Run Dependency Checker' button in Visual Studio - Tools -> Options -> Tools For Apache Cordova -> Cordov Tools. This checker told me that Joyent Node.js wast installed. I did have node.js and npm set up on the latest version, im not sure what the difference is.
I went through the process of modifying the VS installation (change or remove a program) and sure enough Joyent Node.js wasnt checked. I cheked it and it went through the process of installing.
My VS installation now looks like the below and my project is building without:
MDAVSCLI : error : The edge module has not been pre-compiled for node.js version v4.1.1
I have recently installed the Aptana plugin for Eclipse as I wish to learn Ruby and Ruby on Rails, it doesn't seem to have changed anything. Usually when I install a plugin of the sort, there will be new project types under the "New Project" menu, but none appeared. I checked tutorials online and they suggest that there should be new project types as seen in the image below, taken from a tutorial.
Instead, I see the same options I did before.
I wondered if the plugin didn't install, but when I try to install it again, It says it's already installed. I am using Eclipse Juno Service Release 2 with a 64-bit Windows 7 operating system and the version of the plugin from the URL given on the Aptana website (http://download.aptana.com/studio3/plugin/install). Any help would be much appreciated.
I don't know why that's happening. Here's a suggestion for how to get around it.
You might be better off installing and running the standalone Aptana Studio product. It would be a separate installation on your desktop, and thus wouldn't have the same settings as any Eclipse installation you already had, and would be more space on your hard drive. But probably there isn't much you would share between Ruby/Rails development and other development, and it's not that much space.
I've done it both ways - installed Aptana into an Eclipse I've already got, and installed the standalone version - and now I would only do standalone.
I don't know what was wrong in the first place, but after I installed the Aptana plugin, I installed the PyDev plugin. I think this removed the Aptana plugin because of conflicting dependencies (I don't know why it wouldn't tell me, though). I tried installing the Aptana plugin again and it told me there was a conflicting dependency with the PyDev plugin, so I uninstalled it and reinstalled the Aptana plugin. It works now.