G
Guest
Hi
We are porting a vb6 applicaton to .Net 2005. The old vb6 application files
was placed on a network share and the clients only had a shortcut to a exe
file on that share.
The new version that is gonna use both remoting and webservices. Today I
got a question about using file share to distrubute the application because
they don't want to install a lot of stuff on each client.
I know that .Net security will be a problem with starting applications on a
network share, but will the clients still be able to use all functionalites
in Remoting ? Will events still work ? How can I split up an application so
i.e the client only have an exe file and all the referenced files is on a
network share ?
Anybody that have done such a project ?
Why should we not go this way ? Any help / advice would be appriciated.
I would prefer installing everything on each client, but it's not my decision.
Regards
Stein
We are porting a vb6 applicaton to .Net 2005. The old vb6 application files
was placed on a network share and the clients only had a shortcut to a exe
file on that share.
The new version that is gonna use both remoting and webservices. Today I
got a question about using file share to distrubute the application because
they don't want to install a lot of stuff on each client.
I know that .Net security will be a problem with starting applications on a
network share, but will the clients still be able to use all functionalites
in Remoting ? Will events still work ? How can I split up an application so
i.e the client only have an exe file and all the referenced files is on a
network share ?
Anybody that have done such a project ?
Why should we not go this way ? Any help / advice would be appriciated.
I would prefer installing everything on each client, but it's not my decision.
Regards
Stein