从 Visual Studio 2005 迁移到 2008 时需要注意什么？
我们计划将我们的开发人员从 Visual Studio 2005 更新到 2008。在此迁移过程中是否有任何需要注意的常见“问题”？
目前我主要担心的是我们大量使用 WSE 3.0（主要是为了使用外部 .asmx Web 服务，但我们自己也托管一些服务）。 由于 WSE 3.0 已被 WCF 取代，这会成为问题吗？
其他背景信息：具有多个网站的 VB.NET 应用程序，而不是 Web 应用程序。 目前使用 .NET 2.0，并计划很快升级到 3.5。
还有什么我们应该关心的吗？
We're planning on updating our developers from Visual Studio 2005 to 2008. Are there any common "gotchas" to look out for during this move?
My major concern at the moment is that we use WSE 3.0 quite a bit (mostly to consume external .asmx web services, but we also host a few ourselves). Will that be an issue since WSE 3.0 has been replaced by WCF?
Additional background info: VB.NET application with several web sites, not web applications. Currently using .NET 2.0 with plans to upgrade to 3.5 soon as well.
Anything else we should be concerned about?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我发现 VS05-08 迁移非常轻松。 理论上，您应该能够简单地在 VS2008 中打开 2005 解决方案，让它进行转换，然后一切就正常了。 VS2008 允许您“定位”特定版本的 .NET，默认情况下它会继续定位 .NET 2.0。 也就是说，3.5 是一个附加更新，因此如果您更改为 3.5（这只是一个需要更改的下拉框），则任何 .NET 2.0 代码都应该很少或没有重大更改。 我很确定华尔街英语的东西应该“正常工作”。
在实践中，项目模板、依赖项等可能是一个问题。 网站和 Web 应用程序仍然受支持，因此我认为这也不应该成为问题。
最后，备份所有内容，然后在 VS2008 中打开，看看会发生什么。
I've found VS05-08 migration pretty painless. In theory, you should be able to simply open the 2005 solution in VS2008, let it convert, and everything just works. VS2008 lets you 'target' a specific version of .NET, and the default here would be that it continues to target .NET 2.0. That said, 3.5 is an additive update, so there should be little or no breaking changes to any .NET 2.0 code should you change to 3.5 (which is just a drop-down-box to change). I'm pretty sure the WSE stuff should "just work".
In practice, things like project templates, dependencies, etc. could be an issue. Web sites and web applications are still both supported, so I think that shouldn't be an issue either.
In the end, just make a backup of everything, then open in VS2008 and see what happens.
我认为你需要注意的主要问题是团队升级。 升级到新版本的 Visual Studio 后，您也将被迫升级项目文件。 升级完成后，该文件将不再与以前版本的 Visual Studio 兼容。 这意味着你将破坏任何使用以前版本的VS进行开发的人。 最好的建议是升级整个团队。
解决此问题的最佳方法是保留项目文件的 2 个版本。 一个适用于 Visual Studio 的早期版本，另一个适用于当前版本。 这显然有一点开销。 一旦您真正开始使用新的语言功能，这将不再足够，因为新功能可能无法在旧版本的 Visual Studio 中编译。
I think the main issue you have to watch out for is upgrading teams. Once you upgrade to a new version of Visual Studio, you will be forced to upgrade your project files as well. Once the upgrade is complete the file will no longer be compatible with previous versions of Visual Studio. This means that you will break anyone who is using the previous version of VS to develop. The best advise is to upgrade the entire team.
The best way to work around this is to keep 2 versions of the project file around. One for the previous version of Visual Studio and the other for the current. This obviously has a bit of overhead. And Once you actually start using new language features this will no longer be a sufficient as the new features likely won't compile in the old versions of Visual Studio.
ASP.NET 项目（尤其是样式元素）等可视化编辑器中的更改非常不同，一开始可能会令人难以置信的令人沮丧。
The changes in the visual editor for things like ASP.NET projects (especially when it comes to styling elements) is very different and can be incredibly frustrating at first.