You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.
When we notice we didn't add required packages to the project after we wrote some missing types on the file, we add those packages to the project, then go back to editor and try to fix missing type issue either by adding "using" directive or resolve it to full name. However monodevelop cannot resolve the type even after we add references via package.
Repro:
Create a new console project.
Add [TestFixture] to the MainClass declaration. It won't resolve to anything (expected). Keep the editor page open.
Open packages dialog and add "NUnit". It will automatically add nunit.framework.dll to
8000
the references.
Move cursor onto TestFixture, open context menu, and select Quick Fix.
Expected results: it should show using NUnit.Framework;
Actual results: it does not show the resolution candidates.
The TestFixture attribute still has an error marker even after the using statement has been added. Closing and re-opening Program.cs fixes that. This might be the same as Red squiggles have a tendency to stick around #3858
The quick fix menu shows 'Using NUnit.Framework' twice.
When we notice we didn't add required packages to the project after we wrote some missing types on the file, we add those packages to the project, then go back to editor and try to fix missing type issue either by adding "using" directive or resolve it to full name. However monodevelop cannot resolve the type even after we add references via package.
Repro:
TestFixture
, open context menu, and select Quick Fix.Expected results: it should show
using NUnit.Framework;
Actual results: it does not show the resolution candidates.
Using monodevelop 036b03b.
The text was updated successfully, but these errors were encountered: