M
Michelle
Hello!
<repost from dotnet.general>
I just have a quick question, if I may. I was wondering what benefits,
if any, one of these deployment methods has over the other. These are
for in-house .NET windows applications that are currently only used at
our Head Office (but may be used in other cities/province in the
future).
Method #1:
Using a setup (setup.exe/.msi), install the application on the
customer's PC.
Method #2:
Create a directory on a web server and copy all application files and
dependencies to the bin folder in that directory, add a shortcut on the
customer's PC that points to the .exe on the web server.
Thank you in advance!
Michelle
<repost from dotnet.general>
I just have a quick question, if I may. I was wondering what benefits,
if any, one of these deployment methods has over the other. These are
for in-house .NET windows applications that are currently only used at
our Head Office (but may be used in other cities/province in the
future).
Method #1:
Using a setup (setup.exe/.msi), install the application on the
customer's PC.
Method #2:
Create a directory on a web server and copy all application files and
dependencies to the bin folder in that directory, add a shortcut on the
customer's PC that points to the .exe on the web server.
Thank you in advance!
Michelle