Oh one other question. Is it just this project or any project?
Two points.
(1) I’ve removed Ankh and I still get the same error.
(2) I can’t say if it’s just this project or any project, but I /can/ say that there are projects which don’t throw an error.
I sent this particular project to support … did you test against it?
what bugid did you get for this from the support bot? I looked through the list and I cannot find anything from your email address.
Hi Carlo. The mail to supprt with attachment bounced (too big) so I told support in the thread above I’d shared it via Dropbox and invited support@remobjects.com.
I’ve put an updated version of the same project in there, so please speak to brianl or mh about getting access to it. Please note, this is the same project that we are talking about in the other thread. Perhaps all of these problems are linked?
By the way, one thing that’s unusual about this project is that it has a reference to a .NET 1.1 DLL that contains remoting definitions.
@ck were you also able to reproduce the exception on startup and the broken code completion? Those problems have persisted with this project since I started working on it, before I introduced the problematic code discussed in the other thread.
John: what’s the support ticket ID you got for this?
@johnid: I did reproduce this yes. The internal error is gone, the IDE exceptions are being worked on; bugs://56537 No colorizing in ASP.Net projects.
Great stuff! Thanks Carlo.
Just to check, which version should I be using to do actual work that contains the fixes discussed here?
Because I don’t think 5.1.34.1047 is really working for me. http://imgur.com/CK3zK
.1055 is the latest beta. http://beta.remobjects.com
So there isn’t a gamma or stable release at the moment that should contain the fixes I need? I should use a beta release for production work at the moment?
Beta software is beta.
306 2012/07/31 15:56:01.188 Error Editor or Editor Extension System.NullReferenceException: Object reference not set to an instance of an object. at RemObjects.Oxygene.VisualStudio.Editor.MarkerAdornmentFactory.TextViewCreated(IWpfTextView textView) at Microsoft.VisualStudio.Text.Editor.Implementation.WpfTextView.<>c__DisplayClassd.<BindContentTypeSpecificAssets>b__a() at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call)Latest beta: http://i.imgur.com/rmbAx.png
Hello John,
the NRE in MarkerAdornmentFactory is a known bug (bugs://57253). The fix should be available in the next build.
Best regards.
Thanks Viktoria. I’m still having considerable issues with the syntax highlighting and other editor features though, as always.
johncc said: I'm still having considerable issues with the syntax highlighting and other editor features though, as always.have these been reported? aside form the NRE you mentioned, which was a weird corner-case regression new in .1055 (and related to new changes there), i'm not aware of a any major editor issues being known and open on our end
Hi Martin. The issues have really been continuous. I’ve reported this issue previously, but I’m never sure if I’m seeing the same problems or new ones. Happy to open a new report if required.
yes, we’ll need details. many of us spend large amounts of our days inside the Oxygene IDE, and we’re not aware of any problems.
just to confirm, this is with .1041? can you upgrade to the new July release we made available today (.1053) and/or better yet the next beta drop which will have fixed the NRE that kept you and some others from using 1055.
Apologies for the delay - just got back from vacation. These latest problems centered around 5.1.34.1047 and the .1055 beta as well. I will try updating to the latest beta, and I’ll post any more comments in the issue thread that I raised.