Bug 10756 - Where is ResourceXmlProvider?
Summary: Where is ResourceXmlProvider?
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC All
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-02-28 04:33 UTC by Heather
Modified: 2013-03-01 06:34 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Heather 2013-02-28 04:33:08 UTC
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?
Comment 1 Mike Krüger 2013-02-28 04:36:37 UTC
I thought the F# binding already got ported - I've seen some twitter buzz about it ? 

It's now ResourceStreamProvider
Comment 2 Heather 2013-02-28 04:44:48 UTC
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
Comment 3 Mike Krüger 2013-02-28 04:48:26 UTC
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 :(
Comment 4 Heather 2013-02-28 04:55:36 UTC
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.
Comment 5 Mike Krüger 2013-02-28 04:58:45 UTC
Just rename ResourceXmlProvider -> ResourceStreamProvider
Comment 6 Mikayla Hutchinson [MSFT] 2013-02-28 05:08:41 UTC
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?
Comment 7 Heather 2013-02-28 05:21:37 UTC
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
Comment 8 Mike Krüger 2013-02-28 05:45:28 UTC
mhutch: not really - it's working differently. It's no longer based on xml streams.
Comment 9 Mikayla Hutchinson [MSFT] 2013-03-01 05:36:24 UTC
The ABI has been fixed: https://github.com/mono/monodevelop/commit/d121fffbe2ccd1fdfe14c5a0dbbce2c225d59716
Comment 10 Heather 2013-03-01 06:33:16 UTC
Thank you :) But there are more breaking changes that I have no time to learn yet.
Comment 11 Mike Krüger 2013-03-01 06:34:40 UTC
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 ?