Application in Batch Mode with user interface - C# Discussion Boards

Re: Deployment problem with the MS Web Browser Control

7-Dec-03 4:18

I doubt this would cause a lockup, but what versions of Internet Explorer are the 1 in 20 users using? If the partial.mshtml.dll was created with a newer version that those few users don't have, and you're trying to use those newer interfaces that don't exist in the MSHTML DOM, this would most likely cause a problem. Your installer should make sure they have the proper version (or higher) of IE.

-----BEGIN GEEK CODE BLOCK-----
Version: 3.21
GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++
-----END GEEK CODE BLOCK-----

Furty8-Dec-03 19:49

Furty

8-Dec-03 19:49

I am working closely with one affected user on the issue.

He is using Win98SE, with IE 6 SP1. I have added a bunch of trace output to the app, and the total system lockup is happening right after the ActiveX is instantiated, when the control would be receiving a handle I guess.

I've tried compiling the app for both 1.0 and 1.1 framework versions, and I've referenced & distributed the entire Microsoft.mshtml.dll assembly.

As for the control itself, I am only calling the Navigate method, and catching the OnNavigateComplete2 event - nothing else.

Note that I have 26 other people using the app with Win98 + IE 5-6 without problem, but this one fellow is experiencing lockups on both of his Win98 SE systems. Outside of him, who knows how many people have dismissed the app as inoperable and simply not advised me!

Re: Deployment problem with the MS Web Browser Control

Heath Stewart9-Dec-03 2:37

Re: Deployment problem with the MS Web Browser Control

9-Dec-03 2:37

Man, I don't know. Confused | :confused:

How much memory does this person have in his machines? I mean, the .NET Framework would throw an exception and exhausting the memory wouldn't lock up the system, but it might appear that way. I doubt this is the problem, though.

Have you checked the MS KB? Besides that, all I can think to tell you is to post a message to an appropriate MS newsgroup (msnews.microsoft.com), but I doubt that'll help since replies to more advanced or "odd" problems like this almost never get answered.

Furty9-Dec-03 11:43

Furty

9-Dec-03 11:43

Heath Stewart wrote:
How much memory does this person have in his machines?

One has 64MB, the other 128MB, however my low-end test machine (that runs the app fine) has just 56MB usable RAM (8 MB is taken up by the video card).

Heath Stewart wrote:
Have you checked the MS KB?

Yes. The only possibly related article I could find was a COM import bug in fx 1.0 that was fixed in 1.0 SP1. However, compiling the app for fx 1.1 should have worked around this issue if it was the problem.

Heath Stewart wrote:
Besides that, all I can think to tell you is to post a message to an appropriate MS newsgroup

Have now posted the problem to microsoft.public.dotnet.framework, but as you noted and I've personally experienced, difficult questions seem to get lost in the ether...

Thanks for your help anyway Heath

Exception in File explore

naxos6-Dec-03 13:24

naxos

6-Dec-03 13:24

Hey

I´m trying to make a File Explore like windows explore. I get the Logical drives GetLogicalDrives and then iterate through them. At this point I´m using GetDirectories.
My problem is that I want to show all the drives, also if there is no media like a cdrom or floppy. But using GetDirectories on a:\ with no floppy inserted throws an exception I can't catch.
Please help I want to avoid this.

Re: Exception in File explore

leppie6-Dec-03 22:15

leppie

6-Dec-03 22:15

naxos wrote:
But using GetDirectories on a:\ with no floppy inserted throws an exception I can't catch.

I somehow doubt this.

leppie ::AllocCPArticle("Zee blog");
Seen on my Campus BBS: Linux is free...coz no-one wants to pay for it.

Application in Batch Mode with user interface

Patrick Luijpers6-Dec-03 12:26

Patrick Luijpers

6-Dec-03 12:26

I am trying to create an manual and automatic application in one with windows interface. The manual/automatic switch is in a configuration file.

I have created a form with two buttons. Start and Cancel/Exit. The Start button starts a process that can take up to an hour. The cancel button cancels the process and Exit closes the application.
So far no problem.

When the application is in automatic mode. It should start the process and exit the application. (batch mode), BUT I want the form to show the processing information. Just in case the operator is watching.

Thanks for your help.

Patrick

Re: Application in Batch Mode with user interface

leppie6-Dec-03 22:16

leppie

6-Dec-03 22:16

So what is the problem?

leppie ::AllocCPArticle("Zee blog");
Seen on my Campus BBS: Linux is free...coz no-one wants to pay for it.

Re: Application in Batch Mode with user interface

Patrick Luijpers7-Dec-03 5:17

Patrick Luijpers

7-Dec-03 5:17

The problem is that the form does not show while running the automatic processes.

For automatic I put Start1, Start2 and Exit in Initialize(), which are the same routines the buttons call in manual mode.

-P

Re: Application in Batch Mode with user interface

leppie7-Dec-03 5:25

leppie

7-Dec-03 5:25

Patrick Luijpers wrote:
The problem is that the form does not show while running the automatic processes.

I assume you mean the form is not responding, due to the process taken a long while.

Just fire the process off in a new thread. Smile | :)

leppie ::AllocCPArticle("Zee blog");
Seen on my Campus BBS: Linux is free...coz no-one wants to pay for it.

Some nodes in TreeView with checkboxes and some others without. Is it possible?

TomaHawKPT6-Dec-03 12:18

TomaHawKPT

6-Dec-03 12:18

Hi,

I'd like to know if it's possible to have a TreeView where some nodes have checkboxes and some other nodes don't.

And if it is possible, how can I do it..

Thanks in advance,
TomaHawK

Re: Some nodes in TreeView with checkboxes and some others without. Is it possible?

Heath Stewart7-Dec-03 4:13

What causes the close button to stop working?

7-Dec-03 4:13

Not with the TreeView in the .NET BCL, unless you extend it and override WndProc, dealing with a lot of the messages. See the SDK Documentation for the Windows Tree View common control about how much you'll need to override. You'll have to owner draw each tree node and add a property to your own TreeNode derivitive.

You might try looking for a third-party tree control. Infragistics has a pretty good one. You should also check ComponentOne.

vektuz5-Dec-03 23:04

5-Dec-03 23:04

I'm writing a (Very simple) application. Currently, the main form view consists of the common arrangement of a tree on the left and a rich view on the right. Each node on the tree causes a different rich view to appear on the right.

However, something is very odd.

If I have the cursor in the rich view, and change tree nodes, causing the new rich view to appear, from then on, I cannot close the app.

Application.Exit() works, but calling Close on the main form does not even trigger the Closing event.

I'm not overriding the Closing event or Closed, or anything related to that.

It only happens if the text cursor is in a rich view at the time the rich view is destroyed.

Clicking the X close button, hitting alt f4, nothing works. However, the program continues to behave as expected in every other way (I can continue to modify the rich views and switch between nodes.)

So what would cause Close to suddenly stop functioning? I'm removing the old rich view and replacing it with a new one each time a new node is selected, perhaps that has something to do with it?

vektuz5-Dec-03 23:25

5-Dec-03 23:25

Additional info:

If I watch for the Closing or Closed events, when in this above mentioned 'broken' state, NEITHER event ever even occurs.

If I use SPY++ to view what messages are occuring, I see WM_CLOSE is being sent to the app, but it does absolutely nothing with it...

It may be entirely unrelated to the rich view - what i'm doing is adding and removing user controls (which include rich views and tool bars of their own) from a panel inside the main window. Could that mess it up so badly?
?

Heath Stewart6-Dec-03 5:12

6-Dec-03 5:12

This typically happens when an exception is thrown that screws up the application pump (such as an unhandled exception thrown inside WndProc. Basically, certain message stop being sent. I haven't found any more on it other than that (it all comes down to Windows Messages as you seemed to have guessed), but we are having a similar problem where certain unhandled exceptions (unhandled by the clients that is, but caught by my AppDomain.UnhandledException handler) cause the application to this as well.

I haven't had time to tackly the problem any more since I'm now working on several more improbable tasks with impossible deadlines ( Mad | :mad:

), so if you figure anything out - would you care to share on the forum (thus preserving your findings for future generations Poke tongue | ;-P

Nick Parker6-Dec-03 8:52

Nick Parker

6-Dec-03 8:52

Heath Stewart wrote:
since I'm now working on several more improbable tasks with impossible deadlines

Simply gain additional time by cutting sleep out of the equation, you can always sleep when your 30. Maybe if you throw a little XML at the problem a solution will appear? Poke tongue | ;-P

-Nick Parker
DeveloperNotes.com

vektuz6-Dec-03 10:10

6-Dec-03 10:10

I still can't figure this out.

Wouldn't an exception show up somewhere? I even tried putting the entire application in a TRY / CATCH block (heh), but nothing showed up.

Heath Stewart6-Dec-03 10:17

6-Dec-03 10:17

You can't put an entire Windows application in a try-catch block. See, Application.Run that starts your application is a blocking call (the application pump loops and distributed Windows messages to the appropriate windows). If an exception occurs there but not in your code, it may not be caught. To do this, you must do as I did and stated in my first reply: handle the AppDomain.UnhandledException event.

In any case, this exception is not an app-crasher - it merely screws up the main UI thread but it continues to run.

vektuz6-Dec-03 10:28

6-Dec-03 10:28

[in the MAIN:]
AppDomain currentDomain = AppDomain.CurrentDomain;
currentDomain.UnhandledException += new UnhandledExceptionEventHandler(MyHandler);

[later on:]

static void MyHandler(object sender,
UnhandledExceptionEventArgs args)
{
Exception e = (Exception) args.ExceptionObject;
MessageBox.Show("Exception.");
}

This is almost straight from the MSDN library documentation. However, the UnhandledException never occurs (Even if I replace the messagebox with a console write, no console text appears), however the problem remains.

Perhaps its something else besides an unhandled exception.

vektuz6-Dec-03 11:00