We've created a windows service to detect the insertion of a particular usb device.
That service is then supposed to launch an application we have written.
We initially made a setup project for our application and a separate one for the windows service.
Now, we are trying to get the service and the application installed in the same setup project.
We tried putting the output of our service into the setup project but without any luck.
We have the a projectinstaller class in the service, so why can't we simply add the project output of the Windows service (including the installer class) to our application's setup project?
There is MSDN article explains it, Create the installers for your service. Microsoft support also have an article, How to create a setup project for a Windows Service application in Visual C#
My primary language is Delphi. In Delphi, when a program is created as Service Application,
installing the program as a Windows Service can be done by running my_service_app_name.exe /INSTALL. I guess, the execution mechanism should be roughly same with service applications created by other compilers.
Thus, adding a windows service to an existing application installer can be done by just running the service application as mentioned, but you should refer to the documentation in case you are not using Delphi.
Related
Hi I have a console app which I need to start up when Windows Server 2012 starts and without needing to login. I've done a bit of research and people advise a windows service is the correct approach, however the links are quite old and I wanted to confirm this is still the case, or indeed correct at all. Cheers.
Yes, Windows Service is still the most popular way to write and run servers and or a 'daemon' in Windows OS.
Depending on what your application is doing, you might have other options though, e.g. hosting an application in IIS (Microsoft's Web server application in Windows Server).
More recently, Microsoft has been working with Docker to also allow the use of containerized application deployments, which is available in new versions of Windows Server (Windows Server 2016).
Here are a few resources for more reading:
For .NET developers: Walkthrough: Creating a Windows Service Application in the Component Designer
Not just for .NET developers: Quick Start: Windows Containers on Windows Server
I'm a very beginner in Windows Apps. I created a Windows Service app to send mail automatically at a specific time daily. Its taking some configuration values from app.config file. Also there is a web reference too in the service application. Then I installed the app using
InstallUtil /i %myapppath%\windowsservicevb.exe
It worked fine. But with less knowledge in this Windows service application I've no idea how to install that in Azure. Do I just need the exe file or I need to copy the app.config file also into the same directory in Azure?
You need to migrate your windows service on to a worker role in azure if you are going for azure PaaS. example here - http://blogs.msdn.com/b/mwasham/archive/2011/03/30/migrating-a-windows-service-to-windows-azure.aspx
Although if you are on an azure - IaaS VM then it is going to be the same as in the case of a windows machine locally.
Can somebody help me with a little issue about Universal Windows Apps?
I'm trying to develop a small universal app that calls an .asmx web service. I can add the Service Reference successfully to the Windows 8.1 project and reference it from the classes in the shared project. When I compile and run the application, it runs without problem.
But when I switch to Windows Phone 8.1, I'm unable to compile and I get an error telling me that the classes generated by the service reference in the Windows 8.1 Project are not accessible from the Shared Project.
Does anyone know how to solve this?
FInally I solved this unanswered question. It seems in Universal Windows Apps is not possible to use SOAP Web Services as Service References, so I used REST Services instead.
I have created an XE2 FireMonkey application which needs to run on an iPad. I am familiar with exporting to XCode and recompiling on the Mac machine. This all works quite fine.
The problem however is when I want to connect to an existing web service. Using the WSDL Import, I can create the necessary file and the functionality from my web service works as expected. This only works in a Windows environment though as the file created by the WSDL Import uses the "InvokeRegistry" which is Windows specific.
How can I connect to a web service in FireMonkey in a way which will compile on XCode and work in an iOS environment?
The Web Service Toolkit of Free Pascal is one option. According to this forum post, iOS can be used as target platform.
The toolkit includes a WSDL importer wizard, also available as command line tool ("ws_helper").
"Web Service Toolkit” is a web services package for FPC, Lazarus and
Delphi; “Web Service Toolkit” is meant to ease web services
consumption and creation by FPC, Lazarus and Delphi users.
It seems that one cannot have data connectivity in mobile iOS applications without various forms of "hacking" code. There is currently no standard way with the XE2 framework to support this.
See: http://edn.embarcadero.com/article/41729
XE5 has major improvements and data connectivity is now easily handled via DataSnap. One can easily reference existing web services via a DataSnap server, so the issues I originally had are now solved.
I have a package I am putting together that contains the following components:
Core windows service
Core web service ( requires windows service )
Secondary web service
Front end
This is designed for a distributed configuration, where the Core Windows and Core web services have to be installed on every machine, the Secondary web service only needs to be installed on one machine and the front end only needs to be installed on one machine.
All four can be co-located on one machine but aside from the core services having to be installed on the same machine they don't have to be.
All four projects have x86 and x64 variants.
Currently I have an installer for each component built as VS2010 deployment projects. This works fine, but it means a lot of files have to be copied and installed before we can get going and it is far too easy to miss one out. I would like to have an integrated installer that pulls them all together and then allows the user to suggest which components to install on any given machine.
Is there a way to do this with a Deployment Project in Visual Studio 2010? I don't believe I can chain MSI packages, but could I create a single one that deployed the windows service and web services to their various locations in such a way that the windows service was guaranteed to be installed before the web service and that all components can be optional with no installation directories created for components that aren't installed? If so, is there anything I can do to ensure that users only see relevant parts of the interface- showing panels conditionally based on previous checkbox responses or similar?
If not is the best alternative ( as suggested in this question ) to put together a simple Forms application to package the files up and chain them manually?
Take a look at Wix (Windows Installer XML). http://wix.sourceforge.net/ Its an add on to visual studio. You can create much more powerful and flexable msi installers with it than with the default VS projects.