Player2

9y

Finally fixed a major bug.....

FUCK YOU C# AND YOUR FUCKING CASE SENSITIVE BULLSHIT.

DAYS
THAT TOOK FUCKING DAYS AND AT NO POINT DUD VISUAL STUDIO BOTHER TO MENTION THAT FUCKING ERROR.

1 CHARACTER, ON ONE LINE, EFFECTIVELY BROKE THOUSANDS OF LINES OF CODE

fuck this, I quit. See you next time you contact the Microsoft live support chat!

undefined

Ranter

Comments

4

jw56578

110

9y

What the hell version of visual studio are you using. The special discount version that doesn't compile anything
3

Player2

2123

9y

@jw56578 the unity version. The unity cloud build integrated version. That decides the difference between working and not working is the difference between "ElseIf" and "elseIf".....

FUCK
1

Player2

2123

9y

@azuredivay first thing I did once I found and fixed the error was a repair, they always seem to help, right up untill the crucial point :D
1

ElectricCoffee

3340

9y

Switch to visualbasic, it's case insensitive :P
2

Player2

2123

9y

@ElectricCoffee yadda yadda, I know. Buy it had been a long day
3

CodeMasterAlex

1147

9y

That's not C#'s fault, it's your IDE to blame.
3

ChrilleKrim

8

9y

I remember those days when using notepad as IDE...not so much ranting over it back then.
4

enchance

1032

9y

@ChrilleKrim Coding in notepad is for rockstars. I want to be a rockstar but...it's so hard.
2

hell

16461

9y

Ew case insensitive programing makes me sick 😵
0

GigabyteDX

528

9y

@jw56578 bruh. Visual studio code it the shit.
0

GigabyteDX

528

9y

@Player2 where are your unit tests at?
1

Player2

2123

9y

@GigabyteDX the same place VS's error detecting is apparently...
0

ElectricCoffee

3340

9y

@azous I dunno, lisp is insensitive and it never got in the way

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service