Visual Studio 转换向导:如果坏了为什么要放进去?重点是什么? [英] Visual Studio Conversion Wizard: Why put it in if it is broken? Whats the point?

问题描述

我尝试将许多项目从 vb.net 2005 转换为 vb.net 2008，但没有一个成功过.如果这个工具很明显坏了，你认为他们为什么还要费心去包含这个工具?我的意思是，它可以转换一些代码没问题，但我永远无法正确加载设计视图，而且它几乎永远不会编译而不会出错.

I have tried converting many projects from vb.net 2005 to vb.net 2008, and not a single one has ever made it. Why do you think they even bothered to include this tool if it is very clearly broken? I mean, it can convert some code okay, but I can never load Design view properly, and it'll almost never compile without error.

放入损坏的工具有什么意义?我以为 Microsoft 产品总是向后兼容的?在运行向导之前，他们有什么要求吗?

Whats the point in putting in a broken tool? I thought Microsoft products were always backwards-compatible? Do they have any requirements before running the wizard?

推荐答案

通常项目无法编译是因为编译器/语言/环境发生了变化，而不是因为项目文件有任何问题.

Generally projects won't compile because the compiler/language/environment has changed, not because there's anything wrong with the project files.

我通常使用 vspc 来转换项目文件，但我通常是从 vs2008 转换它们到 vs2003，Visual Studio 做不到.

I typically use vspc to convert project files, but I'm usually converting them from vs2008 to vs2003, which Visual Studio cannot do.

这篇关于Visual Studio 转换向导:如果坏了为什么要放进去?重点是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！