Files Not Uploading to Git Visual Studio
preface:
Every bit a. Net developer, we take the nearly 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, considering vs has rich extension tools. Don't talk too much nonsense, simply get to the point. When we utilize VS to develop related. Net projects, we oftentimes find that goose egg has changed in the pull-downward lawmaking, that is, some files need to be submitted after running, such as the most mutual bin / debug, bin / release, obj / debug, obj / release files. Simply I don't want to submit these files to the remote git code remote warehouse. In fact, this is very simple. We merely need to add a new ignore text file (. Gitignore) in the project directory when we first create the project, and then button it to the remote warehouse using GIT.
Files to be ignored:
Configure. Gitignore to ignore files that do not need to exist submitted:
Add the. Gitgnore template of visual studio to the project:
The post-obit is an ignored file template for. Net /. Net core related projects. Any project developed with visual studio can apply information technology:
Gitnore ignores file template source: https://github.com/github/gitignore/blob/master/VisualStudio.gitignore At that place 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 y'all have tasks that create the project'south static files in wwwroot #wwwroot/ # Visual Studio 2017 automobile generated files Generated\ Files/ # MSTest exam 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 # Criterion Results BenchmarkDotNet.Artifacts/ # .Cyberspace Cadre projection.lock.json projection.fragment.lock.json artifacts/ # ASP.Internet Scaffolding ScaffoldingReadMe.txt # StyleCop StyleCopReport.xml # Files congenital past 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 Lawmaking Coverage Tool *.dotCover # AxoCover is a Code Coverage Tool .axoCover/* !.axoCover/settings.json # Coverlet is a gratuitous, cantankerous platform Code Coverage Tool coverage*.json coverage*.xml coverage*.info # Visual Studio lawmaking 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/Assist/*.HxC DocProject/Help/*.hhc DocProject/Help/*.hhk DocProject/Help/*.hhp DocProject/Assist/Html2 DocProject/Help/html # Click-Once directory publish/ # Publish Web Output *.[Pp]ublish.xml *.azurePubxml # Note: Annotate the next line if you want to checkin your web deploy settings, # simply database connection strings (with potential passwords) volition be unencrypted *.pubxml *.publishproj # Microsoft Azure Web App publish settings. Comment the next line if y'all want to # checkin your Azure Web App publish settings, simply sensitive information independent # in these scripts will be unencrypted PublishScripts/ # NuGet Packages *.nupkg # NuGet Symbol Packages *.snupkg # The packages folder can exist ignored because of Package Restore **/[Pp]ackages/* # except build/, which is used equally an MSBuild target. !**/[Pp]ackages/build/ # Uncomment if necessary nonetheless generally it will exist 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 parcel directories and files AppPackages/ BundleArtifacts/ Package.StoreAssociation.xml _pkginfo.txt *.appx *.appxbundle *.appxupload # Visual Studio cache files # files catastrophe in .cache tin 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 stiff name files can present a security risk # (https://github.com/github/gitignore/pull/2483#issue-259490424) #*.snk # Since in that location 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/ # Fill-in & study files from converting an old project file # to a newer Visual Studio version. Backup files are non needed, # because we accept 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-nine]).rdl # Microsoft Fakes FakesAssemblies/ # GhostDoc plugin setting file *.GhostDoc.xml # Node.js Tools for Visual Studio .ntvs_analysis.dat node_modules/ # Visual Studio half-dozen build log *.plg # Visual Studio 6 workspace options file *.opt # Visual Studio six 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/ # Simulated - F# Make .fake/ # CodeRush personal settings .cr/personal # Python Tools for Visual Studio (PTVS) __pycache__/ *.pyc # Cake - Uncomment if yous 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 assay 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 binder .mfractor/ # Local History for Visual Studio .localhistory/ # BeatPulse healthcheck temp database healthchecksdb # Backup folder for Packet 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:
Grammar:
- Comments are indicated by "#";
- The directory starts with a slash '/';
- The asterisk "*" is used to lucifer multiple characters;
- The question mark "?" is used to match a single graphic symbol
- The square subclass "[]" is used to incorporate the matching list of single character;
- The exclamation mark "!" indicates that the matched file or directory will non be ignored (tracked);
In addition, GIT matches the rules of. Ignore configuration file from top to bottom by line, which ways that if the previous rules match more widely, the afterward rules will not take effect;
#This is a annotate - 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 doctor/ notes.txt But Doc / server is not included/ arch.txt Reference accost of the rule: https://blog.csdn.net/sundna/article/details/90749495
To process files that have been submitted to the remote warehouse:
We may non 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:
i. Delete the local files and submit them to the remote end (provided that they are environment variable files. If they cannot be generated automatically, information technology is non recommended).
2. Use the following git command:
//When we need to delete a file in the temporary store or branch, but we demand to use it locally, we just don't desire the file to exist version controlled and tin can use it git rm -r --cached file_ Path (file path) // put the file_ Delete path file in the electric current branch's staging area < br > git add. // submit the electric current operation local staging expanse Git commit - One thousand '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 projection and submit it:
The path of the file is: D: evolution learning master my training military camp dailylearning work & learning. Internet training camp application obj
Enter the following command to remove related files that practise not need to be tracked:
git rm -r --cached Application/obj Afterward successful execution, the file will exist deleted from the branch (information technology volition still be locally), and finally we can submit it to the remote warehouse.
Here is the article nearly the details of visual studio using git to ignore files that do not want to upload to the remote warehouse. For more information virtually git ignoring files that do not want to upload to the remote warehouse, please search previous manufactures of developer or continue to browse the post-obit related articles. I hope you tin back up developer more in the future!
Source: https://developpaper.com/details-of-visual-studio-using-git-to-ignore-files-that-you-dont-want-to-upload-to-remote-warehouse/
0 Response to "Files Not Uploading to Git Visual Studio"
Postar um comentário