Severity Code Description Project File Line Suppression State
Error Custom tool PublicResXFileCodeGenerator failed to produce an output for input file 'CodeExplorer\CodeExplorerUI.de.resx' but did not log a specific error. Rubberduck.Resources C:\Users\cpaustell\Source\Repos\Rubberduck\Rubberduck.Resources\CodeExplorer\CodeExplorerUI.de.resx 1
Error MC4003 Cannot resolve the Style Property 'FixScrolling'. Verify that the owning type is the Style's TargetType, or use Class.Property syntax to specify the Property. Line 49 Position 25. Rubberduck.Core C:\Users\cpaustell\Source\Repos\Rubberduc…
1>------ Build started: Project: RubberduckCodeAnalysis, Configuration: Release Any CPU ------
1>C:\Users\cpaustell\Source\Repos\Rubberduck\RubberduckBaseProject.csproj : warning MSB4011: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props" cannot be imported again. It was already imported at "C:\Users\cpaustell\Source\Repos\Rubberduck\RubberduckCodeAnalysis\RubberduckCodeAnalysis.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
@this Still failed even with pulling from comintern next to make sure it's up to date.
1>------ Build started: Project: RubberduckCodeAnalysis, Configuration: Release Any CPU ------
1>C:\Users\cpaustell\Source\Repos\Rubberduck\RubberduckBaseProject.csproj : warning MSB4011: "C:\Users\cpaustell\.nuget\packages\sunburst.net.sdk.wpf\1.0.47\Sdk\Sdk.props" cannot be imported again. It was already imported at "C:\Users\cpaustell\Source\Repos\Rubberduck\RubberduckCodeAnalysis\RubberduckCodeAnalysis.csproj". This is most likely a build authoring error. This subsequent import will be ignored.
> 13>C:\Users\cpaustell\Source\Repos\Rubberduck\Rubberduck.Core\UI\Settings\AutoCompleteSettings.xaml(49,25): error MC4003: Cannot resolve the Style Property 'FixScrolling'. Verify that the owning type is the Style's TargetType, or use Class.Property syntax to specify the Property. Line 49 Position 25.
that's the only error of its kind. That might be something to fix, but what do I know RE: WPF.
Again, I know nothing about WPF. I only point that out because it's only error of its kind and last night Mat/Com was talking about a missing DP of something
@IvenBach OK, so maybe this is my own ignorance of WPF showing here, but doesn't ScrollViewerCorrector need an instance property for FixScrolling to bind to?
I mean, if businesses encouraged people to use the right tool, it might help people learn instead of just sticking with what they are told to use and always doing it wrong.
Basically, instead of the business owning the app, the outsourcer is the product owner, with the agreement that the client gets everything back if they go under.
I'd rather "add a little bit of complexity" than see the follow up question about why looping over an array gives an extra iteration. If explaining how to properly size an array is "difficult for a new user", then how do you explain that one? Or the "complexity" of writing type safe code? It's never too early to learn fundamentals. — Comintern6 secs ago
I f'n hate that attitude toward dumbing things down. What a paternalistic POS.
Duck check: In XAML as part of the UserControl attributes where xmlns:foo="clr-namespace:Rubberduck.Bar.Duk" what are the valid things that can be used? Is it just .cs files?
You specify which namespace it's coming from converters and the class BindingModeToTextConverter. Thereafter within the XAML file you refer to it by the key BindingModeToText.
Coders log:
Checking out a different branch is causing VS to barf-n-crash.
Symptoms are worsening.
Preparing for the inevitable nuclear winter that's approaching.
Hoarding supplies for now.
Right, but when you sync your branch, it's trying to sync something that isn't committed yet. Curious what that looks like in a branch visualization...
Nuked from orbit. Brand new directory with git clone ... branch. Open VS and watch dependencies go from yellow triangles to good as NuGet restored them via automagic. Attempt to build has an instant failure.
my guess is that something went wrong with a git pull and/or conflict resolution, the wrong file was kept or discarded, and there's a merge commit in the tree somewhere that shouldn't be there
VBA Rubberducking
VBA Rubberducking