Windows Forms

MannyTheMammoth5-Oct-11 19:21

5-Oct-11 19:21

It worked fine some time ago... You're right the exception could be caused somewhere else. I tested to disable only the ShowDialog() method call and it worked fine. No exceptions.

When you ran the code, did you activate the "Unmanaged code debuging"?

Eddy Vluggen5-Oct-11 6:38

Eddy Vluggen

5-Oct-11 6:38

Looks more like your memory has become corrupted. You're not running the method from a different thread, are you?

Bastard Programmer from Hell Suspicious | :suss:

MannyTheMammoth5-Oct-11 19:17

5-Oct-11 19:17

No I'm not, I call it from the main thread.
The Control.InvokeRequired method returns always false.

Luc Pattyn5-Oct-11 7:55

Luc Pattyn

5-Oct-11 7:55

There shouldn't be any problems provided your main method is managed, has the [STAThread] attribute, and you create your AForm instance(s) from the main thread. If you deviate from this path, you are set for trouble with COM objects such as OpenFileDialog.

Smile | :)

Luc Pattyn [My Articles] Nil Volentibus Arduum

MannyTheMammoth5-Oct-11 19:29

5-Oct-11 19:29

That's exactly what I did Frown | :(

Perić Željko5-Oct-11 9:29

Perić Željko

5-Oct-11 9:29

<pre>
public MainForm()
{
InitializeComponent();

OpenFileDialog ofd = new OpenFileDialog();
ofd.ShowDialog(); //The exceptions are thrown from here

}
</pre>

I have copied the code into my program and it works perfectly.
Perhaps you forget to Initialize some Components that are used by AFORM() and exceptions are thrown because of that, or you forget to initialize the OpenFileDialog itself if it is necesary,
InitialDirectory,Filter...

Try to use your code in different place,
for example in subprogram, and call it from wanted place:

<pre>
public AForm()
{
// calling subprogram
Openfiledialog();
}

void Openfiledialog()
{
OpenFileDialog ofd = new OpenFileDialog();
ofd.ShowDialog(); //The exceptions are thrown from here
}
</pre>

If you dont get error messages again it is clear that something diferent is wrong with your program.

For this exception I have found explenation,

RPC Server unavailable:

You are trying to connect to a remote server that is unavailable or does not exist. This error may be caused by your network connection being lost.

For other exeptions I didnt.

All the Best,

Peric Zeljko
(periczeljkosmederevo@yahoo.com)

-- modified 16-Dec-11 13:59pm.

DaveyM695-Oct-11 10:44

DaveyM69

5-Oct-11 10:44

Kudos for answering, but please place code inside a pre block either by using the code widget or manually using <pre> ... </pre> around the code. You can still do this by editing your response.

I would not post your email address publicly in an online forum unless you really like spam!

Dave

Binging is like googling, it just feels dirtier.
Please take your VB.NET out of our nice case sensitive forum.
Astonish us. Be exceptional. (Pete O'Hanlon)

BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)

MannyTheMammoth5-Oct-11 19:53

Linking two pages using Visual STudio

5-Oct-11 19:53

That was a good clue! I disabled my network adapter to check if the network could cause the problem and the OpenFileDialog worked fine!

As my "My Documents" folder is stored on a remonte server, my computer uses the network connection to get the folder and files informations. Any idea why this could throw the exceptions I have?

I'm not sure yet why I have those exceptions, but my code isn't faulty! Poke tongue | ;-P

Jomon T Jose26-Sep-11 16:53

Jomon T Jose

26-Sep-11 16:53

I am doing a project which requires me to have a link from one page that will direct/take me to another page. How can i do this..?

Re: Linking two pages using Visual STudio

RobCroll10-Oct-11 12:11

RobCroll

10-Oct-11 12:11

Pages generally refer to web development not form development but if you are talking about forms in a Windows Application, it is easy. Create Form1 and place a button on the form using the form designer. Double click on the button and it will create the default event code stub for that control. The stub will be displayed in the code view. In the code stub enter something like:

Form2 form = new Form2();
form.Show();

"You get that on the big jobs."

Re: Linking two pages using Visual STudio

rajeevcapgeminiindia17-Nov-11 19:50

rajeevcapgeminiindia

17-Nov-11 19:50

There are two conditions in Windows form application to open Secod Form from First form.

Openning the form in Normal mode:
---------------------------------
Form2 objForm2=new Form2();
objForm2.Show();

it will open the second form as normal mode.

Openning the form in Model mode:
---------------------------------

Form2 objForm2=new Form2();
objForm2.ShowDialog();

It will open the second form as model form.

dock a windows form into ppt application window

shama_12325-Sep-11 21:18

shama_123

25-Sep-11 21:18

how to dock a windows form into ppt application window

Re: dock a windows form into ppt application window

Dave Kreskowiak26-Sep-11 3:40

Dave Kreskowiak

26-Sep-11 3:40

If you're talking about a normal Windows Form application, you can't. PowerPoint will not repaint your window since it will know nothing about it. There is also no interface in PowerPoint to tell it about your window either.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Visual Studio insists my form has changed

Wjousts22-Sep-11 4:05

22-Sep-11 4:05

I have an old Windows Forms project that has an annoying habit of claiming (some of) the forms have changed when they haven't. For example, I open the project. I open frmMain.cs, it appears in design mode and is immediately marked as changed (with the * next to the file name) even though I haven't do anything yet. This would be only marginally annoying except several times in the past it's managed to mess up some of the controls on the form (e.g. disappearing toolbars) when I've let it save while closing the project (without thinking about the fact that I didn't actually change anything).

Has anybody else seen something like this? Has anybody else managed to fix this problem?

RobCroll24-Sep-11 12:01

RobCroll

24-Sep-11 12:01

Someone's been writing code in the InitializeComponent method. Thumbs Down | :thumbsdown:

#region Windows Form Designer generated code

/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
	this.components = new System.ComponentModel.Container();
	this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
	this.Text = "Form1";
}

"You get that on the big jobs."

Wjousts27-Sep-11 11:41

27-Sep-11 11:41

I don't *think* I changed anything in there, but I'll make sure to double check.

Alan N24-Sep-11 20:59

Alan N

24-Sep-11 20:59

I've seen this too and it is damned annoying! Last week I built a form from scratch and found that the problem occurred when I set the docking property of a MonthCalendar. I didn't pursue that any further as I already knew that the form.cs, .designer.cs and .resx were not changing.

As for stuff disappearing I think you just have to accept that the designer will occasionally get it wrong. I've seen the error message

Code generation for property 'Items' failed. Error was: 'An item with the same key has already been added'

presented on a message box with a nice OK button to click. No it is not OK to remove the items from my toolstrip would be my answer but by then it's too late and usually the line of code that adds the individual items to the container has been deleted.
e.g.

toolStrip1.Items.AddRange(new ToolStripItem[]{....})

I've got a note in the comments on one form that says "WTF - added Load event handler, toolstrip items wiped".

My solution to these designer problems was an automated hourly backup of changed source code. I know that this works as the problem reoccurs only when the backup has failed!

Good luck, Alan.

modified 25-Sep-11 3:42am.

Eddy Vluggen26-Sep-11 8:33

Eddy Vluggen

26-Sep-11 8:33

Wjousts wrote:
Has anybody else seen something like this?

Yup. Often in custom controls, someplace setting a property once it's shown. The Designer picks up the change, and marks the document as dirty. Checking the DesignMode[^] would be a quick work-around.

If the form goes dirty, can you undo it?

Bastard Programmer from Hell Suspicious | :suss:

Wjousts27-Sep-11 11:43

27-Sep-11 11:43

I have some custom controls and some forms that inherit from other forms. You might be on to something there.

Wjousts27-Sep-11 11:41