As a. Net developer, we have the most powerful ide in the universe: Visual Studio, which makes our development efficiency better. We don’t need to worry about the configuration of environment variables and other code management tools, because vs has rich extension tools. Don’t talk too much nonsense, just get to the point. When we use VS to develop related. Net projects, we often find that nothing has changed in the pull-down code, that is, some files need to be submitted after running, such as the most common bin / debug, bin / release, obj / debug, obj / release files. But I don’t want to submit these files to the remote git code remote warehouse. In fact, this is very simple. We only need to add a new ignore text file (. Gitignore) in the project directory when we first create the project, and then push it to the remote warehouse using GIT.
Files to be ignored:
Configure. Gitignore to ignore files that do not need to be submitted:
Add the. Gitgnore template of visual studio to the project:
The following is an ignored file template for. Net /. Net core related projects. Any project developed with visual studio can use it:
Gitnore ignores file template source: https://github.com/github/gitignore/blob/master/VisualStudio.gitignore There are many programming languages or IDE related. Gitgnore configurations in this project, which can be downloaded and used directly.
## Ignore Visual Studio temporary files, build results, and ## files generated by popular Visual Studio add-ons. ## ## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore # User-specific files *.rsuser *.suo *.user *.userosscache *.sln.docstates # User-specific files (MonoDevelop/Xamarin Studio) *.userprefs # Mono auto generated files mono_crash.* # Build results [Dd]ebug/ [Dd]ebugPublic/ [Rr]elease/ [Rr]eleases/ x64/ x86/ [Ww][Ii][Nn]32/ [Aa][Rr][Mm]/ [Aa][Rr][Mm]64/ bld/ [Bb]in/ [Oo]bj/ [Ll]og/ [Ll]ogs/ # Visual Studio 2015/2017 cache/options directory .vs/ # Uncomment if you have tasks that create the project's static files in wwwroot #wwwroot/ # Visual Studio 2017 auto generated files Generated\ Files/ # MSTest test Results [Tt]est[Rr]esult*/ [Bb]uild[Ll]og.* # NUnit *.VisualState.xml TestResult.xml nunit-*.xml # Build Results of an ATL Project [Dd]ebugPS/ [Rr]eleasePS/ dlldata.c # Benchmark Results BenchmarkDotNet.Artifacts/ # .NET Core project.lock.json project.fragment.lock.json artifacts/ # ASP.NET Scaffolding ScaffoldingReadMe.txt # StyleCop StyleCopReport.xml # Files built by Visual Studio *_i.c *_p.c *_h.h *.ilk *.meta *.obj *.iobj *.pch *.pdb *.ipdb *.pgc *.pgd *.rsp *.sbr *.tlb *.tli *.tlh *.tmp *.tmp_proj *_wpftmp.csproj *.log *.vspscc *.vssscc .builds *.pidb *.svclog *.scc # Chutzpah Test files _Chutzpah* # Visual C++ cache files ipch/ *.aps *.ncb *.opendb *.opensdf *.sdf *.cachefile *.VC.db *.VC.VC.opendb # Visual Studio profiler *.psess *.vsp *.vspx *.sap # Visual Studio Trace Files *.e2e # TFS 2012 Local Workspace $tf/ # Guidance Automation Toolkit *.gpState # ReSharper is a .NET coding add-in _ReSharper*/ *.[Rr]e[Ss]harper *.DotSettings.user # TeamCity is a build add-in _TeamCity* # DotCover is a Code Coverage Tool *.dotCover # AxoCover is a Code Coverage Tool .axoCover/* !.axoCover/settings.json # Coverlet is a free, cross platform Code Coverage Tool coverage*.json coverage*.xml coverage*.info # Visual Studio code coverage results *.coverage *.coveragexml # NCrunch _NCrunch_* .*crunch*.local.xml nCrunchTemp_* # MightyMoose *.mm.* AutoTest.Net/ # Web workbench (sass) .sass-cache/ # Installshield output folder [Ee]xpress/ # DocProject is a documentation generator add-in DocProject/buildhelp/ DocProject/Help/*.HxT DocProject/Help/*.HxC DocProject/Help/*.hhc DocProject/Help/*.hhk DocProject/Help/*.hhp DocProject/Help/Html2 DocProject/Help/html # Click-Once directory publish/ # Publish Web Output *.[Pp]ublish.xml *.azurePubxml # Note: Comment the next line if you want to checkin your web deploy settings, # but database connection strings (with potential passwords) will be unencrypted *.pubxml *.publishproj # Microsoft Azure Web App publish settings. Comment the next line if you want to # checkin your Azure Web App publish settings, but sensitive information contained # in these scripts will be unencrypted PublishScripts/ # NuGet Packages *.nupkg # NuGet Symbol Packages *.snupkg # The packages folder can be ignored because of Package Restore **/[Pp]ackages/* # except build/, which is used as an MSBuild target. !**/[Pp]ackages/build/ # Uncomment if necessary however generally it will be regenerated when needed #!**/[Pp]ackages/repositories.config # NuGet v3's project.json files produces more ignorable files *.nuget.props *.nuget.targets # Microsoft Azure Build Output csx/ *.build.csdef # Microsoft Azure Emulator ecf/ rcf/ # Windows Store app package directories and files AppPackages/ BundleArtifacts/ Package.StoreAssociation.xml _pkginfo.txt *.appx *.appxbundle *.appxupload # Visual Studio cache files # files ending in .cache can be ignored *.[Cc]ache # but keep track of directories ending in .cache !?*.[Cc]ache/ # Others ClientBin/ ~$* *~ *.dbmdl *.dbproj.schemaview *.jfm *.pfx *.publishsettings orleans.codegen.cs # Including strong name files can present a security risk # (https://github.com/github/gitignore/pull/2483#issue-259490424) #*.snk # Since there are multiple workflows, uncomment next line to ignore bower_components # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) #bower_components/ # RIA/Silverlight projects Generated_Code/ # Backup & report files from converting an old project file # to a newer Visual Studio version. Backup files are not needed, # because we have git ;-) _UpgradeReport_Files/ Backup*/ UpgradeLog*.XML UpgradeLog*.htm ServiceFabricBackup/ *.rptproj.bak # SQL Server files *.mdf *.ldf *.ndf # Business Intelligence projects *.rdl.data *.bim.layout *.bim_*.settings *.rptproj.rsuser *- [Bb]ackup.rdl *- [Bb]ackup ([0-9]).rdl *- [Bb]ackup ([0-9][0-9]).rdl # Microsoft Fakes FakesAssemblies/ # GhostDoc plugin setting file *.GhostDoc.xml # Node.js Tools for Visual Studio .ntvs_analysis.dat node_modules/ # Visual Studio 6 build log *.plg # Visual Studio 6 workspace options file *.opt # Visual Studio 6 auto-generated workspace file (contains which files were open etc.) *.vbw # Visual Studio LightSwitch build output **/*.HTMLClient/GeneratedArtifacts **/*.DesktopClient/GeneratedArtifacts **/*.DesktopClient/ModelManifest.xml **/*.Server/GeneratedArtifacts **/*.Server/ModelManifest.xml _Pvt_Extensions # Paket dependency manager .paket/paket.exe paket-files/ # FAKE - F# Make .fake/ # CodeRush personal settings .cr/personal # Python Tools for Visual Studio (PTVS) __pycache__/ *.pyc # Cake - Uncomment if you are using it # tools/** # !tools/packages.config # Tabs Studio *.tss # Telerik's JustMock configuration file *.jmconfig # BizTalk build output *.btp.cs *.btm.cs *.odx.cs *.xsd.cs # OpenCover UI analysis results OpenCover/ # Azure Stream Analytics local run output ASALocalRun/ # MSBuild Binary and Structured Log *.binlog # NVidia Nsight GPU debugger configuration file *.nvuser # MFractors (Xamarin productivity tool) working folder .mfractor/ # Local History for Visual Studio .localhistory/ # BeatPulse healthcheck temp database healthchecksdb # Backup folder for Package Reference Convert tool in Visual Studio 2017 MigrationBackup/ # Ionide (cross platform F# VS Code tools) working folder .ionide/ # Fody - auto-generated XML schema FodyWeavers.xsd
Gitignore ignore rule:
- Comments are indicated by “#”;
- The directory starts with a slash ‘/’;
- The asterisk “*” is used to match multiple characters;
- The question mark “?” is used to match a single character
- The square bracket “” is used to contain the matching list of single character;
- The exclamation mark “!” indicates that the matched file or directory will not be ignored (tracked);
In addition, GIT matches the rules of. Ignore configuration file from top to bottom by line, which means that if the previous rules match more widely, the later rules will not take effect;
#This is a comment - will be ignored by GIT *. a # ignore all files ending in. A ! lib. A # except lib. A /Todo # just ignore the todo file in the root directory of the project, excluding subdir / todo Build / # ignore all files in the build / directory Doc / *. TXT? Will ignore doc/ notes.txt But Doc / server is not included/ arch.txt
Reference address of the rule: https://blog.csdn.net/sundna/article/details/90749495
To process files that have been submitted to the remote warehouse:
We may not pay attention to add gitignore file configuration at the time of development, and push these files to the remote warehouse. We have the following two solutions:
1. Delete the local files and submit them to the remote end (provided that they are environment variable files. If they cannot be generated automatically, it is not recommended).
2. Use the following git command:
//When we need to delete a file in the temporary store or branch, but we need to use it locally, we just don't want the file to be version controlled and can use it git rm -r --cached file_ Path (file path) // put the file_ Delete path file in the current branch's staging area < br > git add. // submit the current operation local staging area Git commit - M 'Delete remote somefile' // submit to local git repository Git push // submit to remote code base
If I need to remove an obj file from a project and submit it:
The path of the file is: D: development learning master my training camp dailylearning work & learning. Net training camp application obj
Enter the following command to remove related files that do not need to be tracked:
git rm -r --cached Application/obj
After successful execution, the file will be deleted from the branch (it will still exist locally), and finally we can submit it to the remote warehouse.
Here is the article about the details of visual studio using git to ignore files that do not want to upload to the remote warehouse. For more information about git ignoring files that do not want to upload to the remote warehouse, please search previous articles of developer or continue to browse the following related articles. I hope you can support developer more in the future!