-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git.sln is reported as "corrupt" by Visual Studio 2017 #1507
Comments
Known issue. This is where I am at: master...dscho:fix-vcxproj-generation. I just need more time to work on it. There are higher-priority issues, though. |
This comment was marked as abuse.
This comment was marked as abuse.
CMake has been discussed. On the Git mailing list, as it is appropriate. |
I wouldn't care about this issue but I am getting stuck trying to building within the SDK environment.
|
@AnthonyIacono if you are getting stuck trying to build within the SDK, it would probably make more sense to open a new ticket, and describe your setup as well as the precise error (what command was invoked, full error message) in detail. |
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes git-for-windows#1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We ran out of GUIDs in the script generating Visual Studio project files. This topic branch fixes that issue once and for all, by generating the GUIDs. For extra goodness, we now generate GUIDs that are not random, but are generated from the SHA-256 checksums of the target file of the project. That way, the project<->GUID mapping is stable. This fixes #1507 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
When I open
git.sln
in Visual Studio 2017 (v15.5), I get the following popup:I have the following SHA1 checked out:
4dab739100908644a76f3f06388bd2d250331b89
(tip ofvs/master
). Followed the steps on the Visual Studio wiki page.The text was updated successfully, but these errors were encountered: