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.
Related
I recently reinstalled my Windows 10 OS, and now Nuget packages are "not compatible". After an explanation, I will be asking, how do I resolve this problem.
Lead up
Due to an unrelated problem, I had to reinstall my operating system. In the course of that, I reinstalled Visual Studio 2019. I cloned my repository (https://github.com/PaulSchrum/CogoDN), then opened it locally with VS.
Now when I build, I get several Nuget errors and warnings. These Nuget dependencies have been present in my code since December 2019, and never caused me a problem until this month (July 2020) associated with the reinstallation of VS.
Question: How do I resolve this problem?
Other Details
I am targeting .Net Core 3.1, but it happens no matter which version of .Net Core I target.
The main error seems to be of the pattern:
NU1202 Package System.Drawing.Common 4.5.0 is not compatible with netcoreapp3.1 (.NETCoreApp,Version=v3.1).
This is happening for System.Drawing.Common, netDxf.netstandard, and packages necessary for Microsoft Tests. Specifically, it can't recognize using Microsoft.VisualStudio.TestTools.UnitTesting; (namespace 'VisualStudio' does not exist), and every attribute ([TestClass], [TestMethod]) now is a syntax error.
What have I already tried
Various combinations of reestablishing the Nuget packages. This includes at least twice clearing the Nuget cache and installing the dependencies again. I also followed the advice here: https://stackoverflow.com/a/63108317/1339950 (Item 3) Close VS, Delete global NuGet.config, start VS and let it rebuild Nuget.config.
None of these work.
One last note: I have tried so many things and got into various different states of not working that my description may have inadvertently conflated a few details.
Visual Studio can't resolve Nuget dependencies after reinstalling
operating system
It is quite strange and in my side, I can also build the project without any errors.(I download the project from your github link and then open it with VS0219----build well).
So I think your Net Core SDK or VS IDE have broken.
1), please try to install the latest Net Core 3.1 Developer SDK.
Or you could open Programs and Features from Control Panel, then right-click on every net core sdk-->Change-->Repair
2) run sfc /scannow to scan your os and you can refer to this link for more steps.
3), try to do a repair in VS Installer. Or if your VS2019 is not the latest, please update it to the latest version.
4) try to create a new net core project and then install these nuget packages to check if the issue still persists.
I just upgraded to version 3.0.1 from nunit 2.6.4. It used to have a NUnit Gui Runner, located here:
After installing 3.0.1 (which I downloaded windows version from here)
I now no longer see the nunit.exe in the installation folder, for example the directory structure is different and appears to be missing many files that were part of the previous installation:
The NUnit team decided to make the GUI a separate product and will be releasing it separately. It is being rewritten from the ground up for NUnit 3, but hasn't been released yet. Development is happening on the GitHub page at https://github.com/nunit/nunit-gui if you want to get involved or track the progress. Initial releases will be out soon.
Update - There have been several preview releases of the new NUnit GUI that can be found at https://github.com/nunit/nunit-gui/releases. The previews are not recommended for production use, but they work and can be used.
The "final" release is here, you can find it at: https://github.com/TestCentric/testcentric-gui/releases
For anyone coming to this page, looking where to find the NUnit Gui, please note that on http://nunit.org/?p=download you can get version 2.6.4, which does contain the Gui.
UPDATE
As pointed out in the comments, a lot has changed since, and you should no longer use the 2.x version tools, rather use the new TestCentric UI found at https://github.com/TestCentric/testcentric-gui/releases
I'm currently using EF7 - beta4 and would like to use beta6. I know I'm playing with fire by using nightlies, but has anyone else done this and have been able to build after upgrading?
I've added the nightly nuget repository: https://www.myget.org/F/aspnetvnext/api/v2/ but when ever I upgrade a package it totally trashes all of .net in both DNX 4.5.1 and DNX Core 5. Now I'm not crazy enough to do this in a working project, so I'm testing this out in new empty mvc project and when I attempt to build I get in excess of 2000 errors from everything.
Has anyone else attempted this and if so how does one get around all the errors?
The nightly builds are highly unstable. Here are some pointers for working on the bleeding edge of ASP.NET.
Reset all packages. Sometimes nightly builds break other packages. Delete project.lock.json and delete all packages (~/.dnx/packages/). Reinstalling may help you get a coherent set.
Upgrade DNX. dnvm upgrade -u. This installs the latest, unstable version of DNX.
Submit issues. If it's breaking for you, it may not just be you.
Pay attention to the ASP.NET on GitHub. Nightly builds are usually only a few days behind the latest changes to the dev branch. We are working fast, and breaking things.
If stability is important, stick to the Nuget.org betas. Beta5 was just released yesterday, and has been more thoroughly vetted for stability.
Watch the Announcements repository to receive a heads-up on breaking changes.
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
I thought I'd give Helios a try, so I grabbed the latest Java EE install from http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/heliosr. Note, both OSX 32bit and 64bit exhibit the same symptoms.
So from a fresh install I run Helios (it launches fine), then the problem comes when I try running an upgrade. I keep getting these two errors errors:
Artifact not found: http://download.eclipse.org/releases/helios/compositeContent.jar.
http://download.eclipse.org/releases/helios/compositeContent.jar
No repository found at http://download.eclipse.org/releases/helios.
These are my (default) update sites:
Helios http://download.eclipse.org/releases/helios Enabled
Mylyn for Eclipse Helios http://download.eclipse.org/tools/mylyn/update/helios Enabled
The Eclipse Project Updates http://download.eclipse.org/eclipse/updates/3.6 Enabled
The Eclipse Web Tools Platform (WTP) software repository http://download.eclipse.org/webtools/repository/helios Enabled
http://download.eclipse.org/tools/mylyn/update/e3.4 Disabled
http://download.eclipse.org/tools/mylyn/update/extras Disabled
Note, I'm not behind any firewalls/proxies etc, no nothing weird with network connectivity.
I've searched all over the place and there are others with the same problem, with no solution that I could find.
Has anyone else run into these issues?
UPDATE 1:
Notes:
I'm not behind a proxy.
I've tried the Java EE, but also bare bones Eclipse 3.6.1.
I've tried different mirrors (including the main site),
I've tried SpingSource's version.
I've tried exporting the update sites to XML, deleting them and reimporting them.
I even tried adding forward slashes to the ends of site names.
I've made sure I have full write permissions for the eclipse folder, and have even placed it on my desktop.
I mention all of these seemingly odd behaviours because these are suggestions I've read around the web on this problem, which many people are having.
Once last interesting point I've just tried, is to download the "http://download.eclipse.org/releases/helios/compositeContent.jar" directly in the browser. It redirects to "http://www.gtlib.gatech.edu/pub/eclipse/releases/helios/compositeContent.jar" with a 403 forbidden. :\ It seems as though system is finding a mirror, but perhaps the mirror is broken? Also note, I'm in Australia, so Georgia Tech is nowhere near me ;)
Just as I was writing this, I tried one last idea. I discovered "Pulse" by Genuitec, which is a Eclipse install manager. I gave it a shot, and it worked. The site it uses for updates is:
"[url=http://eclipse.poweredbypulse.com/downloads/aux/eclipse-mirror/releases/helios] http://eclipse.poweredbypulse.com/downloads/aux/eclipse-mirr or/releases/helios[/url]"
So, I've wasted enough time on this now. I'd create a bug in Eclipse Bugzilla, but there are already entries with no solution.
UPDATE 2:
Ok, from a fresh install, if I disable:
http://download.eclipse.org/releases/helios/
and add Pulse's update site:
http://eclipse.poweredbypulse.com/downloads/aux/eclipse-mirror/releases/helios/
I don't get any errors. I really think it's to do with the automatic mirrored update site. Is this possible?
Here is a screenshot of my update sites now:
Regards,
Shane
Ok, I had the same issue on Windows XP 64bits laptop an Fresh Helios 64bits download, however your workaround works for me.
See update 2 in the question.
Shane