当前位置： 文江博客话题详情

“所选文件不是有效的解决方案文件”尝试开源安全数据库时出错

发布于 2024-10-17 17:37:25 字数 4214 浏览 8 评论 0原文

我最近重新构建了我的开发机器，现在使用 Windows 7。在这台新机器上，VS 2010 无法再直接从 SS 2005 打开 sln 文件。这些是有效的 2010 解决方案（最初使用 VS 2010 创建），工作正常，直到我重新-建造了我的机器。我的同事也有同样的设置，没有这个问题。

我收到的消息是“所选文件不是有效的解决方案文件”。

我已经重建了很多次并使用了很多次 VS 安装，并且使用 VS 05、08 或 10 从 SS 打开 sln 从来没有遇到过问题。我以前从未见过这种情况。我的同事也没有遇到过这个问题，

我已经重新安装了 SS 2005 以及最新的 SS 更新，但没有任何效果。

VS 2010 可以很好地从文件系统打开解决方案，所以它一定是 SS 的东西。

有什么想法吗？

编辑解决方案文件的内容：

Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MyProject", "MyProjectX\MyProject.csproj", "{8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MyProject_BL", "MyProject_BLMyProject_BL.csproj", "{595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "LinqKit", "LINQKit\LinqKit.csproj", "{AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MyProject_DL", "MyProject_DL\MyProject_DL.csproj", "{55506B29-70A8-4556-ADF9-2553B0F18379}"
EndProject
Global
    GlobalSection(SourceCodeControl) = preSolution
        SccNumberOfProjects = 5
        SccLocalPath0 = .
        SccProjectUniqueName1 = MyProject\\MyProject.csproj
        SccProjectName1 = \u0022$/MyProject.root/MyProject/MyProject\u0022,\u0020
        SccLocalPath1 = MyProject
        SccProjectUniqueName2 = MyProject_BL\\MyProject_BL.csproj
        SccProjectName2 = \u0022$/MyProject.root/MyProject/MyProject_BL\u0022,\u0020
        SccLocalPath2 = MyProject_BL
        SccProjectUniqueName3 = LINQKit\\LinqKit.csproj
        SccProjectName3 = \u0022$/MyProject.root/MyProject/LINQKit\u0022,\u0020
        SccLocalPath3 = LINQKit
        SccProjectUniqueName4 = MyProject_DL\\MyProject_DL.csproj
        SccProjectName4 = \u0022$/MyProject.root/MyProject/MyProject_DL\u0022,\u0020JNAAAAAA
        SccLocalPath4 = MyProject_DL
    EndGlobalSection
    GlobalSection(SolutionConfigurationPlatforms) = preSolution
        Debug|Any CPU = Debug|Any CPU
        Release|Any CPU = Release|Any CPU
    EndGlobalSection
    GlobalSection(ProjectConfigurationPlatforms) = postSolution
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Release|Any CPU.Build.0 = Release|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Release|Any CPU.Build.0 = Release|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Release|Any CPU.Build.0 = Release|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Release|Any CPU.Build.0 = Release|Any CPU
    EndGlobalSection
    GlobalSection(SolutionProperties) = preSolution
        HideSolutionNode = FALSE
    EndGlobalSection
EndGlobal

采取的措施：

第 1 步： 文件->打开项目/解决方案

在此处输入图像描述

步骤 2： 在左侧菜单中选择 SourceSafe。您现在可以看到存储在 sourcesafe 中的 ss_IssueTrak 数据库 在此处输入图像描述

步骤 3： 导航到解决方案 IssueTrakX.sln 在此处输入图像描述

步骤 4： 单击打开或双击 IssueTrakX.sln 并收到此错误 在此处输入图像描述

原文

I recently re-built my development machine which now uses windows 7. On this new machine, VS 2010 can no longer open sln files directly from SS 2005. These are valid 2010 solutions (orginally created witih VS 2010) that worked fine until I re-built my machine. My co-workers have the same setup and do not have this problem.

The message I get is "The selected file is not a valid solution file".

I've re-built many times and used many installs of VS and never had a problem opening sln's from SS using VS 05, 08 or 10. I've just never seen this before. My co-workers have not had this problem either

I have re-installed SS 2005 as well as the latest SS update but nothing works.

VS 2010 can open solutions from the file system just fine, so it must be a SS thing.

Any ideas?

Edit for contents of Solution file:

Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MyProject", "MyProjectX\MyProject.csproj", "{8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MyProject_BL", "MyProject_BLMyProject_BL.csproj", "{595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "LinqKit", "LINQKit\LinqKit.csproj", "{AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MyProject_DL", "MyProject_DL\MyProject_DL.csproj", "{55506B29-70A8-4556-ADF9-2553B0F18379}"
EndProject
Global
    GlobalSection(SourceCodeControl) = preSolution
        SccNumberOfProjects = 5
        SccLocalPath0 = .
        SccProjectUniqueName1 = MyProject\\MyProject.csproj
        SccProjectName1 = \u0022$/MyProject.root/MyProject/MyProject\u0022,\u0020
        SccLocalPath1 = MyProject
        SccProjectUniqueName2 = MyProject_BL\\MyProject_BL.csproj
        SccProjectName2 = \u0022$/MyProject.root/MyProject/MyProject_BL\u0022,\u0020
        SccLocalPath2 = MyProject_BL
        SccProjectUniqueName3 = LINQKit\\LinqKit.csproj
        SccProjectName3 = \u0022$/MyProject.root/MyProject/LINQKit\u0022,\u0020
        SccLocalPath3 = LINQKit
        SccProjectUniqueName4 = MyProject_DL\\MyProject_DL.csproj
        SccProjectName4 = \u0022$/MyProject.root/MyProject/MyProject_DL\u0022,\u0020JNAAAAAA
        SccLocalPath4 = MyProject_DL
    EndGlobalSection
    GlobalSection(SolutionConfigurationPlatforms) = preSolution
        Debug|Any CPU = Debug|Any CPU
        Release|Any CPU = Release|Any CPU
    EndGlobalSection
    GlobalSection(ProjectConfigurationPlatforms) = postSolution
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {8E519F6C-A405-43AB-ADA0-F4829ECBEFE0}.Release|Any CPU.Build.0 = Release|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {595FFFB2-5CC3-40BB-9059-32ACFAA9DEFA}.Release|Any CPU.Build.0 = Release|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {AEC98F52-83F5-488D-99EF-8AFFE7C9F6E6}.Release|Any CPU.Build.0 = Release|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Debug|Any CPU.Build.0 = Debug|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Release|Any CPU.ActiveCfg = Release|Any CPU
        {55506B29-70A8-4556-ADF9-2553B0F18379}.Release|Any CPU.Build.0 = Release|Any CPU
    EndGlobalSection
    GlobalSection(SolutionProperties) = preSolution
        HideSolutionNode = FALSE
    EndGlobalSection
EndGlobal

Actions taken:

Step 1:
File -> Open Project/Solution

enter image description here

Step 2:
Select SourceSafe on left menu. You can now see ss_IssueTrak database stored in sourcesafe
enter image description here

Step 3:
Navigate to Solution IssueTrakX.sln
enter image description here

Step 4:
Click Open or double click IssueTrakX.sln and receive this error
enter image description here

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论， 你可以免费 注册 一个本站的账号。

评论（8）

绾颜 2024-10-24 17:37:25

您必须更改权限

，右键单击父文件夹 => 属性 =>; 安全性 => （编辑）按钮=> （添加）按钮=> （高级）按钮=> （立即查找）button=>
现在选择：每个人
=> 好的 => 好的 =>现在你必须让它完全控制=>完全控制=允许
=> 好的

现在让它应用于所有子文件夹和文件

已完成

you have to change permission

right click on parentfolder=>properties => security => (edit) button => (add) button => (advanced) button => (find now) button=>
and now select : Everyone
=> ok => ok => Now you have to allow it full control=> Full control = Allow
=> ok

now let it to apply for all of subfolders and files

FINISHED

回复 原文
吹梦到西洲 2024-10-24 17:37:25

我在安装 Windows 7 后也遇到过类似的错误消息。原来是 Visual Studio 的某些功能尚未安装。它可能是一个服务包或 EF4。安装后，我就可以打开解决方案文件。然后，我还收到“此安装不支持该项目类型”，直到我安装了一些其他更新，例如 MVC3。

我认为解决方案文件包含未修补的 Visual Studio 无法识别的信息。

I've had a similar error message after installing Windows 7. Turns out that some features of Visual Studio were not yet installed. It might have been a service pack or EF4. Once that was installed, I was able to open the solution file. Then, I was also getting "The project type is not supported by this installation" until I installed some other updates, like for MVC3.

I presume that the solution file had information that the un-patched Visual Studio did not recognize.

回复 原文
小霸王臭丫头 2024-10-24 17:37:25

就我而言，当我的解决方案中的文件名对于我想要下载解决方案的路径来说太长时，会出现消息“所选文件不是有效的解决方案文件”。将解决方案文件夹直接放在 C:\ 驱动器下或靠近 C 驱动器的文件夹解决了我的问题。

In my case, the message "The selected file is not a valid solution file" occurred when there were file names in my solutions that were too long for the path where i wanted to download the solution. Putting the solution folder directly under the C:\ drive or a folder short to the C-drive solved my problem.

回复 原文
白昼 2024-10-24 17:37:25

对我来说，这个解决方案非常完美：

在 Visual Studio 中创建新项目（新项目名称应与主项目名称相同）并删除新解决方案中任何默认创建的项目。现在转到新项目位置并复制 .sln 文件。转到主项目位置并删除 .sln 文件并粘贴复制的 .sln 文件并打开，然后再次重新构建解决方案。

注意：如果遇到有关项目清单的任何错误，您可以编辑.csproj（通过记事本）并删除与清单相关的任何标签并保存。再次重新加载解决方案。

对我来说这有效。

For me this solution worked perfect:

Create new project in visual studio(new project name should be same as main projct name) and delete any default created project in new solution. now go to new project location and copy .sln file. go to main project location and delete .sln file and paste copied .sln file and open, than rebiuld solution again.

Note: if faced any erorr about project manifest you can edit .csproj(by notepad) and delete any tag related to manifet and save. again reload solution.

For me this worked.

回复 原文
多谢你的绝情让我学会死心 2024-10-24 17:37:25

.sln 文件的主要问题。只需使用默认的 .sln 代码编辑它即可。就像这个在此处输入图片描述

The main problem of .sln file. just edit it with your default .sln code. like this one enter image description here

回复 原文
梦行七里 2024-10-24 17:37:25

我进入包含文件夹，在 Visual Studio 中打开 .csproj 文件，这导致解决方案重新加载，并且我不再遇到错误。

I went into the containing folder, I opened the .csproj file in visual studio which caused the solution to reload and I no longer had the error.

回复 原文
芸娘子的小脾气 2024-10-24 17:37:25

备份现有项目并将其删除，然后从版本控制重新下载源代码。这个步骤对我有用

Have a backup for existing project and delete it and re-download source code from version control. this steps worked for me

回复 原文
盛夏尉蓝 2024-10-24 17:37:25

在 Visual Studio File>Project from Existing Code 中，导航到包含 .sln 的根文件夹并将其所有内容添加到新项目中。一切都应该加载到您的新解决方案中。

In Visual Studio File>Project from Existing Code, then navigate to the Root folder containing the .sln and add all of it's contents to your new project. Everything should load in your new solution.

回复 原文
~没有更多了~

关于作者

你在看孤独的风景

暂无简介

0 文章
0 评论
23 人气
发私信

相关话题

更多

热门标签

操作系统 程序设计 IT运维 Linux系统管理 JavaScript 服务器应用 solaris C/C++ PHP Shell BSD Vue.js aix Oracle Python HTML 系统管理 HTML5 CSS 前端
更多

推荐作者

離殇

文章 0 评论 0

小姐丶请自重

文章 0 评论 0

Aik

文章 0 评论 0

国产ˉ祖宗

文章 0 评论 0

猥琐帝

文章 0 评论 0

半仙

文章 0 评论 0

更多

友情链接

文江博客
    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
    原文