Sharing EXE

[s_muhilan]

Hi

We are rewriting our VB6 application in VB.NET 2008. The application contains several VB.NET dlls and one COM OCX control.

We want to keep our executable file in shared folder of Server and want to create a shortcut in all other PCs. (This is the way we deployed our VB6 application)

We know that using .NET Code security option we can give permission for sharing exe of a VB.NET 2008 program and .NET Framework is necessary to install in Client and Server PCs.

But we have some questions regarding this:

1. In which place we need to change .NET Code security: Server or Client?
2. Our application has a COM OCX control. Will it affect our sharing?
3. Which resource will be used for running application: Server or Client?
4. We want to use local resource of client such as reading registry setting, INI file etc. Is it possible?
5. Where to put DLLs of the application: Server or Client?

 

[JohnH]

Client is the one executing it, so client must be configured to be able to do that.

1. client
2. COMs must be registered in client, the file can be in application folder on network share.
3. client, server is only serving the files over network.
4. yes, it the client computer that is executing.
5. .Net assemblies should follow in application folder.