« first day (2994 days earlier)      last day (186 days later) » 

12:03 AM
REFRESH!
[Minesweeper] 100 Games Played. 59 Bombs Used. 13866 Moves Performed. 9 New Users
[Zomis/Games] 51 additions. 17 deletions. 2 commits
 
 
6 hours later…
 
7 hours later…
1:24 PM
In testing a like-for-like file removal, explorer appears to delete 3.1 files per second (including time to scan/analyze files prior to actual deletion)... the powershell remove-item appears to remove 2.4 files per second from initiating code.
I ran both simultaneously, so unsure if that has an impact (n=1)
 
 
2 hours later…
3:47 PM
@Duga I recognize that username
 
4:02 PM
So, I have officially given up on getting my stupid virtual machines to work properly (HDD usage stuck at 100% is cripplingly unworkable) and bought a new laptop, which I'm in the middle of setting up. Got VS2022 installed and RD cloned, trying to retarget everything to Framework 4.8 and hitting issues with olewoo, but all projects (except . Deployment) are building fine at this point.
2
 
yay for new hardware
 
=)
Also I've created a Rubberduck3 private repo to get the ball rolling on that; I started it off an empty solution and slowly bring in the RD foundations piece by piece (no .Deployment project yet) and it's going well so far, but I'm worried about losing the git history and I think v3 might be feasible after all, off a separate branch in the current repo
I've also resumed work on the website project; the Bootstrap stuff is fixed but I messed up the xmldoc parsing service so that's where I need to put my attention now, because the details pages look like a bad regression right now.
The VersionCheck service in v3 is no longer hitting the website front-end; instead it gets actual tag metadata from the back-end API, which is actually already live: api.rubberduckvba.com/api/v1/public/tags
This API can also serve the feature content (that's how the website gets it), so in the future RD could request the "user manual" for any given feature or sub-feature
 
4:35 PM
Anyway the v3 repo at this point is just a do-nothing VBIDE add-in that can load RD settings and hook up the VBE (the Parsing assembly and everything that touches any of it, isn't there), the idea was just to get an empty shell add-in and make the Avalon editor happen.
2
#AvalonMentions++
 
 
2 hours later…
6:21 PM
ok so, uh, well, this is annoying.
 
> I figuered out some more cases. Looks like a combination of Colon and some Keywords that Trigger indent/outdent.
```
Sub foo()
' : loop
' bar
End Sub
```

```
Sub foo1()
' : next
' bar
End Sub
```

```
Sub foo2()
' : while
' bar
End Sub
```
> Looks like the indenter isn't consistently tracking when it's inside a comment.
 
6:47 PM
Ugh, why does it need this interop assembly anyway...
 
 
3 hours later…
9:31 PM
 
10:29 PM
 
11:22 PM
Rubberduck.Deployment.Build failing to build in VS2022 basically means we're either stuck with VS2019 (2017?) or back to manual release and add-in registration, but why did we need to build the .tlb ourselves again?
IIRC it was about adding special attributes we couldn't add otherwise, to hide some types for a cleaner API, but functionally it wouldn't break anything to flip back to manual, yeah?
 
@MathieuGuindon I'm not sure what you're doing with the tlb files but according to @bclothier you don't need that in the .NET4, he cites as his evidence... RubberDuck source. So this might be a problem that has already been solved. github.com/leibnitz27/olewoo/issues/11
 
11:48 PM
[rubberduck-vba/Rubberduck] 1628 stars vs. [decalage2/oletools] 2165 stars
 

« first day (2994 days earlier)      last day (186 days later) »