3 ms·
I work with C#, Visual Studio. 1 level of folder nesting was more than enough for me so far. I see a deeply nested folder hierarchy as a code smell, I once had
by GoblinSlayer 7y ago
I work with C#, Visual Studio. 1 level of folder nesting was more than enough for me so far. I see a deeply nested folder hierarchy as a code smell, I once had to walk one such hierarchy to convert files into utf8, and it was a massive pain.
- nxc18 7y agoThe issue is with forms and the like, the tooling creates a lot of intermediate files based on the names of classes and whatnot. If you’re following the ‘best practice’ naming patterns, and have your code in a user folder, it’s likely you’ll run out of characters. I don’t use more than 2 folder levels ever, but I have a product with wordy names.
- 9wzYQbTYsAIc 7y agoWhat I’ve started to do is put everything in c:\src\<git-repo>, which limits the overhead to 3 characters instead of the 42 or whatever for your users folder.
- GoblinSlayer 7y agosrc/MyProductDeluxe9999LimitedUnleashed/Branch/MyProductForms/AboutForm.Designer.cs - 83 characters, about 1/3 of path length limit.
- 9wzYQbTYsAIc 7y agoEw, TFS?
- nxc18 7y agoC:\Users\user\Documents\Visual Studio 2019\Projects\myrepo\src\MyProductDeluxe9999LimitedUnleashed\Branch\MyProductForms\myapp.Android\obj\Debug\90\android\bin\classes\mono\android\support\design\widget\BottomNavigationView_OnNavigationItemReselectedListenerImplementor.class - 276 characters Only 227 if you're careful about where you put it, but that's kind of the point - you have to be careful about where you put/build your Xamarin projects from.