|
Hi ppl,
I'm new here on this forum. I'mdoing a final project for my study of information systems development. This final project is at Centric, and is about Oslo. Thats very good for me indeed :)
The last few days i've been googling and searching the oslo forum on various error messages and crashes. None of the search engines could help me out; typing in error codes results into nothing or jibberish. Maybe Oslo is just too new.
Or, maybe i'm searching in the wrong locations. For example: where should i find elaboration on the following error:
warning M0227:Reference 'Artists' used to bind to a a type member using implicit 'this' and now binds to an item at a higher scope. Please use 'value.Artists' to restore the original binding.
Yes i solved it.I just added the module name (other scope) in front of the extent. (where value in Music.Artists instead of Artists).
Searching for warning M0227 results into nothing. Is it supposed to be like that?
Regards, Elger Performing my Final Project, looking into codename "Oslo". | | Elger [Centric] | Elger, Compiler and runtime error and warning messages contain unique identifiers (such as M0227) to correlate the different internationalizations/localizations of the text in the error/warning messages (otherwise, the message is uniquely identified solely by the text of its message). I suspect that (like every other Microsoft product) once the compiler and runtimes are released as 1.0, MSDN will have "elaboration" on each message, but I'm guessing that that documentation just isn't yet written/published. Regarding that particular message, I do notice a typo in it, so if you copied & pasted the message, it has a typo. :) "to bind to a a type". Did the warning message help you in solving the issue, or could it be more clear? More precisely, does it help you understand the reason why it's giving a warning?
'blog: http://diakopter.blogspot.com/
JSMeta: http://jsmeta.org/- Proposed As Answer byKraig BrockschmidtMSFT, ModeratorTuesday, July 21, 2009 2:34 PM
- Marked As Answer byElger [Centric] Tuesday, July 21, 2009 3:05 PM
-
| | Matthew Wilson _diakopter_ | Yes, Matthew is correct in that documentation for error messages is something that comes together closer to the actual release of a technology. "Oslo" is still in pre-release/CTP stages and is thus undergoing significant changes month to month. I'm sure that experience has show that it's not a good investment to document warnings/errors now because so much of that work would have to be thrown away.
The best alternative at this point in "Oslo's " development is to ask about errors and warnings here on this forum, exactly as you did.
.Kraig - Marked As Answer byElger [Centric] Tuesday, July 21, 2009 3:05 PM
-
| | Kraig Brockschmidt | Elger, Compiler and runtime error and warning messages contain unique identifiers (such as M0227) to correlate the different internationalizations/localizations of the text in the error/warning messages (otherwise, the message is uniquely identified solely by the text of its message). I suspect that (like every other Microsoft product) once the compiler and runtimes are released as 1.0, MSDN will have "elaboration" on each message, but I'm guessing that that documentation just isn't yet written/published. Regarding that particular message, I do notice a typo in it, so if you copied & pasted the message, it has a typo. :) "to bind to a a type". Did the warning message help you in solving the issue, or could it be more clear? More precisely, does it help you understand the reason why it's giving a warning?
'blog: http://diakopter.blogspot.com/
JSMeta: http://jsmeta.org/- Proposed As Answer byKraig BrockschmidtMSFT, ModeratorTuesday, July 21, 2009 2:34 PM
- Marked As Answer byElger [Centric] Tuesday, July 21, 2009 3:05 PM
-
| | Matthew Wilson _diakopter_ | Yes, Matthew is correct in that documentation for error messages is something that comes together closer to the actual release of a technology. "Oslo" is still in pre-release/CTP stages and is thus undergoing significant changes month to month. I'm sure that experience has show that it's not a good investment to document warnings/errors now because so much of that work would have to be thrown away.
The best alternative at this point in "Oslo's " development is to ask about errors and warnings here on this forum, exactly as you did.
.Kraig - Marked As Answer byElger [Centric] Tuesday, July 21, 2009 3:05 PM
-
| | Kraig Brockschmidt | Thanks for this answer. (also thanks Kraig). It makes perfect sense the docs aren't finished yet, but i could have overlooked something.
The reason the message has a tpyo is due to my copy pasting mutation.
The message in itself is clear for persons with medium programming experience, but you have to think about what it means. It could have been improved by hinting how to explicitly usethe higher scope; yet, this might be a trivial. Fine with me i guess. :)
Performing my Final Project, looking into codename "Oslo". | | Elger [Centric] |
|