When i tried to install plugin Live edit in PHPStorm, and run it by debugging i get this error
Registry key js.debugger.use.chrome.extension is not defined. I don't know what's the problem with it.
Related
In my app.json folder, I have everything bundled nicely, but I have one undefined package at the bottom of the install list:
"undefined": "react-navigation/bottom-tabs"
I tried running an "npm install react-navigation/bottom-tabs" but it threw this error:
warn Package undefined has been ignored because it contains invalid configuration. Reason: Cannot find module 'undefined/package.json'
Has anyone encountered an issue like this before? I am running React-Native Version 5 on top of Expo.
EDIT: It turns out that it was supposed to be #react-navigation/bottom-tabs, so I installed that and made an adjustment; but now I am still stuck with the original undefined package in my app.json folder, and cannot get rid of it.
So, I forgot this post existed and I actually figured this out months ago. When you're dealing with:
A bad bundle,
the wrong version,
or there's just something wrong with your 'package.json' file, (the file that contains the list of your packages)
These steps should fix it:
Perform "npm uninstall 'package-name' " or "yarn remove 'package-name'"
Note: You do this instead of 'expo-uninstall' because 'expo-uninstall' does not exist. We use 'expo-install' instead of 'npm' or 'yarn' install to make sure you download the proper npm or yarn version associated with your version of expo.
Open the package.json file and see if the bad package you uninstalled is still present.
If the bad package is still there, select and delete it from the file, then save.
Run an "expo" "npm" or "yarn" install on the correct package name
This should fix it. This is best fixed when step 4 is executed with an 'expo install' as you likely have an incompatible version of the package, so this will prevent that from happening again.
In my case, I couldn't figure out why my terminal was telling me a specific package didn't exist, so I did a "sud" command to force download the package. This package didn't exist, because I had actually spelled it wrong.
try deleting your node modules and install them again and make sure your metro is closed
clear cache and you are good to go by the way it worked for me
npm install or yarn add
npm start --reset-cache
In fact, I wanted MySql.Data.Entity.EF6, however, for some reason Visual Studio ADO EDMX editor wanted MySql.Data.Entity.EF5 (same version, 6.9.9.0).
First, I checked if the NuGet packages 'MySql.Data' and 'MySql.Data.Entity' were installed.
I then issued the following command in PowerShell to reinstall all packages to help fix any .net version errors:
update-packages -reinstall
and proceeded to verify that all references in web.config were correct; however, the error remained. I even reinstalled MySQL for Visual Studio 1.2.6, but still the same.
(FYI: Restarting Visual Studio at each step above)
The solution for me was to simply add a new "dummy" ADO Entities Data Model to the project, referencing the same database (not sure this matters), which seemed to correct some references (somewhere) within the solution/project to the wrong version of the MySQL DLL (the error said 'EF5', but it should have been looking for 'EF6'). I'm sure there was a cache somewhere that was doing this, but just not sure where.
Edit: In retrospect, I perhaps should have tried deleting the obj folder first, as there are some *AssemblyReferences*.cache files in there. I tried rolling back to a previous version of the source (using Git) to test this, but the old version works now! So I'm sure it must have been the obj folder, which is ignored by Git by default.
I installed a cakephp 3 app via composer from the root of my website c:wamp/www/my_app, and I developed untill i need to implement acl.
I installed the acl plugin for cakephp 3 via composer for the same path c:/wamp/www/myapp and i configured it, was everything well, but when i test the implementation of acl, i get the following error:
Missing Component, Create the class AclComponent below in file: src\Controller\Component\AclComponent.php
and seems to be true, theres no such file in the above location, instead the file is in vendor/cakephp/acl/src/controller/component.
Was investigating and i find that composer doesnt install plugins in a cake default path, theres many articles about, but how doi correct my installation? I already did all the stuff to implement the access control lists.
Thanks in advance error screenshot
I have made a VS2010 project which installs MySQL by calling MySQLInstallerConsole.exe with necessary arguments. This works perfectly however, when I try to run this project's exe as a custom action it executes the exe but MySQL is not installed.
I checked the log file for MySQL exe and it had the following error:
Error 50: Package Name State change request failed.
What does this really mean, any solutions?
There are at least a couple of things that have something to do with this:
I believe the MySQL installer is an MSI file according to this:
http://dev.mysql.com/downloads/installer
You cannot install an MSI from a custom action of a Visual Studio setup because recursive calls to MSI installs are not allowed.
In a Everyone install custom actions run with the SYSTEM account, and installs are not often expecting this if they want to install files in user-profile folders because the SYSTEM account doesn't have any.
You need to bootstrap this somehow, and I think people are often using the WiX Burn bootstrapper for that. You define the ProductCode, name etc of the product and define how to install it.
When restoring packages via solution's context menu option "Restore NuGet Packages..." the MonoDevelop IDE still marks references to NuGet libraries as invalid and complains about non-existing namespaces. Restarting IDE helps as it clears MonoDevelop's cache, but is there a way to do this automatically? Perhaps some option in some settings that I've missed?
Not currently. Whilst MonoDevelop will detect assemblies that have been removed, and indicates this in the Solution window by marking the reference in red, it does not detect assemblies that been added back.
Debugging MonoDevelop it seems as though MonoDevelop detects changes to the solution file and project file and will reload them. Other changes, such as assemblies being restored, are ignored.
If possible I will have a look at changing the NuGet addin so it asks MonoDevelop to check the references after a package restore.