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
multiple opened projects named VBProject will break the fully-qualified method calls #1
Labels
Milestone
Comments
retailcoder
added
status-declined
This will not be implemented.
bug
Identifies work items for known bugs
and removed
status-declined
This will not be implemented.
labels
Nov 6, 2014
Won't fix - there is no way to avoid these name clashes. The exception should be handled though. |
rubberduck203
added
status-declined
This will not be implemented.
bug
Identifies work items for known bugs
and removed
bug
Identifies work items for known bugs
labels
Nov 11, 2014
retailcoder
added a commit
that referenced
this issue
Nov 12, 2014
Hosch250
added a commit
that referenced
this issue
May 14, 2015
Hosch250
added a commit
that referenced
this issue
May 18, 2015
Hosch250
added a commit
that referenced
this issue
Jun 11, 2015
retailcoder
pushed a commit
that referenced
this issue
Sep 27, 2015
retailcoder
pushed a commit
that referenced
this issue
Sep 3, 2016
Fix for #2177: Crashes Excel.exe on start up of VBA Editor
retailcoder
pushed a commit
that referenced
this issue
Dec 14, 2016
Cleaned up == and != operator methods
This was referenced Mar 30, 2018
Closed
Merged
bclothier
pushed a commit
that referenced
this issue
Jan 3, 2019
Update local fork with rubberduck changes
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Test methods are called with a fully-qualified syntax
ProjectName.ModuleName.TestMethodName
- however if there are two or more projects with the same name, VBA will not be able to resolve the method call and an exception will be thrown.If the test method is added from the Test Explorer, an exception will be thrown when an existing TestMethod (
ProjectName.ModuleName.TestMethodName
) is added to the session.The text was updated successfully, but these errors were encountered: