blocks|key|1508773|text|VB6作为一个代码库(即文本文件)有什么不同，使得它不适合于git？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1508774|文化完全是另一回事:如果您有许多无能的开发人员无法处理命令行，那么解决方法可能包括尽可能地逃离VB6。|1508775|唯一的潜在问题是，git世界中的窗口多少有点像二等公民。如果你发现git在你的环境中不能很好的工作，你可能想试试集市或者变化莫测。|1508776|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

What's so different about VB6 as a code base (i.e. text files) that makes it not suitable for git?

The culture is another matter altogether: if you have plenty of incompetent developers who can't handle the command line, the cure would probably include running away from VB6 as far as you can.

The only potential problem is that windows in the git world is somewhat of a second class citizen. You might wanna try bazaar or mercurial if you find git doesn't work very well in your environment.

blocks|key|3032740|text|你最了解你的开发者。他们介意使用命令行吗？他们热衷于IDE集成吗？这些都是个人喜好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3032741|确保最受尊敬的开发人员理解git的好处，并支持这一决定。|3032742|请注意，一些VB6源文件是二进制文件和不应该被合并文件:例如，.frx文件。我不知道吉特，所以我不知道这是不是个问题。|offset|length|style|CODE|3032743|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/322488/how-do-you-deal-with-visual-basic-6-frm-and-frx-files-in-source-control^0|0|0|V|4|J|6|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@$F|U|G|V|H|I]]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

You know your developers best. Will they mind using the command line? Are they keen on IDE integration? These are personal preferences. 

Make sure the most respected developers understand the benefits of git and are behind the decision. 

Do be aware that some VB6 source files are binary and <a href="https://stackoverflow.com/questions/322488/how-do-you-deal-with-visual-basic-6-frm-and-frx-files-in-source-control">shouldn't ever be merged</a>: e.g. <code>.frx</code> files. I don't know git, so I don't know whether that's a problem.

blocks|key|3032773|text|使用Git来管理VB6项目已经有一年了。从未见过任何IDE集成。就我个人而言，我喜欢命令行，所以我不太喜欢它。我遇到的两个主要问题是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3032774|VB6+IDE不监视项目文件，如果其中任何文件是外部更改的(例如使用“git重置”、“git签出”)，则需要重新打开项目以反映更改。|ordered-list-item|3032775|VB6+IDE有时会在加载项目时更改事件参数或变量的情况，因此使用“git-所有”是不安全的，除非您需要大量的垃圾来处理代码更改。|3032776|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|K|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Been using Git to manage VB6 projects for about a year now. Never came across any IDE integration. Personally I like the command line, so I've not been looking much. The two major issues I've encountered are:

<ol>
<li>VB6 IDE doesn't monitor the project files, if any of them is changed externally (e.g. using 'git reset', 'git checkout') then the project needs to be re-opened to reflect the changes.</li>
<li>VB6 IDE will sometimes change the case of event parameters or variables when loading a project, so it's never safe to use 'git commit --all' unless you want a lot of garbage with your code changes.</li>
</ol>

blocks|key|1283897|text|我们要这么做。我们在.gitIgnore中添加了以下内容|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1283898|*.csi|unordered-list-item|1283899|*.exp|1283900|*.lib|1283901|*.lvw|1283902|*.vbw|1283903|MyProject.dll|1283904|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

We are doing this. We have added the following to .gitIgnore

<ul>
<li>*.csi</li>
<li>*.exp</li>
<li>*.lib</li>
<li>*.lvw</li>
<li>*.vbw</li>
<li>MyProject.dll</li>
</ul>

blocks|key|1283906|text|您必须创建文件.gitattributes才能使用windows行尾(crlf)，因为git是在unix中诞生的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1283907|#+Declare+files+that+will+always+have+CRLF+line+endings+on+checkout.
*.vbp+text+eol=crlf
*.frm+text+eol=crlf
*.cls+text+eol=crlf
*.bas+text+eol=crlf
*.dsr+text+eol=crlf
*.ini+text+eol=crlf

#+Denote+all+files+that+are+truly+binary+and+should+not+be+modified.
*.frx+binary
*.exe+binary
*.dll+binary
*.ocx+binary|code-block|syntax|javascript|1283908|还可以使用以下行创建.gitignore文件：|1283909|##+Ignore+Visual+Studio+temporary+files,+build+results,+and
##+files+generated+by+popular+Visual+Studio+add-ons.

#+User-specific+files
*.vbw
*.tmp
*.scc
*.dca|1283910|entityMap^0|7|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

You have to create the file .gitattributes to use windows line endings (crlf) because git was born in unix.

<pre><code># Declare files that will always have CRLF line endings on checkout.
*.vbp text eol=crlf
*.frm text eol=crlf
*.cls text eol=crlf
*.bas text eol=crlf
*.dsr text eol=crlf
*.ini text eol=crlf

# Denote all files that are truly binary and should not be modified.
*.frx binary
*.exe binary
*.dll binary
*.ocx binary
</code></pre>

Also create .gitignore file with the following lines:

<pre><code>## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.

# User-specific files
*.vbw
*.tmp
*.scc
*.dca
</code></pre>

blocks|key|3032818|text|在我们的情况下，我找到了这个解决方案。它为以前的答案添加了更多内容，解决了我们所有的许多问题，使我们的项目能够与git一起工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3032819|.gitattributes|offset|length|style|BOLD|3032820|#+Set+the+default+behavior,+in+case+people+don't+have+core.autocrlf+set.
*+text+eol=auto
*.bas+text+eol=crlf
*.frm+text+eol=crlf
*.log+text+eol=crlf
*.vbp+text+eol=crlf
*.cls+text+eol=crlf
*.vbw+text+eol=crlf
*.dsr+text+eol=crlf
*.ini+text+eol=crlf
*.res+binary
*.RES+binary
*.frx+binary
*.exe+binary
*.dll+binary
*.ico+binary
*.gif+binary
*.ocx+binary
*.tlb+binary
*.ocx.bin+binary
*.ism+binary
*.bin+binary
*.aps+binary
*.ncb+binary
*.exe.compat+binary
*.ocx.compat+binary|code-block|syntax|javascript|3032821|.gitignore|3032822|.DS_Store
.Trashes
*.vbw
*.csi
*.exp
*.lib
*.lvw
*.dca
*.scc
*.tmp
<name+of+built+binary,+exe,+dll+or+ocx>|3032823|entityMap^0|0|0|E|0|0|0|A|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

I found this solution to work in our situation. It adds a bit more to the previous answers and solved all of our MANY issues getting our project to work with git.

.gitattributes

<pre><code># Set the default behavior, in case people don't have core.autocrlf set.
* text eol=auto
*.bas text eol=crlf
*.frm text eol=crlf
*.log text eol=crlf
*.vbp text eol=crlf
*.cls text eol=crlf
*.vbw text eol=crlf
*.dsr text eol=crlf
*.ini text eol=crlf
*.res binary
*.RES binary
*.frx binary
*.exe binary
*.dll binary
*.ico binary
*.gif binary
*.ocx binary
*.tlb binary
*.ocx.bin binary
*.ism binary
*.bin binary
*.aps binary
*.ncb binary
*.exe.compat binary
*.ocx.compat binary
</code></pre>

.gitignore

<pre><code>.DS_Store
.Trashes
*.vbw
*.csi
*.exp
*.lib
*.lvw
*.dca
*.scc
*.tmp
&lt;name of built binary, exe, dll or ocx&gt;
</code></pre>

blocks|key|3032891|text|这确实是对KeithTheBiped其他优秀评论的补充，等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3032892|但是，有可能在某种程度上强迫VB6中的即时窗口像现代终端窗口一样运行，但有一些注意事项。如果我们创建一个帮助函数来运行命令，那么以某种方式捕获输出，然后使用Debug.Print将其转发回与终端窗口类似的即时窗口，当然没有任何交互元素。|3032893|这对于大多数命令都有效，但无法捕获git+push阶段的一些输出。一个可接受的折衷方案，以方便无壳(国际海事组织)。|offset|length|style|CODE|3032894|我们可以使用命令提示符(cmd.exe+/c)，使用针对临时文件的1>和2>管道。我不提供几个基本功能，但如果您还没有这些功能，我会提供它们的源代码。|3032895|考虑以下职能：|3032896|Public+Function+RunCmdToOutput(ByVal+cmd+As+String,+Optional+ByRef+ErrStr+As+String+=+"")+As+String
Const+p_enSW_HIDE+=+0

On+Error+GoTo+RunError

++Dim+A+As+String,+B+As+String
++A+=+TempFile
++B+=+TempFile

++ShellAndWait+"cmd+/c+"+&+cmd+&+"+1>+"+&+A+&+"+2>+"+&+B,+p_enSW_HIDE

++RunCmdToOutput+=+ReadEntireFileAndDelete(A)
++ErrStr+=+ReadEntireFileAndDelete(B)

++Exit+Function

RunError:
++RunCmdToOutput+=+""
++ErrStr+=+"ShellOut.RunCmdToOutput:+Command+Execution+Error+-+["+&+Err.Number+&+"]+"+&+Err.Description
End+Function|code-block|syntax|javascript|3032897|你需要：|3032898|TempFile+-返回程序具有读写权限的唯一和不存在的文件名。它可能应该使用GetShortPathName+API缩短长路径名。|unordered-list-item|3032899|ShellAndWait+--标准“启动一个进程并等待它退出”。|3032900|ReadEntireFileAndDelete+-就像它说的.抓取内容，删除文件，返回字符串。|3032901|一旦您完成了这一任务，并且可以成功地将任何简单的执行和输出运行到即时窗口，如下所示：|3032902|?runcmdtooutput("ver")
Microsoft+Windows+[Version+10.0.16299.309]|3032903|从这里开始，您可以运行Git，并将大部分内容显示到即时窗口中，并且可以简单地使用它，但我们可以做得更好。|3032904|假设您已经安装了一个命令行Git并更新了path以使其可用，那么您可以创建一些新的函数(希望在一个模块中)：|3032905|Private+Function+GitCmd(ByVal+C+As+String,+Optional+ByVal+NoOutput+As+Boolean+=+False)+As+String
++Dim+ErrSt+As+String
++GitCmd+=+RunCmdToOutput(C,+ErrSt)
++If+Not+NoOutput+Then+Debug.Print+GitCmd+'+Because+it+also+returns+the+string
++If+ErrSt+<>+""+Then+Debug.Print+"ERR:+"+&+ErrSt
End+Function

Public+Function+Git(ByVal+C+As+String)+As+Boolean
++GitCmd+"git+"+&+C
++Git+=+True
End+Function|3032906|在这里，您几乎可以从即时窗口运行Git命令。请记住，Git()是一个函数，所以必须将参数作为字符串传递.只有一个必要的角色。当然，VB会自动完成一个字符串，所以你不需要拖尾，但我会包括它。使用以下语法：|3032907|Git+"status"
Git+"add+."
Git+"commit+-m+""Some+Git+Commit"""
Git+"pull+-r"
Git+"push"|3032908|它不允许交互式git命令(git+add+-p)，但是，您可以强制它(git+add+.+-f)。但是，这些命令运行并直接将它们的输出显示到即时窗口中，而无需做太多其他工作。|3032909|git+"status"
On+branch+master
Your+branch+is+up+to+date+with+'origin/master'.

Changes+not+staged+for+commit:
++(use+"git+add+<file>..."+to+update+what+will+be+committed)
++(use+"git+checkout+--+<file>..."+to+discard+changes+in+working+directory)
...|3032910|你明白了吧。|3032911|从那里，你也可以自动化的事情。创建帮助函数来批处理常用的Git命令等，或者只是消除一些笨拙的语法。使用RunCmdToOutput，您还可以重新处理其中的一些内容，以便使用MsgBox+(如果愿意的话)，但我认为即时窗口是足够直观的。|3032912|在某个时候限制任何函数仅在IDE中运行也很重要，但这是可选的。|3032913|Public+Function+IsIDE()+As+Boolean
++On+Error+GoTo+IDEInUse
++Debug.Print+1+\+0+'division+by+zero+error+-+Debug+is+ignored+by+compile
++IsIDE+=+False
++Exit+Function
IDEInUse:
++IsIDE+=+True
End+Function

Public+Function+GitStatus()
++If+Not+IsIDE+Then+Exit+Function
++GitCmd+"git+status"
++GitStatus+=+True
End+Function|3032914|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vbforums.com/showthread.php?707489-RESOLVED-GetShortPathName-not-working-help!|1|https://stackoverflow.com/questions/5685972/how-to-wait-for-a-shell-process-to-finish-before-executing-further-code-in-vb6^0|0|0|H|8|0|C|A|X|2|10|2|0|0|0|0|13|K|0|0|0|C|1|0|0|0|0|0|0|0|0|0|D|A|Z|C|0|0|0|1F|E|0|0|0^^$0|@$1|2|3|4|5|6|7|21|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|22|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|23|8|@$F|24|G|25|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|26|8|@$F|27|G|28|H|I]|$F|29|G|2A|H|I]|$F|2B|G|2C|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|2D|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|2E|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|2F|8|@]|9|@]|A|$]]|$1|U|3|V|5|W|7|2G|8|@]|9|@$F|2H|G|2I|1|2J]]|A|$]]|$1|X|3|Y|5|W|7|2K|8|@]|9|@$F|2L|G|2M|1|2N]]|A|$]]|$1|Z|3|10|5|W|7|2O|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2P|8|@]|9|@]|A|$]]|$1|13|3|14|5|P|7|2Q|8|@]|9|@]|A|$Q|R]]|$1|15|3|16|5|6|7|2R|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|2S|8|@]|9|@]|A|$]]|$1|19|3|1A|5|P|7|2T|8|@]|9|@]|A|$Q|R]]|$1|1B|3|1C|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|P|7|2V|8|@]|9|@]|A|$Q|R]]|$1|1F|3|1G|5|6|7|2W|8|@$F|2X|G|2Y|H|I]|$F|2Z|G|30|H|I]]|9|@]|A|$]]|$1|1H|3|1I|5|P|7|31|8|@]|9|@]|A|$Q|R]]|$1|1J|3|1K|5|6|7|32|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|33|8|@$F|34|G|35|H|I]]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|36|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|P|7|37|8|@]|9|@]|A|$Q|R]]|$1|1R|3|-4|5|6|7|38|8|@]|9|@]|A|$]]]|1S|$1T|$5|1U|1V|1W|A|$1X|1Y]]|1Z|$5|1U|1V|1W|A|$1X|20]]]]

This really is an addition to the other excellent comments by KeithTheBiped, et al...

But, it is possible to somewhat coerce the Immediate Window in VB6 to act like a modern terminal window, with some caveats. If we create a helper function to run the command, capture the output somehow, and then use Debug.Print to relay that back to the Immediate window SIMILAR to the terminal window, but without any interactive elements, of course.

This works for most commands, but fails to capture some of the output in the <code>git push</code> phase. An acceptable compromise, for the convenience of no shell (imo).

We can do just that using the the command prompt (<code>cmd.exe /c</code>) using the <code>1&gt;</code> and <code>2&gt;</code> pipes aimed at temporary files. I don't supply a couple underlying functions, but provide sources if you don't have them already.

Consider the following function:

<pre><code>Public Function RunCmdToOutput(ByVal cmd As String, Optional ByRef ErrStr As String = "") As String
Const p_enSW_HIDE = 0

On Error GoTo RunError

 Dim A As String, B As String
 A = TempFile
 B = TempFile

 ShellAndWait "cmd /c " &amp; cmd &amp; " 1&gt; " &amp; A &amp; " 2&gt; " &amp; B, p_enSW_HIDE

 RunCmdToOutput = ReadEntireFileAndDelete(A)
 ErrStr = ReadEntireFileAndDelete(B)

 Exit Function

RunError:
 RunCmdToOutput = ""
 ErrStr = "ShellOut.RunCmdToOutput: Command Execution Error - [" &amp; Err.Number &amp; "] " &amp; Err.Description
End Function
</code></pre>

You will need:

<ul>
<li>TempFile - Return a unique and non-existant file-name that your program has read/write access to. It should probably use the <a href="http://www.vbforums.com/showthread.php?707489-RESOLVED-GetShortPathName-not-working-help!" rel="noreferrer">GetShortPathName API</a> to shorten long path names.</li>
<li><a href="https://stackoverflow.com/questions/5685972/how-to-wait-for-a-shell-process-to-finish-before-executing-further-code-in-vb6">ShellAndWait</a> - The standard "start a process and wait for it to exit".</li>
<li>ReadEntireFileAndDelete - Just what it says... Grab the contents, delete the file, return the string.</li>
</ul>

Once you have accomplished this and can successfully run any simple executing and output into the Immediate window like this:

<pre><code>?runcmdtooutput("ver")
Microsoft Windows [Version 10.0.16299.309]
</code></pre>

From here, you can run Git, and display MOST things into the Immediate window, and could use it as simple as that, but we can do better.

Assuming you have already installed a command-line Git and the path is updated so that it is available, you can create a few new functions (hopefully in a module):

<pre><code>Private Function GitCmd(ByVal C As String, Optional ByVal NoOutput As Boolean = False) As String
 Dim ErrSt As String
 GitCmd = RunCmdToOutput(C, ErrSt)
 If Not NoOutput Then Debug.Print GitCmd ' Because it also returns the string
 If ErrSt &lt;&gt; "" Then Debug.Print "ERR: " &amp; ErrSt
End Function

Public Function Git(ByVal C As String) As Boolean
 GitCmd "git " &amp; C
 Git = True
End Function
</code></pre>

From here, you can ALMOST run Git commands from the immediate window. Remember, Git() is a function, so you have to pass in the argument as a string... Just one necessary character. Of course, VB will auto-complete a string, so you don't NEED the trailing quite, but I'll include it. Use the syntax:

<pre><code>Git "status"
Git "add ."
Git "commit -m ""Some Git Commit"""
Git "pull -r"
Git "push"
</code></pre>

It doesn't allow interactive git commands (<code>git add -p</code>), but, you could just brute-force it (<code>git add . -f</code>). But, the commands run and directly display their output into the Immediate window without much other effort.

<pre><code>git "status"
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
 (use "git add &lt;file&gt;..." to update what will be committed)
 (use "git checkout -- &lt;file&gt;..." to discard changes in working directory)
...
</code></pre>

You get the idea.

From there, you can also automate things. Create helper functions to batch commonly used Git commands, etc, or just eliminate some of the clunky syntax. With <code>RunCmdToOutput</code>, you can also re-work some of it to use the MsgBox, if preferred, but I thought the Immediate Window was intuitive enough.

It might also be important at some point to restrict any functions to only run in the IDE, but that's optional.

<pre><code>Public Function IsIDE() As Boolean
 On Error GoTo IDEInUse
 Debug.Print 1 \ 0 'division by zero error - Debug is ignored by compile
 IsIDE = False
 Exit Function
IDEInUse:
 IsIDE = True
End Function

Public Function GitStatus()
 If Not IsIDE Then Exit Function
 GitCmd "git status"
 GitStatus = True
End Function
</code></pre>

blocks|key|1285279|text|我正在使用Atlassian源代码树来管理我在git存储库中的VB6项目。效果很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1285280|如前所述，一个障碍是，当在IDE中定义了标识符时，IDE就会关闭，并更改匹配标识符的情况，而这些标识符产生的变化都是虚假的。|1285281|解决方案是在文本文件中保留一个标识符块，并根据需要将它们放入每个文件的(General)+(声明)部分，如下所示：|1285282|#If+False+Then
++++Dim+Index+
++++Dim+T+
++++Dim+Ctrl
++++Dim+C+
#End+If|code-block|syntax|javascript|1285283|这将迫使索引的所有实例都成为Index，等等。如果您看到一堆IDE编辑以代码更改的形式出现，您只需粘贴到标准大小写中，然后再次保存文件。|1285284|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I am using Atlassian Source tree to manage my VB6 projects in git repositories. Works fine.
As mentioned, one hurdle is that when an identifier is defined in the IDE, the IDE goes off and changes the case of matching identifiers and these produce screeds of changes that are all spurious.
The solution is to keep a block of identifiers in a text file and slap them into the (General) (Declarations) part of each file as needed like this:
<pre><code>#If False Then
 Dim Index 
 Dim T 
 Dim Ctrl
 Dim C 
#End If
</code></pre>
This will force all instances of index to be Index, etc. If you get a bunch of IDE edits appearing as code changes, you simply paste in the standard casing, and save the file again.

Our company has a large codebase in VB6, and we currently use VSS which, for all that we hate about it, at least integrates into the VB6 IDE.

My own team, which is using .NET, are now looking into alternative SCMs like my personal favourite, Git. With <a href="http://sourceforge.net/projects/gitextensions/" rel="noreferrer">Git Extensions</a>, it seems we will be able to integrate Git commands into the Visual Studio IDE pretty well.

However, the question has been asked: could Git be used for our VB6 codebase too?

Of course I assume the files themselves would work fine in git repositories, but no doubt developers would complain if they had to use the command-line to do all their source control. But has anyone had any experience using VB6 and Git? Any integration available from within the VB6 IDE? Or is it perhaps not that much of a hassle to not have the IDE integration?

And do I get a badge for being the first to create the absurd tag combination of [vb6] and [git]?

Using Git with VB6

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我们公司在VB6中有一个很大的代码库，我们目前使用的是VSS，尽管我们讨厌它，但它至少集成到了VB6 IDE中。我自己的团队正在使用.NET，现在正在研究替代的SCM，比如我个人最喜欢的Git。使用，我们似乎能够很好地将Git命令集成到Visual中。然而，有人提出了这样的问题: Git也能用于我们的VB6代码库吗？当...

问在VB6中使用Git
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在VB6中使用GitEN