This is documentation from Moq site:
// out arguments
var outString = "ack";
// TryParse will return true, and the out argument will return "ack", lazy evaluated
mock.Setup(foo => foo.TryParse("ping", out outString)).Returns(true);
// ref arguments
var instance = new Bar();
// Only matches if ...
I just launched Despicable Me, so I have about 90 minutes to work on RD ..then I won't be able to touch my laptop until tonight. 1.3 today might be a stretch
Well... The high level SC view/presenter only really tell its children to refresh. I can get away without testing it right now. But this is a major hang up. The way things work right now, we will never be able to Moq the VBE. The only solution is either really screwing around with the way DockablePresenter works (bad) or write our own fakes (also bad).
Hmm in this case I can't persist it... the window caption is readonly and matches the target's name... wrapping it in a try..catch
else if (referenceCount > 1)
{
// if there's more than one reference, show the dockable reference navigation window:
try
{
ShowReferencesToolwindow(target);
}
catch (COMException)
{
// the exception is related to the docked control host instance,
// trying again will work (I know, that's bad bad bad code)
ShowReferencesToolwindow(target);
C:\Users\Christopher\Source\Repos\Rubberduck\RetailCoder.VBE\bin\Release\Rubberduck.tlb not found. An error occurred building the MsiFileHash table record for this file. Verify that the file exists in the specified location. ISEXP : error : -6271: File C:\Users\Christopher\Source\Repos\Rubberduck\RetailCoder.VBE\bin\Release\Rubberduck.tlb not found. An error occurred building the MsiFileHash table record for this file. Verify that the file exists in the specified location.
@RubberDuck I'll have to re-link the output folders... and then commit the installers: next release you build an installer for you'll have to redo this
IsDate("13.50") returns True but IsDate("12.25.2010") returns False
This is because IsDate could be more precisely named IsDateTime. And because the period (.) is treated as a time separator and not a date separator. See here for a full explanation.
This is documentation from Moq site:
// out arguments
var outString = "ack";
// TryParse will return true, and the out argument will return "ack", lazy evaluated
mock.Setup(foo => foo.TryParse("ping", out outString)).Returns(true);
// ref arguments
var instance = new Bar();
// Only matches if ...
IsDate("13.50") returns True but IsDate("12.25.2010") returns False
This is because IsDate could be more precisely named IsDateTime. And because the period (.) is treated as a time separator and not a date separator. See here for a full explanation.
VBA Rubberducking
VBA Rubberducking