> > > Unless you've got a NotifyIcon or a Timer.
>
[quoted text clipped - 3 lines]
> suggest I use application.run? I tried it in seperate module with
> the same results.
> I want single stand-alone executable- no dlls.
> > I want single stand-alone executable- no dlls.
>
[quoted text clipped - 3 lines]
> part of the Framework that is, for the reasons mentioned, the minimum
> requirement for every .Net application.
That's just silliness. By that reasoning, you made assumptions about my
operating system. And what about the bootstrap loader? Heck, if JAVA apps can
be referred to as standalone outside of a browser I think it's perfectly
reasonable to call a .NET executable without distributed DLLs "standalone."
If you run an application, you assume it to be in context, be it framework,
VM, or OS. But, to be clear: I meant a single executable file for
distribution to clients with .Net installed.
> Back to your question... I copied some parts of a real-world app. Does this
> help?
I already have a real-world solution: I delegated the task. What I am
interested in is the underlying theory.
Maybe I should have titled the thread "Loading a form hidden." I want the
form to load and be active. Invisibly. There are timer events and message
monitors, etc, that I want to be up and processing.
Try statements are kludgy at best. This code was helpful, though because it
helped me see my stupid mistake (I included the object as a parameter to the
run statement)
> Private Shared WithEvents NI As NotifyIcon
> Private Shared MainForm As Form1
[quoted text clipped - 17 lines]
>
> End Sub
Cor Ligthert [MVP] - 07 Dec 2005 07:16 GMT
AJ,
>> > I want single stand-alone executable- no dlls.
>>
[quoted text clipped - 11 lines]
> reasonable to call a .NET executable without distributed DLLs
> "standalone."
No Armin gave you the exact answer if you want to use the Net development
enviroment, withouth completely all parts of the framework.
If you want to do it in another development way, you have even much more
posibilities than you wrote, however not always with the same results as you
have with the Net development environment.
Just my thought,
Cor.
AJPlonka - 07 Dec 2005 17:28 GMT
And I would be using vb to do this because...
> AJ,
>
[quoted text clipped - 24 lines]
>
> Cor.
Armin Zingler - 07 Dec 2005 10:28 GMT
> > > I want single stand-alone executable- no dlls.
> >
[quoted text clipped - 15 lines]
> file for
> distribution to clients with .Net installed.
Sorry guy, I didn't know your skills before. Some people really think "no
dlls" means "no dlls". If you follow dotnet groups, this is not a rare
question. Otherwise I wouldn't have mentioned this, therefore it's not
silliness. Apart from this, I don't see the relation to your actual problem,
but never mind.
> > Back to your question... I copied some parts of a real-world app.
> > Does this help?
[quoted text clipped - 4 lines]
> Maybe I should have titled the thread "Loading a form hidden." I
> want the form to load and be active. Invisibly.
"That's just silliness". An invisible Form can never be active. "Active" is
a term concerning the focus of a window. I've had a hard time trying to
focus an invisible window...
> There are timer
> events and message monitors, etc, that I want to be up and
> processing.
Only a hint, if it's permitted: You do not necessarily need Form to use a
(Windows.Forms.)Timer
> Try statements are kludgy at best. This code was helpful, though
> because it helped me see my stupid mistake (I included the object as
> a parameter to the run statement)
Glad to have helped you.
Armin
AJPlonka - 07 Dec 2005 17:25 GMT
> silliness. Apart from this, I don't see the relation to your actual problem,
> but never mind.
I was thinking that perhaps embedding the form in a dll and then calling it
might work. You're right, it was an off-track comment.
> > Maybe I should have titled the thread "Loading a form hidden." I
> > want the form to load and be active. Invisibly.
>
> "That's just silliness". An invisible Form can never be active. "Active" is
> a term concerning the focus of a window. I've had a hard time trying to
> focus an invisible window...
I realize I'm tripping up on my own semantics. For me, "standalone" means
compiling with bcom instead of brun. And I still call an audio CD is an
"album." Oh well. I should have said "load and processing events." But your
comment surprised me. I checked and, sure enough, take a form below 2%
opacity and it simply stops responding to the interface. So how to build
hotspot overlays? Sorry, I'm digressing...
> Only a hint, if it's permitted: You do not necessarily need Form to use a
> (Windows.Forms.)Timer
I may follow up on that. I just find using the designer an easier way of
keeping track of my code.
> Glad to have helped you.
It helped to confirm that there's no straigtforward up-front way of
configuring a form to do what I was asking. It seems like simple enough
requirement: Load invisibly and process events. Thanks, I do appreciate your
time given to this.
Armin Zingler - 07 Dec 2005 18:52 GMT
> > silliness. Apart from this, I don't see the relation to your
> > actual problem, but never mind.
[quoted text clipped - 8 lines]
> I realize I'm tripping up on my own semantics. For me, "standalone"
> means compiling with bcom instead of brun.
You mean D:\DOS\Qb4\BCOM41.LIB? ;-)
> > Glad to have helped you.
> It helped to confirm that there's no straigtforward up-front way of
> configuring a form to do what I was asking. It seems like simple
> enough requirement: Load invisibly and process events. Thanks, I do
> appreciate your time given to this.
Sorry, I still don't see the problem. If you create the Form, the contained
timer will run even if you don't show the Form. Therefore you do have an
invisible Form and events are processed (that's what application.run is
for). Why is this not straightforward?
Armin