有这么prevents您使用窗体设计器上的抽象形式的子类，一个著名的bug在Visual Studio。

这个问题已经阐明和解决的最优雅通过的城市土豆。这不是一部分，我有麻烦。麻烦的是，我已经复制了由城市土豆描述的技术，并把它列入我的项目（​​这恰好是pretty的大），现在每次我试图打开我的派生形式设计，并且我得到的微软可怕对不起，老伙计，但我将不得不现在就杀了你的字样（让人想起奥多的的叫万达的一个鱼），上面写着微软Visual Studio 2005中遇到了问题，需要关闭。我们深表歉意。

但这里的真正踢球者：如果你只是忽略消息，和东西它拿走超出屏幕的右下角，您可以继续工作，完全正常！只要不点击发送错误报告或不发送按钮，然后堂妹VS 确实关闭。

不过，这种现象是非常讨厌的，而且我非常希望能够在没有感觉的工作，我的IDE是刚刚的寻找的一段真是可恶的方式来报复我维尼poohing其明智的建议退出了 - 。否则

其它有用的信息：此相同的行为可以在我的办公室的所有其他计算机进行复制;这没有什么具体到我的机器。显然，一些项目/ code也影响了IDE，但至少我知道的设计模式的工作原理，怎么我忽略后坠毁的消息，设计师工作得很好。我只是不知道从哪里开始寻找，是造成这一问题的东西。

任何想法？

谢谢！

如果是我的话，我想尝试附加一个调试器（Visual Studio中的，也许另一个实例），以抛出错误对话框的实例，看看堆栈跟踪给你任何见解是什么导致了错误。

There's a famous bug in Visual Studio that prevents you from using the form designer on a subclass of an abstract form.

This problem has already been elucidated and solved most elegantly by Urban Potato; that's not the part I'm having trouble with. The trouble is, I have duplicated the technique described by Urban Potato, and included it in my project (which happens to be pretty big), and now every time I try to open the designer of my derived form, I get that Microsoft "frightfully sorry, old chap, but I'm going to have to kill you now" message (reminiscent of Otto in A Fish Called Wanda) that says "Microsoft Visual Studio 2005 has encountered a problem and needs to close. We are sorry for the inconvenience."

But here's the real kicker: if you just ignore that message, and stuff it away beyond the bottom right corner of the screen, you can carry on working, perfectly normally! Just don't click the "Send Error Report" or "Don't Send" buttons, coz then VS does close.

Still, this phenomenon is highly annoying, and I'd very much like to be able to work without the feeling that my IDE is just looking for some really nasty way to get back at me for pooh-poohing its sage advice to quit now - or else.

Further useful info: this same behavior can be duplicated on all other computers in my office; it's nothing specific to my machine. Obviously something in the project/code is upsetting the IDE, but at least I know the design pattern works, coz after I ignore the crash message, the designer works perfectly well. I just don't know where to start looking for the thing that is causing this problem.

Any ideas?

Thanks!

If it were me, I'd try attaching a debugger (maybe another instance of Visual Studio) to the instance that throws the error dialog, and see if the stack trace gives you any insights into what's causing the error.