01-15-2010 11:28 AM - edited 01-15-2010 11:29 AM
01-18-2010 04:02 PM
This depends on if you are creating an executable or just deploying through the project. If using an exe, you have to have a startup VI anyways, and you can have your configuration code in this. To do this, see the Web Services FAQ for more info. If doing it through the project, it might be more tricky. You can set up a URL Mapping that will run your initialization VI. Then you can call this manually when you first deploy. Alternately you can check an INI key every time a VI is called that sees if it is the first time it's been run and if so, run your initilization code. However this idea seems a bit more complicated and may not be worth it.
Just a few ideas. Hopefully one leads you to success.
01-21-2010 04:14 PM
My understand is that the webservices are "sandboxed" so that the globals from the launching exe are not accessable from the webservice itself. That's why all the examples use shared variables. Otherwise, that might be a good option.
As far as the "from the project" goes, those ideas won't work (aside from the manual one) because I need it to start before a client browser connects.
01-22-2010 12:24 PM
01-25-2010 06:08 PM