inconsistent line endings

[anon_83463695]

I’m using Unity 3D in combination with Visual Studio 2008 on a Windows 7 64 bit system.

When saving a cs file in Visual Studio and returning to Unity 3D I always get the following warning:

There are inconsistent line endings in the ‘someFileName.cs’ script. Some are Mac OS X (UNIX) and some are Windows.
This might lead to incorrect line numbers in stacktraces and compiler errors. Unitron and other text editors can fix this using Convert Line Endings menu commands.

I’ve seen that more people have this problem but they all are using OS X.

How can I fix this problem on my Windows machine?

UPDATE:
OK, I fixed the problem by replacing the NewBehaviourScript.cs that is located in Unity\Editor\Data\Resources
By creating a new script using Windows it contains only CrLf for new lines. So now when I create a new cs script in Unity and edit it in Visual Studio all the line endings are the same. So no more warnings

[anon_26261327]

Good fix. I had been changing the newlines each time I created a new script, didn’t realize the template script was somewhere I could edit once and for all.

John C>
“For all your days, prepare, and meet them ever alike;
When you are the anvil, bear - when the hammer, strike.”

[PatHightree_1]

Awesome, I wish I could upvote this.
Thanks for sharing

[LVBen]

Sweet!

[acollins]

What do you mean by “creating a new script using Windows it contains only CrLf for new lines”? How do you actually do this?

[Hikiko66]

I assume you just have to open the NewBehaviourScript.cs script in VS, and then save it.

[LEDWORKS]

@acollins

What do you mean by “creating a new script using Windows it contains only CrLf for new lines”? How do you actually do this?

Create a new class in visual studio and set it up in the same way as the default NewBehaviourScript.cs.
Do not copy and paste as you will most likely copy the line endings too, thus undoing your efforts.
It is possible Unity does this so that other OS’s IDE’s ‘understand’ the script too.

Line endings by the way are the characters that text editors interpret as a new line.
“/n” or “/r” for example.

[grimprophecy]

IMO the best solution for this problem is not to change the default Monobehaviour script, as in the case you want to share the project, it means you have to ensure they have the same setup as you, or change their default line endings in mono etc which will only hassle potential team mates. Instead what I did was get an addon for VS called “Strip’em”(grebulon.com), it allows you the option to force Unix (the default mono) line endings on save (without having to change settings each time).

[system]

The easiest way to change the line endings without having to modify anything in VS is to go to the File > Advanced Save Options. In the Advanced Save Options window, under Line endings drop down, select the line ending you want to use and click OK. Then save the script again; this will automatically change the line endings in your script when you save it. When you go back into Unity, the error will disappear.

[Valvados]

prefer to change the C# template as it has not neat formatting anyway.

[BlackPanda]

In VS 2013, reopen the file in VS itself and a popup will ask you to convert line endings. Just select crlf there.

[crandellbr]

Finally, no more popups in Visual Studio! I already knew of the script templates, but last time I was only looking to add common using directives like System.Collections.Generic. I wasn’t paying attention to how the code was clumped up on one line, a sure giveaway that the template had non-Windows endings. I just upgraded to 4.6 and had to edit the template again when it finally hit me.

[cmcpasserby]

Just use stripem, or if you know only windows users using vs will be editing you could also change the template.

grebulon.com

I opted to just use stripem to force unix style endings since some people I work with use mono, and that I will sometimes use gvim to do fast edits.

Also a other option is most version control systems like git, can enforce a certain kinda kind ending on commit.

[Elixir]

I’m using VisualStudio 2012 to write my scripts and I used to get these warnings.
To solve the problem just go to your scripts in VS and do:
Edit > Advanced > Format Document

That will stop the warnings.

[Jeromeyers]

Awesome, I love the direct fixing of the line endings in the script template. Both addresses the problem at the root and opens up new possibilities!

[meowFlute]

you could also just use this method of resetting all of the line endings

http://www.larshaendler.com/2013/06/10/notepad-unix-to-dos-line-endings/

[jwinn]

The easiest way to change the line endings without having to modify anything in VS is to go to the File > Advanced Save Options. In the Advanced Save Options window, under Line endings drop down, select the line ending you want to use and click OK. Then save the script again; this will automatically change the line endings in your script when you save it. When you go back into Unity, the error will disappear.

To elaborate on this technique, it does work, but it will only apply to the current file. There unfortunately does not seem to be a per project line ending setting built in (at least in the free Visual Studio 2013), which is why people are using the Strip’em add-in linked above.

Note that this add-in sets the line endings globally (all files, all projects), so you would need to disable/enable it if you’re switching between projects that have both Windows and Linux line endings. Strip-em it is!

[Wolfram]

The easiest way to change the line endings without having to modify anything in VS is to go to the File > Advanced Save Options. In the Advanced Save Options window, under Line endings drop down, select the line ending you want to use and click OK. Then save the script again; this will automatically change the line endings in your script when you save it. When you go back into Unity, the error will disappear.

This. Thank you, this is what I was looking for, and it fixes the problem, without using any workarounds, and you can still have a mixed team of Mac and Windows developers working together.

EDIT: Damn! Seems I was partying too soon. As others wrote, this setting does not appear to be permanent, is maybe on a per-file basis, and even if I re-open “Advanced Save Options” immediatly, it doesn’t show the setting I chose, but merely says “Current Setting”, without stating what that setting is.
To make a long story short, I now also installed Stick’em. The only weird thing seems to be that now the files are saved as ASCII, not as UTF-8. But that should be OK for source code.

[Mattias_Timonen]

The easiest way to change the line endings without having to modify anything in VS is to go to the File > Advanced Save Options. In the Advanced Save Options window, under Line endings drop down, select the line ending you want to use and click OK. Then save the script again; this will automatically change the line endings in your script when you save it. When you go back into Unity, the error will disappear.

That’s the kind of solution we wanted to see! Using the options at hand without the need for downloading scritps and add-in’s or whatever. thank you!

[dlqx]

The easiest way to change the line endings without having to modify anything in VS is to go to the File > Advanced Save Options. In the Advanced Save Options window, under Line endings drop down, select the line ending you want to use and click OK. Then save the script again; this will automatically change the line endings in your script when you save it. When you go back into Unity, the error will disappear.

thanks, that’s the trick