Presumably you are in control of ProcessB? I guess you could simply
recompile it as a win exe, but don't change any code (i.e. don't start
any forms etc - just do the same processing you are doing now). That
way there will be neither a console not a taskbar item.
Sounds fishy, though...
Marc
LVP - 06 Feb 2008 23:06 GMT
Marc,
This is done for Cosmetic reasons. What do you mean by fishy?
The Win App compilation works also.
I tried "user32.dll" and show or hide the window. and it works on the Console window.
I like the Win App Compilation Better less complex and less things to go wrong.
I was wondering if there is any other tricks.
thanks you,
LVP
> Presumably you are in control of ProcessB? I guess you could simply
> recompile it as a win exe, but don't change any code (i.e. don't start
[quoted text clipped - 4 lines]
>
> Marc
LVP - 07 Feb 2008 00:36 GMT
Marc,
If I am to use as WinApp how to pass parameters then.
I can pass a console Args[],
Thanks,
LVP
> Presumably you are in control of ProcessB? I guess you could simply
> recompile it as a win exe, but don't change any code (i.e. don't start
[quoted text clipped - 4 lines]
>
> Marc
Family Tree Mike - 07 Feb 2008 03:28 GMT
Environment.GetCommandLineArgs will get the passed parameters.
> Marc,
>
[quoted text clipped - 13 lines]
> >
> > Marc
Marc Gravell - 07 Feb 2008 08:03 GMT
You can pass a win exe args[]
The only thing you need do is recompile as a win exe ;-p
As for "fishy"; I meant no offence, but we regularly see people with
needs to build stealth apps (usually at corporate's request), which
simply isn't a good way to do things... but if it is just to do some
work as a process, then fine...
Marc
LVP - 07 Feb 2008 16:37 GMT
Yes nothing Fishy just due to limitations and restrictions and for cosmetics
I have to do that.
Thanks for the help
LVP
> You can pass a win exe args[]
>
[quoted text clipped - 6 lines]
>
> Marc
LVP - 07 Feb 2008 16:37 GMT
Thanks Mike, that is good.
LVP
> Environment.GetCommandLineArgs will get the passed parameters.
>
[quoted text clipped - 15 lines]
>> >
>> > Marc
christery@gmail.com - 07 Feb 2008 19:39 GMT
Had a problem like that, using VBA/Word but when running WinZip/Zip I
only put in the instructions to close the black window that appear...
(when finished of course)
didnt bother to figure out how to close it, just put it in the user
istructions instead.
The users must have some important task to preform other than
grumbling about how slow everything is...
Hell, if they want they can have dos/wordstar on a 8088 and two 160k
5,25" floppys back (one for dos/ws and one for documents),
that wasnt so long ago.. well the machine I was thinking about is the
100$ computer - wait... we just did that, we are using thin
clients...
now If I only could outfit them with 160KB floppys so they wont fill
up the SAN with .docx junk, that would be perfect... no taking
anything home either, or bringing wiri to work...
//CY Who stole chr$(12)?