Several members of our development team have started seeing the following errors when they open the Package Manager Console. It's completely preventing us from running Entity Framework commands. We've checked and the files mentioned do exist (GetEvent.types.ps1xml, Diagnostics.Format.ps1xml, Diagnostics.Format.ps1xml). We've tried restarting and cleaning the solution, but these don't seem to help. Has anybody encountered this before? Any ideas about how to fix it?
It was a bug in the latest Windows Management Framework release. An updated package has been released with a fix for this issue.
https://blogs.msdn.microsoft.com/powershell/2016/02/24/windows-management-framework-wmf-5-0-rtm-packages-has-been-republished/
Related
Earlier this week, my work upgraded Unity from 2021.3.1f1 to 2021.3.13f1. My coworker did this first and I pulled the changes (we are using Plastic SCM) I got these errors:
This is happening for both the Timeline and Visual Scripting Package
I thought that it might be due to being on the wrong version of Unity so I installed the 2021.3.13f1 version and the errors were still there. I have done many different things to try and fix this, but the problem still persists. Here are some of the things I have already tried:
Re-imported both my Assets and Packages folders
Deleted the whole project and re-downloaded it
Reinstalled the new version of Unity
Reset packages to defaults
Used a replace my package cache file with a co-worker's
Used a different workspace and branch in Plastic.
Tried using an entirely different project (the problem persisted in all projects)
Deleted the project and re-created it through cloud saves
Removed both of the packages from the project via the package manager and installed them again (this actually removed the visual scripting error when the package was removed, but the timeline errors persisted)
Using an older version of unity.
This apparently has not affected any of my co-workers and is only happening on my computer. I thought fresh installing EVERYTHING would fix it, but no.
Thanks for the help.
I am looking for a Version Control tool for SQLite database. So on exploring I came to know about Fossil which is recommended by SQLite also.
I am using latest version 2.7 for Windows and the problem I am facing is on using it in server mode and committing few files, it gets crashed frequently giving 'database is locked' error.
At first instance I thought that I am using the server and cloned copy on same system so it might be crashing due to this reason. But when I have started server on another system and even committing to it from a different system the result is same, It got crashed again.
Here's the screenshot of the crashed fossil server
Can anyone point me to the right direction that what I am doing wrong here?
Indeed, version 2.7 still had some wrinkles with a newly added backoffice functionality.
In general, the backoffice processing can be turned off via setting 'fossil set backoffice-disable true', see help on backoffice-disable
This would most likely resolve the issue you experienced.
Meanwhile, the recently released version 2.8 has those wrinkles resolved.
I've come to a problem while trying asp.net vNext beta8. I'm running a working project but I wanted to add a unit test project next to it. I've found that you should add the xunit and xunit.runner.dnx nuget packages in the project.json. while typing, the intellisense continuous me so I see that the package must be downloaded from nuget. after saving the project.json i get the error in my output, which says: An error occurred while sending the request.
Does anyone else get this problem or does anyone know the solution?
Thanks in advance :)
My problem appeared to be a corporate proxy which didn't like visual studio and the nuget package manager. when working on the guest network I was able to restore all the packages.
Just installed latest version of Edine from nodeclipse, and in the console that is the only message outside of path information for the directory the project is stationed in. Also tried grabbing the latest default version and tried to install via New Software with similar results.
C:\Users\user\AppData\Local\Temp\express-work\1406755265579/test
Unexpected Exception
Anyone had this ever work? All methods I'm finding online seem to be broken.
This is on Windows 7 64 bit.
For anyone that arrives at this question and has the same issue.
I was under the mistaken understanding that when installing Nodeclipse, it also installed node.js, express, and mongodb. This is not the case. Installing node.js and express resolved this issue.
I am using RAD 7.5 on a Windows XP m/c. Whenever I try to do a clean up/build the project, I get a message saying
The project was not built due to "Could not delete 'D:\Documents and Settings\User\My Documents\project\exe\EXE\WebContent\WEB-INF\classes\BusinessRules.properties'.". Fix the problem, then try refreshing this project and building it since it may be inconsistent
To overcome this problem, I need to stop the server, manually delete this file & then build & restart the server. Any idea why I am facing this issue?
I've experienced the issue in RAD 8.0, but not nearly as consistently as you. A second build attempt nearly always resolves the problem for me.
Although there are a number of references to this issue on the Eclipse bug tracking site, none of the bugs I've read have a definitive answer on the cause. There is some speculation that it may be due to a file handle leak. The problem appears to have begun around Eclipse version 3.6.1. I'm not sure exactly which Eclipse version RAD 7.5 is based on, but I believe it is 3.6.1 or later.
Does the issue only occur when the application is deployed and the server is running? I was wondering if you'd gotten the same results with the server shut down.
Unfortunately, the only concrete suggestions I can offer are to try refreshing the project frequently, and perhaps creating a new workspace -- its a bit of a hack, but a creating a fresh workspace has fixed a few really odd RAD issues I've encountered.
Here are a couple of the bug reports from the Eclipse bug tracking site:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309235
https://bugs.eclipse.org/bugs/show_bug.cgi?id=332607