Visual Studio 2010,2015期 [英] Visual studio 2010, 2015 issue

问题描述

我在Windows 10中使用vs2015制作了一个解决方案。这在测试和编辑中工作正常。好的。

我的问题有3分：

1-当我在Windows 7上测试我的应用程序时。它运行一分钟然后，得到了一个问题（未处理的例外）。

2-当我在Windows 7中用vs2010 编辑时我遇到了问题：

a）我创建的是在测试中看不到的划痕控件，看到的其他普通控件。

b）我自己的控件继承自另一个基本控件，在编辑中混合他们没有显示，并且得到未处理的异常无法创建我的基本控件的实例。

3-当我在窗口10中编辑时vs2010，它可以工作，但我自己的控件继承自另一个基础，在编辑在未显示的混合中，并且得到未处理的异常无法创建我的基本控件的瞬间。

任何人都可以获得帮助吗？发生什么事了？

注意：我想使用vs2010和windows 7.

I've made a solution in Windows 10 with vs2015. This works fine in testing and editing. OK.
My problem has 3 points:
1- When I tested my app on windows 7. It runs for one minute then, got a problem (Unhandled exception).
2- When I edit it in Windows 7 with vs2010 I've problems:
a) My created from scratch controls not seen on testing, other ordinary controls seen.
b) My own controls are inherited from another base one, on editing in blend they are not shown, and got unhandled exception "Cannot create instance of my base control."
3- When I edit it in window 10 with vs2010, it works but My own controls which inherited from another base one, on editing in blend not shown, and got unhandled exception "Cannot create instant of my base control."
Can any one get help? What's happen?
Note: I want to use vs2010 and windows 7.

推荐答案

在我看来，解决方案1（完美的工作，太过激进而不实用。



我刚刚将VS 2013中创建的解决方案降级到2008年，发现它非常简单。 （不是到2010年，但我会在下面提到它）。这就是我所做的。首先，将项目的目标版本设置为.NET v.3.5（您可能希望使用v.4.0，但我不确定它是否真的需要）。确保它编译为较低的目标版本。然后我从头开始创建VS 2008解决方案，并在文本编辑器中比较2008和2013版本。仅使用版本信息更改了几个字符就足够了 - 降级的解决方案和项目立即与VS 2008一起使用。特别是，如果格式版本，这些更改将在数字中for solution file和 ToolsVersion 项目文件中的XML属性。我不记得确切的细节，只记得这很容易;你最好自己走这条路。



尝试对VS 2015和2010做同样的事情。我相信你会找到一个降低解决方案等级的工作流程和项目。此外，我在CodeProject上看到了一些（过时的）自动降级解决方案。我不再使用它们了，不记得哪一个工作得更好，但我记得其中一个有一些严重的缺陷。无论如何，创建这样的工具并不是什么大问题。



此外，我不明白为什么要使用VS 2010。首先，如果原因是与目标.NET版本的兼容性，则不需要不同的解决方案/项目;您只需要在相同的项目上设置适当的目标版本。从VS 2008开始，所有Visual Studio版本都支持多平台构建。我可以理解你需要降级发表，以涵盖更多的读者。但是，你需要降级到VS 2008甚至2005年。另外，我认为最好的VS版本是2008年和2013/2015，2010年相对较差。这些天，2010年毫无意义;我从我的所有系统中删除了它，但仍然使用了2008.它比2008年更加缓慢，没有2013年和2015年的任何优秀功能。只有当它是支持.NET v.4.0的唯一Microsoft IDE时它才有意义，但是这些日子这个角色在VS 2013或2015年的表现要好得多。



至于未处理的例外，这个问题是无关紧要的，特别是当你没有提供任何异常信息或任何代码。这只是您需要修复的错误。使用调试器。

-SA

In my opinion, Solution 1 (perfectly working, of course) is too radical to be practical.

I just recently down-graded the solution created in VS 2013 to 2008 and found it amazingly easy. (Not to 2010, but I'll mention it below). Here is what I done. First of all, set the projects' target version to .NET v.3.5 (you may want to use v.4.0, but I'm not sure it's really required). Make sure it compiles to the lower target version. Then I created VS 2008 solution from scratch and compared 2008 and 2013 versions in a text editor. Changing just few character with version information turned out to be enough — down-graded solution and projects immediately worked with VS 2008. In particular, those changes are in the number if Format Version for solution file and ToolsVersion XML attributes in project files. I don't remember exact detail, only remember that it was easy; you should better go this way yourself.

Try to do the same with VS 2015 and 2010. I'm sure you will find a workflow to down-grade the solution and projects. Besides, I saw a couple of (obsolete) solution for automatic down-grade on CodeProject. I am not using them anymore and don't remember which one is working better, but I remember that one of them has some serious defects. Anyway, it's not a big deal to create such tool.

Besides, I don't understand why using VS 2010 at all. First of all, if the reason is the compatibility with the target .NET version, you don't need different solution/projects; you only need to set appropriate target versions on the same projects. Starting with VS 2008, all Visual Studio versions support multi-platform build. I can understand that you need down-grading for publication, to cover more readers. But then you would need to down-grade to VS 2008 or even 2005. Also, I think that the best VS versions are 2008 and 2013/2015, and 2010 was relatively bad. These days, 2010 is pointless; I removed it from all my system but still use 2008. It was just slower then slim 2008, without any good features of 2013 and 2015. It made some sense only when it was the only Microsoft IDE to support .NET v.4.0, but these days this role is played much better by VS 2013 or 2015.

As to "unhandled exception", this issues is quite irrelevant, especially when you did not provide any exception information or any code. This is just your bug which you need to fix. Use the debugger.

—SA

如果项目是在VS2015中创建的，我会怀疑你无法将VS2015项目加载到VS2010并期望一切都能完美运行。



如果你想要使用VS2010和Windows 7，为什么要创建在VS2015项目？你真的不太可能找到有经验的人在5年历史的Visual Studio中打开VS2015项目。



我真的建议回VS2015进行调试如果可能的话，使用远程调试工具的问题。



如果你真的想使用VS2010，那么我建议你在2010年重新创建这个项目。

If the project was created in VS2015, I would suspect that you cannot load a VS2015 project into VS2010 and expect everything to work perfectly.

If you "want to use VS2010 and windows 7", why did you create the project on VS2015? It's really unlikely you're going to find anyone with experience opening a VS2015 project in a 5 year old Visual Studio.

I was really suggest going back to VS2015 to debug the problem using the remote debugging tools if at all possible.

If you really want to use VS2010, then I would suggest recreating the project in 2010.

这篇关于Visual Studio 2010,2015期的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！