RELOAD!

[rubberduck-vba/Rubberduck] 3 issue comments.

[Zomis/Games] 1 commit. 1 issue comment. 1 addition. 1 deletion.

[Minesweeper] New Users: 17, Games Played: 112, Bombs Used: 62, Moves Performed: 13727

@IvenBach FWIW, I have replicated what you are experiencing. But, if I add the new .resx file directly under Rubberduck.Core and NOT in a subfolder of Rubberduck.Core - the build succeeds. Unfortunately, I do not know what this means, but maybe it can be a piece of useful info to someone who does.

That's the behavior I had too. Documented it because it is a big bowl of makes-no-sense.

@IvenBach @BZngr sounds like a particular quirk with name resolution

That's why I tested with naming the file differently and testing different subfolders.

[rubberduck-vba/Rubberduck] Denvernoell starred us

@IvenBach Here's a path the allows the compile to succeed. Others can comment on whether or not it is valid.

After inserting the new resource file in Rubberduck.Core, try to compile...it will fail (as we know). Open Rubberduck.Core.csproj find and comment out this EmbeddedResource element:

There is another EmbeddedResource element in the .csproj file that relates to the resx file you just added.

@IvenBach lol I carved 2 eyes and called it a pumpkin, should have started it last week

[rubberduck203/VBEX] pawelsadlo2 starred us

@BZngr Commenting out both does not build.

I can change the Build Action property of FooBarUI.resx from Embedded resource --> Content and it builds. Need to test how that works now.

@IvenBach only comment out the one EnbeddedResource shown in my message...not ‘both’.

When I add the *.resx file the following lines are added to Rubberduck.Core.csproj

<Compile Update="UI\Inspections\InspectionResultsUI.Designer.cs">
  <DesignTime>True</DesignTime>
  <AutoGen>True</AutoGen>
  <DependentUpon>InspectionResultsUI.resx</DependentUpon>
</Compile>

<EmbeddedResource Update="UI\Inspections\InspectionResultsUI.resx">
  <Generator>ResXFileCodeGenerator</Generator>
  <LastGenOutput>InspectionResultsUI.Designer.cs</LastGenOutput>
</EmbeddedResource>

I note that they are different than your example you posted.

Commented it out. Build failed.

I am out of WTF to give at this point.

The part to comment out (In my message) is near the top of the .csproj file. (I am not showing the entire file) The xml in your message IS added to the .csproj when you add the .resx and attempt to compile and should remain as-is. Sorry, I am away from my machine so I am going off memory at this point.

I completely misunderstood your post.

Did not realize you meant it to be literal.

Commenting that line out does allow it to compile.

Later tonight I'll try adding resource strings and using them.

I'll have to thing about this but those 3 lines of code don't make any sense as to why they are added.

Glad it now compiles...I think the added lines is what points the compiler to the newly inserted .resx and associated .cs file. Not finding the .cs file was cause of the previous build failures.

[rubberduck-vba/Rubberduck] VB6Hobbyst7 starred us

[rubberduck-vba/Rubberduck] VB6Hobbyst7 forked us into VB6Hobbyst7/Rubberduck