在vb.net Windows窗体中打开特定窗体是有问题的 [英] Opening of a particular form is problem in vb.net windows form

问题描述

大家好
我有一个基于VSS的Windows应用程序.我正在尝试打开显示错误"7285E.tmp"的特定表单，但它没有打开设计表单，但其他表单也在打开.为什么这样做，我不明白，请帮助?

[edit]紧急情况已删除:这可能对您来说很紧急，但对我们而言并非如此.您所强调的紧迫性只是使我们认为您离开得太晚了，并希望我们为您做这件事.这使某些人烦恼，并且可能会减慢响应速度.
-OriginalGriff [/edit]
的确，这很紧迫，但对其他人却不然.我的目的不是要让别人为我的问题烦恼，对此我深表歉意.
-Indrajit Dasgupta [/edit]

Hi All
I have a windows based application which is in VSS. I m trying to open a particular form which is showing error "7285E.tmp" it does not open the design form but other forms are opening.Why it is doing so I didn''t understand please help?

[edit]Urgency deleted: It may be urgent to you, but it isn''t to us. All that your stressing the urgency does is to make us think you have left it too late, and want us to do it for you. This annoys some people, and can slow a response.
- OriginalGriff[/edit]
It is true that it urgent but not for others. My intention is not to that to break others head for my problem I apologies for that.
-Indrajit Dasgupta[/edit]

推荐答案

原则上我不能回答这个问题，因为可能有很多原因导致此类问题.这个问题很常见.

我只想就今后如何避免类似问题提供一些建议.

首先，很高兴您提到VSS.您当然需要在版本控制下完成所有工作，尤其是对于表单.由于很容易弄乱表格，因此，将先前的更改提交到修订控制系统后，应开始进行每个有风险的步骤.您的问题是VSS是一个不好的设备.它基于一些误解并且不够可靠.问题包括:
1)VSS不是事务性的；
2)VSS是侵入式的；它使用与解决方案相当强的耦合，而不是松散耦合；结果，一些粗心的用户经常使用链接的VSS来发布他们的代码，而该代码数据库实际上并不可供读者使用.这很容易恢复但很烦人.
主要问题是VSS是专有的.为什么冒险将最有价值的代码信任专有代码来断言；您永远无法确定将来软件可用性和支持的状态.因此，我们都需要可用的而且非常好的开源系统.请参阅以下讨论:版本控制系统，有哪些可供选择? [ ^ ].

表单开发风格的另一方面.可以看出，这是最常见的错误之一:在表单开发的设计者阶段增加过多的复杂性.您是否拥有太多自动生成的代码，并将其与您开发的代码混合在一起，最终导致本问题描述的情况的风险大大增加，因此您可能会失去大部分工作.逻辑思考:使用设计器进行图形开发的唯一真正好处是将结果清晰地图形显示给开发人员WYSIWYG http://en.wikipedia.org/wiki/WYSIWYG [ ^ ].发展非视觉对象是不切实际的.您可以集中精力进行布局以及VB.NET编程中实现的所有其他功能(这实际上更快，需要的手动工作更少，更受支持).利用部分类声明的优势，在分隔文件中开发代码也非常好.

如果未在设计器中加载表单，则可以快速转到这些单独的源文件，注释掉所有代码，但将表单加载到设计器中并保留有价值的布局.当您还原到此程度的表单时，您可以解决您的问题，至少让设计者可以访问该表单.

实际上，您可以尝试将最后的建议应用于您的情况.

—SA

I cannot answer the question in principle, because of the there can be very many reasons for such problems. This problem is very usual.

I only want to give some recommendations on how to avoid the similar problems in future.

First of all, I''m glad you mentioned VSS. You certainly need to do all the work under Revision Controls, especially for the Forms. As it is too easy to mess-up a form, each risky step should be started after committing the previous change to your Revision Control System. You problem is that VSS is a bad one. It is based on few misconceptions and is not reliable enough. The problems include:
1) VSS is not transactional;
2) VSS is intrusive; it uses pretty strong coupling with the solution instead of loose coupling; as a result, some careless users often publish their code with linked VSS while the code data base is not actually available to the readers; this is easy to recover but very annoying.
The major problem is that VSS is proprietary. Why risking your most valuable code asserts by trusting it to the proprietary code; you never can be sure about the status of the software availability and support in future. By this reason, we all need Open-Source systems, which are available and very good. Please see this discussion: Revision control systems, which to choose from?[^].

Another aspect of Form development style. As can see that this is one of the most common mistake: to put too much complexity in the designer phase of form development. Is you have too much auto-generated code and mix it with the code you develop, your risk ending up with the situation describe in the present Question greatly increased, so you risk loosing a big part of your work. Think logically: the only real benefit of graphical development using the designer is the clear graphical presentation of the result to the developer, WYSIWYG http://en.wikipedia.org/wiki/WYSIWYG[^]. Developing non-visual object is impractical. You can concentrate on layout and everything else achieve in VB.NET programming (which is actually faster, require less of manual job and more supportable). It''s also very good to develop you code in separation file(s), taking the benefit of partial class declaration.

If the form is not loaded in the designer, you can quickly go to these separate source files, comment out all code but have your form loaded int the designer and valuable layout preserved. When you restore to form to this degree, you can address your problem at least having the form accessible by the designer.

Actually, you can try to apply this last advice to your situation.

—SA

这篇关于在vb.net Windows窗体中打开特定窗体是有问题的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！