In your project you should have an app.config file. Make the changes here. When you recompile these changes will be put into the one that is in the bin directory.
At the bottom of the code try using
(your button name).PerformClick() instead of passing references to the other event handlers that were passed into this one. That may be causing a problem.
There is a script file you need to run to make ASP.NET the ISAPi filter to run aspx pages. I forget the details on it but this is a common problem and can be found documented on MSDN. Maybe someone else here remembers the details better than I but do not fret. There is a well-known solution.
Try writing to an event log to get more diagnostics. Something like this might work.
try
...your code hear...
catch e as exception
Dim aLog As EventLog
aLog = New EventLog()
aLog.Source = "MyServiceLog"
aLog.WriteEntry("Error: " & e.Message, _ EventLogEntryType.Error)...
No. A program with a user interface requires just that, a user interface, to run. It will require that a user logs into the system. However, if you write your program so that it runs without a user interface (no forms or dialogs) you can schedule it to run with the scheduler with a specified...
You can have multiple procedures by making each a "WebMethod" within the class created for the web service.
I have done it but the code is much too large to put here. Besides, my employer would not like me posting company code.
I got the roots of the following code from a co-worker so I can't take credit. It uses the WMI interface to the scheduler service. It can be used to schedule a task at a predefined interval. The following code is dependent on a predifined global date which is used to hold the time of day for the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.