@IvenBach don't make me cite that thing...

@M.Doerner well, poop. So it's not necessarily just the VS edition at fault.

I am currently at 15.8.1.

I think Iven is a bit later than that.

Mine is 15.8.8

@IvenBach Do you have R# installed?

Not on my work box.

whats R#?

Resharper.

Resharper

ah

that one tool

RE: C#'s RD

i was like... yet another programming lang?

jeez

everything has # after it now...

If you do not have it on the work machine, updating it will probably not help.

just imagine a world where... VB#

Hm, then R# would be an enhanced version of R, which is a language I really do not like, btw.

Way too helpful.

so the branch you guys cant compile is the Next branch, correcT?

I can't compile anything related to Rubberduck.

And everybody else seems to be able to compile.

odd. when im trying to compile the next branch it complains about missing dll files

@KySoto What message output do you get?

i did a clean

and im rebuilding

1>------ Build started: Project: RubberduckCodeAnalysis, Configuration: Release Any CPU ------
1>C:\Users\MMyers\Source\Repos\Rubberduck\RubberduckBaseProject.csproj : warning MSB4011: "C:\Program Files\dotnet\sdk\2.1.403\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props" cannot be imported again. It was already imported at "C:\Users\MMyers\Source\Repos\Rubberduck\RubberduckCodeAnalysis\RubberduckCodeAnalysis.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
1>C:\Users\MMyers\Source\Repos\Rubberduck\RubberduckCodeAnalysis\RubberduckCodeAnalysis.csproj : warnin…

its entirely possible im just dumb and dont have the project properly configured

That's looking like the same errors I'm getting.

@KySoto Don't use rebuild. Clean, then build.

i didnt.

@KySoto Your actual error is the following:

or i should say, i did the thing you said to do

13>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFx.targets(419,45): error MSB4057: The target "CoreCompile" does not exist in the project.

so almost 100% likely that its a config issue on my part hten?

**then

that error message has to do with how WPF is compiled IIRC

oh, so its the same issue everyone else is having then?

For some values of "everyone".

I probably do not get it, because I still have some working version in my obj folder.

the issue is that this isn't sunburst

so for someone with no prior git repo, it might not build at all

For KySoto to test, I think he has to pull from comintern's PR

@MathieuGuindon I just opened the About window: is the attribution to LibGit2Sharp still appropriate?

oh gee...

no it's not. SC is gone

Thought so.

welll... that makes me sad

since i have 11 minutes

and therefor not enough time to put any real effort into this

@all in regards to the feature freeze, I think we should merge the PRs that should be in 2.3 sooner than later. I'm thinking that the #4465 and later are all good to be merged... Thoughts?

put some "Review requested" labels on them and I can give them a thorough look tomorrow

I'm biased in making sure Suburst SDK gets merged, once it's known to resolve the build issues.

I need to figure out the permissive assert class at some point...

Yes, the trouble is that we don't have good evidence that sunburst will make things worse. IMPOV, it seems to help but just not for you.

Permissive assert probably won't make it for 2.3

Heck, refactoring dialog refactor won't, either. :\ My fault, though.

It'll make it for 3.0 though.

Oh yeah

[rubberduck-vba/Rubberduck] bclothier added label PR-Status: Review Requested to pull request #4487: Use image via resource

[rubberduck-vba/Rubberduck] bclothier added label PR-Status: Review Requested to pull request #4488: Add new inspection for Excel UDFs hidden by cells.

[rubberduck-vba/Rubberduck] bclothier added label PR-Status: Review Requested to pull request #4491: Clean COM wrappers leak: Round 2

@Vogel612 done.

hmm weird.

thanks :)

Duga didn't catch them all

she may have hit the rate-limit

[rubberduck-vba/Rubberduck] bclothier added label PR-Status: Review Requested to pull request #4501: Switch to Sunburst SDK build

[rubberduck-vba/Rubberduck] IvenBach commented on Rubberduck.Core/UI/Refactorings/ReorderParameters/ReorderParametersView.xaml of pull request #4487: Use image via resource

yeah, those are the 2 missing. Good.

Small beneficial updates in each PR will add up over time.

The sunburst PR does fix a number of problems with the WPF code though

TTGH

TTGTB

the way i see, it can't hurt to post an issue @ sunburst GH describing Iven's situation. It might not be anything to do with sunburst. It might be. We're all basically shooting in dark and I don't like that one bit.

What has me stumped is that we can both build just fine.

I know, I know, I know

and that bothers the snot out of me.

> Look at me I'm shooting blanks! :pause: Or is that shooting in the dark?

shooting blanks in the dark and killing people at it

WPF doesn't cache outside the build directory, does it?

I hope not....

That's the only thing I could come up with it being.

that would be horrid

^

Otherwise if everything is contained within the directory nuking should have fixed the problem.

hmm. but nugets are now....

they're now in appdata

And to be clear, you can't do a clean pull of next from my branch, nothing else, and build?

could that be why?

maybe he needs to nuke the nuget cache....

Hmmm... possibly. It is always caching.

@Comintern I can't do a clean pull off anything and build.

cool. I got a hacktoberfest tshirt even though I didn't quite get the 5 PR mark

:+1: vogel.

I'm hoping to get mine. I confirmed my size a while back.

I think mine mailed yesterday.

I just got an email today, soo ..

They were having build issues.

that said: I think the nuget cache should not impact the build in that way

a full package restore might be useful to rule it out just in case, but I'm pretty sure it's not NuGet

Yeah, I can't think of a package that should make a difference.

obtw: @this did you verify fakes work?

IIRC you found there was an issue with EasyHooks...