G
Guest
Hello,
So I develop a vb.net exe on my (win2k) workstation. I have to deploy it to
another workstation (actually several - all win2k). Each receiving
workstation will have .Net Framework 1.1 (or higher). I place the vb.net exe
on the workstation. In vb6 I used to have to run setup if there were any
fancy controls on the vb6 exe. So, in order to correctly deploy a vb.net
exe what all is involved besides having .Net Framework on each workstation
and placing the vb.net exe on the workstation? I briefly ran into something
(an article that I barely noticed) saying something about using the assembly
for deployment. Any clarification appreciated.
Thanks,
Rich
So I develop a vb.net exe on my (win2k) workstation. I have to deploy it to
another workstation (actually several - all win2k). Each receiving
workstation will have .Net Framework 1.1 (or higher). I place the vb.net exe
on the workstation. In vb6 I used to have to run setup if there were any
fancy controls on the vb6 exe. So, in order to correctly deploy a vb.net
exe what all is involved besides having .Net Framework on each workstation
and placing the vb.net exe on the workstation? I briefly ran into something
(an article that I barely noticed) saying something about using the assembly
for deployment. Any clarification appreciated.
Thanks,
Rich