You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks for this great tool and its Visual Studio integration.
I love it, ever since I discovered it some months ago 👍
For me it worked like a charm until I tried to add some XAML-files to my Xamarin.Forms project, which have no code behind-files.
By definition I do need to declare the <?xaml-comp compile="true" ?> node at the top of the file, but unfortunately this line changes on save to <?Mapping compile="true" ?>, if the XAML Styler extension is activated in my Visual Studio 2017 Enterprise IDE .
I tried to find a configuration or a "ignore-list" to avoid automatically "excluding" my XAMLs from compilation - but without success.
Does this happen on purpose or is this just a bug?
I honestly do not understand the <?Mapping compile="true" ?> line at all - perhaps because of my bad searching skills? - so I don't want to blame your great tool, because of some missing knowledge here.
Anyway this could be some unwanted behaviour and I really want to reactivate XAML Styler in my projects 😉
It would be great, if you could have a look at this and let me know what the problem is/could be 👍
Hmm, interesting. This appears to be a bug affecting Xamarin.
I tried to find a configuration or a "ignore-list" to avoid automatically "excluding" my XAMLs from compilation - but without success.
This is not currently possible, but it is on our backlog (#9 and #44). Even if this were available as a workaround, I think we would still want to address the underlying issue here IRT <?xaml-comp compile="true" ?>.
Perhaps I have some spare time around the upcoming holidays to dive a bit more into the structure of this project to prepare a "possible fix"-PR :-) 🥚 🐰
grochocki
changed the title
XML processing instructions changed automatically
XML processing instructions changed automatically (Xamarin)
Sep 23, 2019
…avalon#215)
* Use XmlNode.Name in PI-Processing
relates Issue Xavalon#181
* Add test case based in Issue Xavalon#181
Extended bug scenario by using multiple processing instructions at once.
* Update handling of process instructions
* Remove unnecessary whitespace
* Reduce test-files to its minimum
Use interpolation instead of String.Builder
Hello everyone,
thanks for this great tool and its Visual Studio integration.
I love it, ever since I discovered it some months ago 👍
For me it worked like a charm until I tried to add some XAML-files to my
Xamarin.Forms
project, which have no code behind-files.By definition I do need to declare the
<?xaml-comp compile="true" ?>
node at the top of the file, but unfortunately this line changes on save to<?Mapping compile="true" ?>
, if the XAML Styler extension is activated in my Visual Studio 2017 Enterprise IDE .I tried to find a configuration or a "ignore-list" to avoid automatically "excluding" my XAMLs from compilation - but without success.
Does this happen on purpose or is this just a bug?
I honestly do not understand the
<?Mapping compile="true" ?>
line at all - perhaps because of my bad searching skills? - so I don't want to blame your great tool, because of some missing knowledge here.Anyway this could be some unwanted behaviour and I really want to reactivate XAML Styler in my projects 😉
It would be great, if you could have a look at this and let me know what the problem is/could be 👍
Example.xaml
The text was updated successfully, but these errors were encountered: