|
We do not do your homework: it is set for a reason. It is there so that you think about what you have been told, and try to understand it. It is also there so that your tutor can identify areas where you are weak, and focus more attention on remedial action.
Try it yourself, you may find it is not as difficult as you think!
If you meet a specific problem, then please ask about that and we will do our best to help. But we aren't going to do it all for you!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I refer you to the answer I gave you here[^].
|
|
|
|
|
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
If you have a question, ask it. Don't ask for "discussions"; we cannot answer generic questions, and this is an open-ended question. Like the top post says, "be specific".
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Activity diagrams are drawn by folks that don't know how to draw sequence diagrams because activity diagrams are easier to conceptualize than sequence diagrams.
|
|
|
|
|
I'm reading this[^]
In the Introducing section it says:
If “await” sees that the awaitable has not completed, then it acts asynchronously. It tells the awaitable to run the remainder of the method when it completes, and then returns from the async method
Does this mean that is the awaitable has NOT completed, it stops there and runs it? Isn't this a block?
If it's not broken, fix it until it is
|
|
|
|
|
The code after the await statement won't execute until the awaitable is complete. Yes, this is a blocking call, KIND OF.
The difference is that the thread executing the await goes back to running other code that needs to run, like the applications message pump so UI updates are painted and button clicks and whatnot can still execute.
When the awaitable finally returns, the code after the await statement executes as normal.
|
|
|
|
|
I created an app that will be hosted in a Windows Service. I've been looking up how to install the service, and all the results seem to be to use InstallUtil.
My app will be downloaded and installed using an installer. How do I install my Windows Service with the installer?
Can someone point me to how to do this? Again, I DO NOT want to use InstallUtil.
Thanks
If it's not broken, fix it until it is
|
|
|
|
|
If you don't want to use InstallUtil, then this is your only alternative:
Service Functions[^]
In my opinion, it's much easier to use a Custom Action in the installer to call InstallUtil.
EDIT:
If you are using the Windows Installer (.msi) then you can use the Service Installer table to author the installation of services:
ServiceInstall Table[^]
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: If you don't want to use InstallUtil,
It's not a matter of "want"... My customers are going to pay for & download this app. Their not going to want to run a DOS command line utility to install something.
Next, I don't understand the two inks you posted.. Is there not way to create a Setup.Exe with a VS Setup Project?
If it's not broken, fix it until it is
|
|
|
|
|
Kevin Marois wrote: It's not a matter of "want"...
Geez, take it easy.
I don't believe the VS setup project provides a way to install services. However, if the VS project supports custom actions, you could use a custom action to run the InstallUtil and your users would not have to run any separate utility.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Kevin Marois wrote: Their not going to want to run a DOS command line utility to install something
You're note getting it. It's the custom action in your installer that execute the commands, not your user.
Upgrade to a better installation creation application and chances are good you won't even need the InstallUtil because that functionality would be built into the installer.
|
|
|
|
|
Dave Kreskowiak wrote: Upgrade to a better installation creation application
Can you please elaborate on what this means?
Thanks
If it's not broken, fix it until it is
|
|
|
|
|
I think he means that if you want your installer to jump through hoops, you should invest time and/or money in a decent install authoring tool.
There are quite a few available on the interwebs.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Yep.
The Visual Studio Setup and Deployment project doesn't even exist any more. Get used to using a 3rd party tool to build your installers. There's a ton of tools out there.
|
|
|
|
|
Dave Kreskowiak wrote: The Visual Studio Setup and Deployment project doesn't even exist any more.
Yes it does. I'm using in in VS2013 on other applications.
With this whole thread I've been operating on the assumption that it's possible to build a Setup.exe that will install a Windows Service.
Am I wrong here?
If it's not broken, fix it until it is
|
|
|
|
|
Assuming you've added the necessary service and project installer classes to your service project, you should be able to select "Installer Class" from the properties of the service executable:
How do i create an InstallShield LE project to install a windows service?[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Kevin Marois wrote: Yes it does. I'm using in in VS2013 on other applications.
Actually, the Setup and Deployment PROJECT was removed in VS 2012 and replaced with InstallShield Limited Edition. The heading of "Setup and Deployment" project TYPES is still in the "New Project" dialog.
Kevin Marois wrote: With this whole thread I've been operating on the assumption that it's possible to build a Setup.exe that will install a Windows Service.
Sure, if you felt you needed to go through all the extra work of writing it yourself. There is no built-in template to scaffold out a Setup.exe project for you to modify.
|
|
|
|
|
Dave Kreskowiak wrote: Actually, the Setup and Deployment PROJECT was removed in VS 2012
Ya, in 2012 it was removed. For 2013 there's an extension[^] that adds it back in.
Dave Kreskowiak wrote: Sure, if you felt you needed to go through all the extra work of writing it yourself
I'm clearly confused, because a Setup project is stupid simple to create. With a Win app you simply select the output from the Win project, set a few properties for display in the wizard, and voila! A simple setup is Click, click, click done - installed. Are you saying it's not possible to do this with a standard installer? 
I followed a number of articles about "Windows Service Installer", and they all lead to running a DOS command, which is what confuses me. People who pay for and download my product are not going to run a DOS command to install anything.
InstallUtil if great - IF you have VS on that machine.
I'm not getting HOW the service gets installed on my customer's PC.
If it's not broken, fix it until it is
|
|
|
|
|
Kevin Marois wrote: Ya, in 2012 it was removed. For 2013 there's an extension[^] that adds it back in.
Hmmm, never knew that. It's a simplistic project that doesn't support much beyond a simple installation without a bunch of customization. Frankly, it's a waste as other products do the job far better and easier.
A Windows Service is not really a "standard project" as far as an installer is concerned. It's got extra work that needs to be done to setup and register the service beyond what you'd do in a "throw down executable files and a shortcut" application install.
Kevin Marois wrote: I followed a number of articles about "Windows Service Installer", and they all lead to running a DOS command, which is what confuses me. People who pay for and download my product are not going to run a DOS command to install anything.
InstallUtil if great - IF you have VS on that machine.
And THIS is why you don't use the Setup and Deployment project. You use a product that does this stuff for you! InstallShield is just one of many authoring tools that does all the installation work out-of-the-box. Well, at least the full version does. I don't know about the LE version. Other products are the same way. You don't have to add InstallUtil to your installer or write the code to execute it in a custom action in the installer. It's all done for you.
If you want to use the Setup and Deployment project, you have to add the InstallUtil.exe to your installation files. Then you have to write a custom action to execute the command lines to run InstallUtil with the appropriate command line options.
|
|
|
|
|
OK, I see. Looks like I have more reading to do on this.
Thanks.
If it's not broken, fix it until it is
|
|
|
|
|
|
Thanks
If it's not broken, fix it until it is
|
|
|
|
|
If I were you, I would look to use something like Wix#[^] to develop your installer. It has first class support (and examples) for installing services.
|
|
|
|
|
Thank you, I'll check it out
If it's not broken, fix it until it is
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
