Opening of a particular form is problem in vb.net windows form

Question

3.00/5 (1 vote)

See more:

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]

Posted 4-Mar-11 20:01pm

IndrajitDasgupat

Updated 4-Mar-11 23:13pm

v3

Add a Solution

Comments

OriginalGriff 5-Mar-11 3:04am

Without the relevant code fragment, it is nearly impossible to tell what is wrong.
Please, edit your question, and give us more information.

IndrajitDasgupat 5-Mar-11 5:06am

it is urgent true but not for others it only for me even my intention is not to break other head for my problem I apologizes for that.

[no name] 5-Mar-11 3:25am

There is nothing to identify, what is going actually. I agreed with OriginalGriff.

OriginalGriff 5-Mar-11 3:52am

:laugh: I like being agreed with!

Albin Abel 5-Mar-11 9:58am

if the form have some controls which has no more reference then these kind of problems occur. Open the designer code (Designer.cs) and delete any control references which is not actually in the project now. May be that helps

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-03-05T12:28:00

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