Update '.gitignore' to resolve issues whereby NECESSARY FILES are not committed or recorded... #1

2020-01-10T16:39:01Z

seriussoft commented

2020-01-10 16:39:01 +00:00

Because this repo will eventually house stuff from all across the board (VS, VSCode, Eclipse, Unity, Xamarin, Java, Android, iOS, UWP/Windows, MS Office, etc), they were ALL added to the single .gitignore on repo creation to avoid missing some.
HOWEVER, this broke several commits because they overlap (Unity ignores ALL .csproj , .sln , and similar project/solution files because you might use VS to edit files, but they didn't want your UNITY code to be compiled by VS or MSBUILD except through Unity factories...I was unawares of this (and others to be listed below), so they are being commented out and then mentioned above as to where they are commented out so that when we are ready to add them for their respective directories and the local .gitignore files, we can merely copy-paste them into the appropriate files and uncomment them...this way they will correctly ignore ONLY where ignoring said files is necessary/appropriate/desirable
File Types and Sections affected are as follows:

---- SQL's .MDF files (necessary for web related work that's in dev and/or small/quick projects with mdf files for local easy-to-move database files with their executables)

---- GhostDoc's xml configs (necessary for any GhostDoc or SandCastle documentation work that reads from my XMLDoc files for VS projects)

---- Unity's ignoring of all project and solution level files used/necessary by/for Visual Studio and their projects/solutions (biggest problem right now)

---- Java/Eclipse's .CProject and related file extensions for any C++ code, be it manually created or automagically created (factory/auto-generation)

---- Java/Eclipse's .target file - this is a necessary file extension per Visual Studio (at the minimum) which tells VS how to order things when calling MSBuild on multiple projects (specifically, there's the .csproj project file, then the ..props file[s] for pre-csproj MSBuild instructions, and finally ..target file[s] for post-csproj MSBuild instructions)

---- MonoDevelop's *.resources (used by all manner of VS Project development (.csproj projects, C++ project files, .lib mentions, *.dl links, .vbproj projects, and more all use *.resource and/or *.resources for housing information about resource bits (such as strings, icons, images, binary data, etc... it is especially useful/necessary for Xamarin.Forms Android projects...)

Again, these are necessary for later on (planned out already), so i wanted to avoid having to build brand new repo's just to determine the .gitignore contents for each of these sections that will be used for local .gitignore files when necessary, but didn't expect them to block necessary files, and because of this, will have to start over on my work getting the Xamarin projects loaded and committed (and hopefully building..hopefully)...

- Because this repo will eventually house stuff from all across the board (VS, VSCode, Eclipse, Unity, Xamarin, Java, Android, iOS, UWP/Windows, MS Office, etc), they were ALL added to the single .gitignore on repo creation to avoid missing some. - HOWEVER, this broke several commits because they overlap (Unity ignores ALL .csproj , .sln , and similar project/solution files because you might use VS to edit files, but they didn't want your UNITY code to be compiled by VS or MSBUILD except through Unity factories...I was unawares of this (and others to be listed below), so they are being commented out and then mentioned above as to where they are commented out so that when we are ready to add them for their respective directories and the local .gitignore files, we can merely copy-paste them into the appropriate files and uncomment them...this way they will correctly ignore ONLY where ignoring said files is necessary/appropriate/desirable - File Types and Sections affected are as follows: ---- SQL's .MDF files (necessary for web related work that's in dev and/or small/quick projects with mdf files for local easy-to-move database files with their executables) ---- GhostDoc's xml configs (necessary for any GhostDoc or SandCastle documentation work that reads from my XMLDoc files for VS projects) ---- Unity's ignoring of all project and solution level files used/necessary by/for Visual Studio and their projects/solutions (biggest problem right now) ---- Java/Eclipse's .CProject and related file extensions for any C++ code, be it manually created or automagically created (factory/auto-generation) ---- Java/Eclipse's .target file - this is a necessary file extension per Visual Studio (at the minimum) which tells VS how to order things when calling MSBuild on multiple projects (specifically, there's the .csproj project file, then the *.*.props file[s] for pre-csproj MSBuild instructions, and finally *.*.target file[s] for post-csproj MSBuild instructions) ---- MonoDevelop's *.resources (used by all manner of VS Project development (.csproj projects, C++ project files, .lib mentions, *.dl links, .vbproj projects, and more all use *.resource and/or *.resources for housing information about resource bits (such as strings, icons, images, binary data, etc... it is especially useful/necessary for Xamarin.Forms Android projects...) Again, these are necessary for later on (planned out already), so i wanted to avoid having to build brand new repo's just to determine the .gitignore contents for each of these sections that will be used for local .gitignore files when necessary, but didn't expect them to block necessary files, and because of this, will have to start over on my work getting the Xamarin projects loaded and committed (and hopefully building..hopefully)...

seriussoft marked the pull request as ready for review 2020-01-10 16:39:49 +00:00

seriussoft commented

2020-01-10 16:40:37 +00:00

OK - Merging PR

seriussoft closed this pull request

2020-01-10 16:40:58 +00:00

seriussoft closed this pull request

2020-01-10 16:40:58 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Reference: seriussoft/FF-Helper#1