Visual Studio 2008 - 移动解决方案文件（sln、suo）
如果最初使用 Web 应用程序项目创建 VS2008 项目，并添加类项目，结构如下：
Parent Folder
Web App Project Folder - (solution Files in this folder)
Class Project 1
Class Project 2
...
您是否发现将 .sln 和 .suo 文件移动到父目录有任何问题？
Parent Folder - (solution Files in this folder)
Web App Project Folder
Class Project 1
Class Project 2
...
我调整了 .sln 项目目录，解决方案似乎工作正常，但我想知道此操作是否会破坏我没有预料到的东西。
If a VS2008 project is created initially with a web app project, and class projects are added, and the structure is like this:
Parent Folder
Web App Project Folder - (solution Files in this folder)
Class Project 1
Class Project 2
...
do you see any problems with moving the .sln and .suo files to the parent directory?
Parent Folder - (solution Files in this folder)
Web App Project Folder
Class Project 1
Class Project 2
...
I adjusted the .sln project directories and the solution seems to be working fine, but I'm wondering if this action will break something I didn't anticipate.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
只有项目文件决定其构建输出 - 解决方案仅将项目链接到一个逻辑实体中，以便它们可以同时加载到 Visual Studio 实例中。如果项目仍然相同，则没有任何问题。
Only the project files determine their build outputs - solutions only link projects together into a logical entity, so that they can be loaded at the same time in a Visual Studio instance. If the projects are still the same, nothing's broken.
并且.suo 文件可以安全删除。它是一个特定于用户的文件，仅保留特定用户的解决方案选项。它不包含对项目、构建设置等重要的内容。
And the .suo file can be safely deleted. It's a user-specific file that simply retains a particular user's options for a solution. It contains nothing that's important to projects, build settings etc.
您可以使用任何您喜欢的编辑器（甚至记事本）打开 .sln 文件，并看到它仅包含对其中项目文件的引用，您可以修改它，以便其中项目文件的相对路径与您的布局匹配。 VS 不会反对它。
所有构建设置都存储在项目文件中，因此您不会丢失在项目中所做的任何配置更改。
You can open your .sln file with whatever editor you'd like, even notepad, and see that it contains only references to your project files in it, you can modify it so that the relative paths to your project files in it match your layout. VS wouldn't have anything against it.
All build settings are stored in project files, so you don't loose any configuration changes you've done in your projects.