Interfaces are merely a way of providing polymorphism when it comes to the idea of OOP (in VB 6 and earlier and COM they were the only supported way).
Under .Net you will find interfaces are more flexible than under COM (interfaces can inherit from each other for starters) but server the same basic purpose.
You could always just remove 1.0. Applications compiled against 1.0 should work with 1.1. Also you will find ASP.Net is probably working with the latest version installed by default.
However if you are running VS.Net 2002 it will require framework 1.0 to be present so only consider removing it if you are running VS.Net 2003.
Have you recently added this webmethod to the service? If so you may need to refresh the client proxy for the web service:
Under solution explorer, web references - right click on the web reference in question and select update, then try a rebuild.
If you install .Net after IIS you need to register the framework with IIS.
Drop to the Command prompt under the Visual Studio tool in your start menu and type aspnet_regiis /i - should take a few seconds to complete and things should then work.
TextBox1.Text = MonthCalendar1.SelectionStart.Month.ToString
will work if there is only one date selected otherwise you may need to also look at the .SelectionEnd and .SelectionRange properties
Within Visual studio go to the file menu and new project, on the left select Setup and Deployment projects then on the right there should be a setup wizard option.
Easiest way to get a control to resize is to set it's anchor property, this will allow you to fix your control's position / size in respect to it's container.
Why would you want to display scrollbars if there is nothing outside the form? If you really do need this then you would probably have to set the Form's AutoScroll property to false and place your own scrollbars on the form.
Our very own Divil's site is probably worth a look. Some excellent GUI related controls can be found there. You may find the Docking Suite and Document Manager controls are fine if you are on a tight (i.e. no) budget, otherwise the SandDock control is excellent value. (Feel I should be on commision for this post ;))
The following 2 links may give you a bit more info - haven't had time to try them myself though....
http://www.c-sharpcorner.com/2/window_service.asp
http://www.fawcette.com/archives/premier/mgznarch/vbpj/2001/08aug01/ce0108/ce0108-1.asp <- is probably the better one to try.
Rodenberg - He doesn't mention anything about this involving remoting anywhere in his post - so I'm not sure why this would have any impact.
To create a regular windows service he needs to do what he is doing now - creating a service project. Services will run if a user is logged in or not, a normal application requires a user to be logged in. If this is a process that runs on a server having it logged in is generally a bad idea.
niros - not near a machine with .Net installed at the moment but off the top of my head you may need to look at threading, possibly launching the filesystem watcher in it's own thread during the service startup. However I should have access to .Net tomorrow and can have a look then.
IIRC MTS isn't supported although COM+ (Component Services) is - this is really an upgrade to MTS anyway and ship as part of Win2K and XP.
Within the .Net framework you are probably best looking at the System.EnterpriseServices namespace.
Does the account the service runs under have permissions to the directory in question? Also could you post the relevant code (service startup, the monitor function etc)?
If you change the server's exception handler to return something else does that really not change the contents of the label?
i.e.
catch (Exception ex)
{
return ex.Message + ' ' + "test";
}
If the string will always be a number you could convert it to an int and then format it.
string s = "11304200";
int i = int.Parse(s);
s = i.ToString("00-0000.00");