« first day (2903 days earlier)      last day (130 days later) » 

12:01 AM
REFRESH!
[Minesweeper] 30 Games Played. 15 Bombs Used. 4371 Moves Performed. 5 New Users
[rubberduck-vba/Rubberduck] 2 issue comments
 
12:50 AM
 
 
16 hours later…
5:17 PM
> I can reproduce this on a fresh clone on a machine without MSOffice installation. We should really switch to explicitly referencing this as a nuget package. This seems to be tangentially related to #5969, the base issue seems to be that we're using a positively ancient version of Microsoft.Build.Framework and related.

This should be fixed by pulling the involved dependencies to an up to date version (i.e. 17.2.0 at time of writing) and updating the Rubberduck.Deployment.Build tasks accordin
 
@Duga welp... we seem to be using Microsoft.Build stuff from version 4 ...
@this I recall that you were the original author of these tasks. Any particular reason we were using those versions?
 
 
2 hours later…
7:26 PM
i'm one of the many users who, when they were updated (definitely not upgraded) to win11, noticed that References to Object libraries don't seem to be accepting references within the specific Reference (e.g., Microsoft Scripting Runtime). it appears that the 'fix' is to turn on and off each individual Reference in each module, for modules generated in previous versions of excel... i hate this so very, very much.

i have no where else to take that complaint...
 
7:45 PM
 
7:59 PM
lol @Cyril take the complaint to MS. I would do product feedback through the host application seeing that there may be no official place to complain about the VBE\VBA itself.
 
@HackSlash thanks
 
 
4 hours later…
11:46 PM
[rubberduck-vba/Rubberduck] 1585 stars vs. [decalage2/oletools] 2067 stars
 

« first day (2903 days earlier)      last day (130 days later) »