« first day (1996 days earlier)      last day (21 days later) » 

12:00 AM
Should that be? I'd expect with the other modules being deleted with Replace that would also be the same for document modules.
 
We could change the replace command to clear the code behind of all document modules.
 
RELOAD!
[rubberduck-vba/Rubberduck] 3 opened issues. 13 issue comments.
[Minesweeper] Games Played: 110, Bombs Used: 71, Moves Performed: 13914, New Users: 19
 
@IvenBach document modules belong to the host, not the VBIDE
 
Where do the standard and class modules belong? The VBIDE?
These are things I'm just starting to understand.
 
Well, the project anyway
 
12:03 AM
But what about the code behinds of the document modules?
 
I'd expect them to be overwritten based on the component name
(and warned if attributes are to be lost)
@IvenBach only the host app knows how to add or remove document modules
 
What should the replace command do with the documents for which no file has been provided?
 
leave them alone, I suppose
 
Should it clear them?
 
nah, uselessly destructive
 
12:07 AM
^^ That's the behavior I'd expect.
Having one set of behavior for .bas and .cls when choosing replace and another for .doccls doesn't feel right.
 
They're fundamentally different and simply can't be handled the same way
so, if you want to use SC for VBA, put as little code as possible in doc modules
and that's it, I'm blogging about this
 
Because of those differences making a proxy for them is the preferred alternative?
I have several sheets multiple properties and importing them individually will be a chore.
Mines Excel specific though as that's all I use.
@MathieuGuindon Already looking forward to the article sensei.
 
~.~
 
In other news, rubberduckvba.com apparently fits on a single floppy disk
 
12:22 AM
Tweet about it.
> What can your devs do for you? We can fit XX number of code inspections and a duck on a floppy.
 
12:59 AM
@MathieuGuindon FWIW, I don't feel the same way with Access documents but that's only because it already has the SC support present so it's easy enough to SC them compared to an Excel worksheet, and it can implement interfaces to which I've used to good effect.
IDK if there's other hosts, but I think Access is likely the only one host to have that support.
 
@this oh I'm definitely only talking about Excel here - other hosts, other rules!
One thing Sage300 did right: no document modules!
 
I do wonder how many sets of rules there are.
 
200-some, IIRC
 
one per host? Yeah, I guess that'd be the case.
 
Ok, I have moved most of the checks to the ImportCommand now.
Now, I just have to write a million tests to cover the new functionality.
 
1:03 AM
lol
 
I guess it also depends on what the document it is. Excel spreadsheet don't really lead itself well to reusable component the same way a form would, I guess.
 
Well, and Ishould review the user notifications and align the resource keys to the new location.
 
@M.Doerner that's the easy part, right? ;-)
 
which part, the resources?
 
The tests. That was me being facetious.
 
1:08 AM
I actually just have to port and adapt the correct tests for the UpdateFromFilesCommens.
 
And I bet you didn't even bother clicking that link I gave you. smh. — Mathieu Guindon 56 secs ago
the entitlement is strong with this one
 
It's just annoying work.
 
@FreeMan wait, wut? sensible countries drive on the left ;-)
@M.Doerner that, I don't know. I suspect it ignores the change, like it ignores source file changes. VB6 is from an era before external changes, before multi-dev considerations. I'll check and get back to you.
There's also .vbg files to consider (the predecessor to .sln, and vastly inferior)
 
1:24 AM
@mansellan IIRC VB6 Enterprise shipped with VSS (gasp)
Wut wait a minute why how did I not ever know about .vbg?!!
 
@MathieuGuindon True. But until vary late (VSS 2005), the only sharing in VSS was "I've got this file, everyone else wait"
 
lol yeah
 
Lock-Edit-Commit
 
well it's safe
 
VS2005 introduced Edit-Resolve-Commit, but too late for anyone to care.
About 7 years after MS stopped caring about classic VB
@MathieuGuindon Because it solved almost nothing?
(speaking as someone who had one in a business setting, and was disappointed)
 
1:33 AM
IDK, does it make multiple .vbp in the PE?
@mansellan what does/doesn't it do?
I mean, I worked with .vbp and ..yeah. makes me wonder what could possibly have gone wrong with .vbg...
 
Sure, it's like Excel, multiple projects in the PE. The vbg puts them into a group. But it's not like modern VS... Everything has to be done via COM, you can't treat it like sorta-one-big-project.
It's difficult to explain... Same idea, more sucky.
It basically got you nothing much above "load project 1". "Compile to dll." "load project 2"". "Reference project1.dll".
I know that's kinda what VS does. But it wasn't the same.
 
1998 was tough =)
 
2:08 AM
Thing is, VSS became TFS. They moved the storage to SQL, added some niceties, and hoped nobody would notice.
 
2:19 AM
it checks out
 
TFS was just a rebranding exercise. VSS2008 didn't sound so good.
 
did VSS live that long?
I'd thought it dead in the "VS.NET" era
 
It lived on in TFVC. Which MS have now accepted is now dead, they're full-on with Git in Azure DevOps.
 
Azure sounds nice
 
It's actually difficult to kill TFVC repos in Azure DevOps. It's still the default.
 
2:28 AM
yikes
 
@MathieuGuindon Azure DevOps is really nice.
It kinda just works.
 
2:41 AM
Huh? No
It has been defaulting to git for a good while
At least when I make new project, I don't have to do anything - it just has git OOB
TFS (aka VS' VSS) can burn in a tire fire.
 
 
4 hours later…
6:45 AM
VSS = ???
 
 
4 hours later…
10:54 AM
Visual source safe
MS's bad ancient take on SC.
I think DevOps is a not too bad, but a bit lacking in some areas.
In particular the diff view is inferior to GitHub's.
 
11:12 AM
 
 
8 hours later…
8:05 PM
Should we really overwrite the contents of forms without binary and documents on import or should the import command be guaranteed to be non-destructive?
 
 
1 hour later…
9:24 PM
Currently, if there is an exception withing an action executed under parser suspension, we swallow the exception and return that there was an unexpected error as suspension result.
I think that this is very unexpected behaviour.
Shouldn't we let the exception bubble up?
At least, we have to report the exception on the result, which is something I will add anyway.
Argh! MS, why do you have to do stuff so inconsistently?
The type returned from Dictionary<TKey, TValue>.Values implements ICollection<TValue>, which contains Remove(TValue item), but invoking that member causes an exception.
Either don't put Remove on the interface of don't say that the type implements the interface!
 
9:42 PM
> Now, most of the checks introduces for UpdateFromFilesCommand are executed for all import commands. We check that the component names for the files are unique (Otherwise the import is non-deterministic since the VBE numbers the later imported components and the order cannot be determined by the user.), we check that binary files are present (VBA only) and if they are not abort unless there is a different import path into existing modules (currently for user forms). In this case we check whe
 
10:10 PM
[rubberduck-vba/Rubberduck] build for commit 93028391 on unknown branch: AppVeyor build succeeded
 
@MathieuGuindon That makes no sense whatsoever! What does "cows circulating on the other side of the road" even mean???
 
@this "standard gauge" railroad width was determined by the width of a Roman Centurion's chariot. The Romans built their roads to fit their chariots. The locals they dominated build their wagons to work on those nice stone roads. The rest, as they say, is history...
yesterday, by Mathieu Guindon
also there was a crisis in beef prices (don't recall when or where) when the "correct" side was changed from left to right, because farmers had to kill all the animals since they couldn't re-train them to circulate on the other side of the road, so there was a sudden peak in beef offering
catching up on yesterday afternoon
 
> The problem here arises because we never set the dialog result if the dialog is closed not using the button. This causes the observed behaviour since the first element of the results enum is Execute. This can be fixed by either making Cancel the first element or adding a third value Undetermined as the first value.
 
10:25 PM
Not good, after cancelling a rename refactoring I consistently get a restart of Excel after close.
 
10:43 PM
Hm, the problem only occurs if the dialog is cancelled.
 

« first day (1996 days earlier)      last day (21 days later) »