9
woops
3y

FUCK YOU MICROSOFT
GO FIX YOUR FUCKIN C# METHODS

Language felt good but jesus fuckin christ.

HOW YOUR File.Exists() can be so retarded jesus fuckin christ
I mean god, how retarded can it be when i obtain the current directory with your builtin method (System.Environment.CurrentDirectory) attach to it the directory name with the images i need and I ALWAYS GET FALSE ABOUT ITEMS THAT ARE FUCKIN THERE.

Fix your fuckin encodings too, suckers.

Comments
  • 0
    is it case-sensitive?
  • 2
    I’ve never had a problem with System.IO...
    What happens when you call Directory.GetFiles ?
  • 8
    1- File.Exists(string) is a .net framework method. Not a C# method. That same method is available in VB.net too.
    2- From your post, i saw you're trying to check if a Directory exists. If So, use Directory.Exists(string) instead.
    3- use the fucking Path.Combine(string1, string2, ...) if you don't like dealing with the paths in windows.
  • 3
    And remember to recheck the working path as in .net core visual studio sets the working path rather to the path where the build output is...
  • 7
    By the last two comments, seems you are in the wrong and Microsoft seems to know what they are doing.

    Shape up.
  • 0
    @mundo03 if i search for a way to check if the file exists and everyone recommends File.exists() i see that this method is provided by MS so i expect that shit to work like it supposed to do

    True if the file exists, false if it doesn't

    not returning true if it exists and false in every other case, throw a fuckin error if there is a problem.

    @MrCSharp

    thanks for the path, i will keep that in mind
Add Comment