« first day (1780 days earlier)      last day (94 days later) » 

12:01 AM
RELOAD!
[bruglesco/FleetCommand] 3 commits. 271 additions. 67 deletions.
[rubberduck-vba/Rubberduck] 17 commits. 1 opened issue. 1 closed issue. 5 issue comments. 4611 additions. 4160 deletions.
[Minesweeper] Games Played: 103, Bombs Used: 61, Moves Performed: 13425, New Users: 15
 
 
8 hours later…
7:34 AM
[rubberduck203/VBEX] wiky2 starred us
2
 
 
3 hours later…
10:55 AM
> Just discovered Rubberduck and tried out. First impression is very good, but it is very slow and hanging when using Code Inspection on an existing VBA Excel project with ~40 modules.
> @hugelsb could you tell us which version you're using exactly?

@pstiefel the latest prerelease includes the changes that might alleviate the issue a bit. Could I ask you to check your findings against the latest prerelease?
> Version 2.4.1.4674
OS: Microsoft Windows NT 10.0.17763.0, x64
Host Product: Microsoft Office 2013 x86
Host Version: 15.0.5101.1000
Host Executable: EXCEL.EXE
 
 
2 hours later…
1:22 PM
I have just puled the current next and now I am unable to build anymore.
Assets file 'N:\Repositories\Rubberduck\Rubberduck.JunkDrawer\obj\project.assets.json' not found. Run a NuGet package restore to generate this file.	Rubberduck.JunkDrawer
When I try to do a NuGet Refresh, I get the following:
Error occurred while restoring NuGet packages: '' is not a valid version string.
 
somehow I don't think the JunkDrawer was supposed to be a part of the next... ?
 
It is supposed to.
 
Oh ok.
 
At least, I think so.
 
@Vogel612 can confirm
 
1:26 PM
Several other assemblies reference it.
It is the root of all dependencies, actually.
However, it seems to be empty.
 
It only has the IExportable and StringExtensions in the Output
I'm thinking that if it's just something that's used everywhere, it probably can go into Resources instead of having yet another JunkDrawer
The name JunkDrawer made me think it was just a temporary thing
 
No, Resources has other dependencies.
I particular, Resources depends on the UI frameworks.
 
that can't be right - resources is one of the first project to build
 
Yes, but the resource framework is part of the UI frameworks.
 
1:54 PM
@PeterMTaylor looks very promising, would take some time to confirm. However, if we decided to target 4.8, we lose support for Vista.
Maybe not a problem - 0.55% market share... gs.statcounter.com/windows-version-market-share/desktop/…
 
TBH, I'd think those still on Vista has to be some kind of masochist.
I can understand staying behind on XP or 7. Vista? O_o
Alright, 9 more failing tests to go...
 
2:18 PM
> This support is leveraged by WPF to ensure that controls that are hosted under a native window can respond to DPI changes and update themselves. For e.g.- a WPF control hosted in a Windows Forms or a Win32 application that is manifested as Per Monitor V2 – will now be able to respond correctly to DPI changes and update itself.
 
2:53 PM
@this it wasn't though the name is supposed to imply it
 
 
 
1 hour later…
4:23 PM
I see I have the same problem :-) Just came here to report it.
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0006	Metadata file 'C:\Users\jverner\Desktop\RUBBERDUCK\Rubberduck.JunkDrawer\bin\Debug\net46\Rubberduck.JunkDrawer.dll' could not be found	Rubberduck.CodeAnalysis	C:\Users\jverner\Desktop\RUBBERDUCK\Rubberduck.CodeAnalysis\CSC	1	Active
one of many errors.
 
 
2 hours later…
6:23 PM
@SonGokussj4 The root cause is that JunkDrawer cannot load its NuGet packages. It is the root dependency. So all other builds fail because the dependencies are not there.
 
 
1 hour later…
7:50 PM
bah, tried to get SlimDucky building against Core 3 preview, failed. Looks like the tooling is not quite finished yet...
 
Yea. We should wait until Core 3 is out as a stable
 
yeah that was my conclusion too
Builds, but can't regasm yet
does look like COM activation is a big feature of 3 though :-)
 
sigh... ffs. The JunkDrawer project seems like it's bent on being a pain
 
so iiuc there's no reason we couldn't go to Core when its ready. Would lose Vista, but meh...
 
We could even multitarget
 
8:02 PM
true
 
also we have a big reason to opt into Core3
proper build support for XAML and Forms
 
ah yes, that pain...
 
i'm still annoyed at VS for throwing a hissy fit at my JunkDrawer and the utter incapability to deal with custom UserControls
 
 
2 hours later…
10:10 PM
~sigh
> assembly can be omitted if the clr-namespace referenced is being defined within the same assembly as the application code that is referencing the custom classes. Or, an equivalent syntax for this case is to specify assembly=, with no string token following the equals sign
yet... VS is throwing a hissy fit
 
10:50 PM
@MathieuGuindon is losing Vista a big concern?
 
@mansellan isn't it dead?
 
Well yes, but dropping support for anything is suboptimal...
 
Don't forget that there are corporate environments that simply do not update the .net framework.
 
Yeah, should be avoided if we can help it
gotta run
 
@M.Doerner true...
or at least, not without a review process lasting months / years
 

« first day (1780 days earlier)      last day (94 days later) »