-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'uWindowCapture' could not be found (are you missing a using directive or an assembly reference?) #41
Comments
I don't know if perhaps this is due to duplicate assembly names where the plugins are named uWindowCapture and the ASDF file in Runtime folder is also named uWindowCapture. I notice in the uDesktopDuplication package, you have named the ASDF in the runtime folder uDesktopDuplication.Runtime Perhaps renaming the ASDF to uWindowCapture.Runtime will fix it, but I cannot do that as it's part of the package. |
@hecomi Can you confirm this issue isn't something on my end? I will take suggestions if you have any. |
Hi @hecomi , Same for the Samples. I have to set Auto Referenced to True and re-import, then I am able to reference the public methods. Did you not want the asmdef file for uWindowCapture to be auto referenced? I notice uDesktopDuplication asmdef file has auto referenced set to True. I had no problem with that package regarding the references. What is the difference between the 2 packages regarding references? Edit: Just FYI - If I just set Auto Referenced to True and re-import, this solves the issue. Don't need to checkmark added for RegistryPackages. |
Thanks for the report, it is a mistake that |
This problem was fixed in v1.1.2:
|
Hello, I added uWindowCapture package via UPM git url. I'm wanting to reference the classes from the uWindowCapture namespace in my own scripts but after adding the #using uWindowCapture; I'm getting the following error:
error CS0246: The type or namespace name 'uWindowCapture' could not be found (are you missing a using directive or an assembly reference?)
The text was updated successfully, but these errors were encountered: