I have been trying to set up some services that keep conflicting with each
other because of VS2003 default names.
Even though I set up a service, such as EmailService, it still sets up the
file as Service1.vb. If I change the file name in Soluction Explorer to
EmailService.VB , I find the Class is still Service1. I found that I had to
manually go through the code do find all the places (including ServiceName
in Properties) and manually put in the name (which if you mess up and
mispell - can cause problems).
Is there an easier way to do this?
Why does it force you to take the "Service1" after you already gave the name
to the Project.
Thanks,
Tom
other because of VS2003 default names.
Even though I set up a service, such as EmailService, it still sets up the
file as Service1.vb. If I change the file name in Soluction Explorer to
EmailService.VB , I find the Class is still Service1. I found that I had to
manually go through the code do find all the places (including ServiceName
in Properties) and manually put in the name (which if you mess up and
mispell - can cause problems).
Is there an easier way to do this?
Why does it force you to take the "Service1" after you already gave the name
to the Project.
Thanks,
Tom