UID 4.4 system feedback .NET

General
,
1

The whole UID system is pointless for projects using .NET. It makes no sense to have to have a companion uid file for every single source file. When you are using a language that has assembly and is using stuff like namespaces.

If the goal is to ensure that the file path doesn’t change without the editor being aware of it, then just don’t use the path. Use the assembly and namespace from that. This is just unnecessary additional files to version. Or at least give us the option to just turn this system off and let me handle the file moving paths on my own like I was before.

Or just have one file with a list of all the UIDs not thousands of files with just one UID in it for every file in the project. This seems very rushed and not thought through.

1 Like
2

Hello,
you can use separate C# project for independent scripts.

3

Also one more point. If you use generated code ie. generating sources from a protobuf file. You usually do not version those but now the generated files have a uid file as well.

1 Like
4

Yes but sometimes you don’t want to do that. When you didn’t have to separate code from editor before like this only to not be annoyed by the new uid system.

5

Seconding this. I’m holding off on using 4.4 just because of how much of an irritation all the pointless extra files in my source directory will be. There really needs to be an obvious way to turn off uid files for C# code.

2 Likes