VS Editor Alignments all messed up

Hey,

Not sure if this is related to Oxygene or if it’s actually Visual Studio but of late my indents on the code editor are all getting messed up.

When I tab and enter a line of code (like in a begin…end structure) and then press return before it used to place the cursor under the indented line. However now it takes it all the back to column 0 in the editor. Any one got any clues, or is this happening to anyone else ?

Visual Studio 2013 Update 3
Remobjects Elements 7.2.77.1621

edit the thing is, if I close VS and then re-open it, my indents go back to normal. It’s really frustrating

Is tour editor set to inset tabs o spaces? for Oxygene, it SHOULD be set to insert 2 spaces per indent. If it gets set to tabs, that could be whats causing problems…

Mark,
I had also this problem with some versions of the compiler. It was corrected in more recent versions, but I can’t remember which one was correcting this…

Just checked,

VS is set as follows for Oxygene :-
Indenting = Smart
Tab Size = 2
Indent Size = 2
Insert Spaces radio button checked

Hello Anthoni,

That sounds like a bug of Oxygene. We fixed some errors in the indentation and if you are using latest Oxygene build I need more info on how to reproduce that error. Does it happens in specific project or specific file only? Any additional info on what you did before getting error will be very helpfull.

Best regards.

It happens in all the projects I am doing.
Not found any pattern that triggers it (or I would avoid it).

One thing I did find is it I close the editor and restart my indentation is back, but that slows down productivity as you can imagine :smile:

Not sure if this is related, but since upgrading to the latest release, my VS seems to regularly crash when opening Oxygene projects.

I notice that if I remove the projects suo file, then I can normally re-open the project again safely. Has something got screwed saving options?

Hi,

I have the same issue, I have to delete the .user or .suo file to be able to open a project all the time.
All started after I upgraded VS to the latest update.

@estechco, @jeroenvandezan : If you guys see this with a relatively simple project you can send us with the suo that breaks it, that’d be great, we can investigate what makes it crash.

Unfortunately, I’ve only seen it, so far, with a couple of my bigger projects and even then rather sporadically. It’s conceivable, once the suo has been regenerated the problem may have disappeared (although I’m fairly certain one project has done it more than once). I don’t think in either case I would have had more than a handful of open files in VS.

I’ll keep an eye out for a simpler case, or respond back once I have more to go on. Would you need every file in the project or just the .suo, .sln, .oxygene type files?

the suo contains which files were open last time you had the project open, which is probably what it fails on. I would need the full thing yes

If we can’t get the project, then it would be good if we can get the crash report from Event Viewer, if any.

Mark,

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.ThrowHelper.ThrowInvalidOperationException(System.ExceptionResource)
at System.Collections.Generic.List`1+Enumerator[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNextRare()
at System.Collections.Generic.List`1+Enumerator[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Linq.Enumerable+d__14`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at a.j.IntDoneLoading()
at a.j.b__0()
at e.E.IntRun(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

After three crashes, the solution was loaded correctly!

I’ve not experienced the crashes like the others just the stupid indents not working.
However, come to think of it, they did stop working on the latest VS update (Update 3), so maybe it’s all related ?

Anthoni,
I also have VS2013 Update 3 and I don’t have the indent problem with the last BETA release. I had them with some older releases and they have been corrected. So please install the last version and try again.

What version are you on ?
I posted my Oxygene version above.
Is yours higher ?

Version 8.0.80.1627.
If RemObjects continues at the same speed as before, there should be a new version today.

Patrick: I think I got this one fixed for todays build.

If tonights build doesn’t work for you @anthoni it might be the project itself that’s confusing the IDE somehow.

Is this the beta build that I need to download ?