Is it acceptable to package a web service application in an installer that can only install to a virtual directory of an existing website? And not to its own website from the installer?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it acceptable to package a web service application in an installer that can only install to a virtual directory of an existing website? And not to its own website from the installer?
What’s acceptable depends on what the application does. If it’s inherently bound to/dependent on an existing app, it might be OK. What will make sense to the customer?