Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem with WPF images rendering #55

Open
cpyrgas opened this issue Jun 17, 2019 · 2 comments
Open

Problem with WPF images rendering #55

cpyrgas opened this issue Jun 17, 2019 · 2 comments
Assignees
@RobertvanderHulst
Labels
bug vs form editor vs projectsystem

Comments

@cpyrgas
Copy link

cpyrgas commented Jun 17, 2019

I have a problem on wpf images rendering. When I try to add an image to a ribbon toolbar in wpf the compiler can't find the image in the path and in the resource file and the compiler return me an error "Resource not found". The same solution written in c# works perfectly.

Thank you in advance.

Raffaele.

Ps: In attach the solution
ICP.zip
@cpyrgas cpyrgas added this to To do in VsIntegration via automation Jun 17, 2019
@RobertvanderHulst RobertvanderHulst added this to the 2.1 and later milestone Jun 27, 2019
@RobertvanderHulst RobertvanderHulst modified the milestones: 2.1 and later, 2.2 and Later Jul 14, 2019
@RobertvanderHulst RobertvanderHulst modified the milestones: 2.2 , November 2019 Nov 18, 2019
@RobertvanderHulst RobertvanderHulst modified the milestones: April 2020, May 2020 May 2, 2020
@RobertvanderHulst RobertvanderHulst modified the milestones: May 2020, June 2020 Jun 5, 2020
@RobertvanderHulst RobertvanderHulst added this to To do in Later Apr 8, 2021
@RobertvanderHulst RobertvanderHulst removed this from the August 2020 milestone Apr 8, 2021
@RobertvanderHulst RobertvanderHulst added this to To do in June 2021 May 28, 2021
@RobertvanderHulst RobertvanderHulst removed this from To do in June 2021 Jun 22, 2021
@RobertvanderHulst RobertvanderHulst removed this from To do in Later Dec 6, 2021
@RobertvanderHulst RobertvanderHulst removed this from To do in VsIntegration Jan 12, 2022
@RobertvanderHulst
Copy link
Member

I cannot reproduce this in the current build

@RobertvanderHulst RobertvanderHulst added this to To do in Build 2.14 via automation Nov 10, 2022
@RobertvanderHulst RobertvanderHulst added this to the X# 2.14 milestone Nov 10, 2022
@RobertvanderHulst RobertvanderHulst moved this from To do to Needs Testing in Build 2.14 Nov 10, 2022
@cpyrgas
Copy link
Author

cpyrgas commented Nov 10, 2022

Robert, apparently this is a runtime problem, not a compile time one. I'm on the 2.13 VS integration, but when I try to rebuild and run the app, I get a runtime error: System.Windows.Markup.XamlParseException: ''Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception.' Line number '17' and line position '18'.'

Also I tried editing the MainWindow.xaml directly in the editor, but even after making only a dummy change, the moment I hit Save, VS freezes forever. HAppens in both VS2017 and VS2019

@cpyrgas cpyrgas moved this from Needs Testing to In progress in Build 2.14 Nov 10, 2022
@cpyrgas cpyrgas moved this from In progress to To do in Build 2.14 Nov 10, 2022
@RobertvanderHulst RobertvanderHulst self-assigned this Nov 11, 2022
@RobertvanderHulst RobertvanderHulst removed this from To do in Build 2.14 Nov 16, 2022
@RobertvanderHulst RobertvanderHulst removed this from the X# 2.14 milestone Nov 16, 2022
RobertvanderHulst added a commit that referenced this issue Aug 21, 2023
@RobertvanderHulst
Feature/x sharp compiler (#55)
80144f1 
* [Compiler tests] Adjusted tests for #1187 and #1191

* [Compiler tests] Added C877 and adjusted R882 for #1184

* [Compiler tests] Added C878 for #1194 (and missing C877 from previous commit)

* [Common] Fixes #/issues/1194

* WIP on StackAlloc, debugger sequence points and line numbers in error messages

* [Compiler tests] Added test C879 for #1195

* [Compiler] Switch to .Net Analyzers version 7.0.0

* [Compiler] Fixes #/issues/1195
Adjust overload resolution to only use our "logic" when:
- functions are involved
- our types are involved
- param is passed by reference
- argument is enum

* [Compiler] Suppress error messages about updated NetAnalyzers. Also suppress NetAnalyzer all together for X# code

* [Tests] Fixed one more test

* Fixes #/issues/1184, C877 and R882

* [Tests] SUM command has been fixed in the header file

* [Compiler] Fixes #/issues/1084

* [Tests] Added test for Stackalloc keyword

* [Compiler] A predicate prevents STACKALLOC(123) from being parsed as STACKALLOC followed by a paren expression

* [Compiler] Fixes #/issues/1166, issue number 1

* [Compiler] Fixes #/issues/1109

* [Tests] Added pragma to several tests to suppress messages about missing REF or OUT modifiers for parameters

* [tests] Changed incorrect '.' operators to ':' in two tests

* [tests] Updated STACKALLOC test to use STACKALLOC as an identifier for a local

* [tests] Set compiler profile to debug tests

Co-authored-by: cpyrgas <chris@xsharp.eu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RobertvanderHulst RobertvanderHulst

Labels
bug vs form editor vs projectsystem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RobertvanderHulst @cpyrgas