Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
One of my addition (F# binding) is using it and
I'm getting "Failed to load Mono.TextEditor.Highlighting.ResourceXmlProvider from assembly Mono.TextEditor
in git version on Monodevelop there is no ResourceXmlProvider but in 4.0 archive there is...
What should I do?
I thought the F# binding already got ported - I've seen some twitter buzz about it ?
It's now ResourceStreamProvider
F# binding is using ResourceXmlProvider it's ported to 4.0 but ResourceStreamProvider appears later then 4.0 (seems like)
May you help us to close this bug https://github.com/fsharp/fsharpbinding/issues/105
and edit https://github.com/fsharp/fsharpbinding/blob/master/monodevelop/MonoDevelop.FSharpBinding/FSharpSyntaxMode.fs
to point ResourceStreamProvider instead of ResourceXmlProvider
You've to choose either 4.0 or monodevelop master. The new color scheme backend came too late to be included in 4.0 :( ... it's a 4.0.1 feature now.
I've no write access to the fsharpbinding, it's not ours :(
I need just to know the way how to replace it :)
There are really complex stuff in C# binding there and I'm not sure if I guess how to use it correct.
Just rename ResourceXmlProvider -> ResourceStreamProvider
Uh oh, an ABI break between 4.0 and 4.0.2 is really bad.
Mike, is there any way you can add dummy/obsolete classes so we at least don't break ABI?
Can I get some help for all the changes? :)
I get one error next to another :D
and answers: https://github.com/Cynede/monodevelop/commit/a428c2419775075a3b455b8497cf4d78bb64765c#commitcomment-2712610
mhutch: not really - it's working differently. It's no longer based on xml streams.
The ABI has been fixed: https://github.com/mono/monodevelop/commit/d121fffbe2ccd1fdfe14c5a0dbbce2c225d59716
Thank you :) But there are more breaking changes that I have no time to learn yet.
mhutch: not really 'fixed' but the case is working.
(Keep in mind that the methods change the signature)
The bigger problem is that the color system changed - you need to update colors. Which brings me to another point:
Why do you have a semantic syntax mode that doesn't color anything ?