Issues Running VB.Net application as network application

[vescetec]

After successfully running a VB.NET application on a 2003 SQL server we are having issues running the same application from anywhere else other than locally on the database server. Ideally we are trying to run the application via a UNC path to the shared database directory on the server. The initial remarks from our programming staff is that the failing workstation does not know where to find the dll's for the application. Being new to the .NET environment, could someone point in the right direction as to the approach to take in configuring a network workstation to properly run a .NET app in this scenario. I assume there must be an area in the system inform the workstation where to look on the network for the supporting dll's. Thanks for any assistance or direction.

 

[ThatRickGuy]

If the app has COM components, they will need to be registered locally I beleive. But first, you must change the .Net security for that application.

On any machine that you want to run the application on you need to open the control panel -> advanced tools -> .Net Wizards. Then use either the Adjust .Net Security tool to adjust the trust level of intranet apps to full, or us the Trust an Assembly to adjust the security on the app in question to full.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[AccordingToDale]

This might seem a rather dumb question, but...

Are you installing the app on the workstation or just copying the exe over?

Creating an installer (very easy with VS) will make sure all dependent objects will be installed on the workstation.

Dale

 

[vescetec]

We are attempting to house all exe's and dll's on the database server and simply running the exe via a UNC pathed shortcut. We don't want to persue storing the exe's and dll's on the workstation(s) in order to minimize the future refresh overhead. Also this app will ultimately run on a terminal server. thanks

 

[vescetec]

Here is some additional clarification. The application has no COM components that would require registering. Our application is a vb.net app that uses infragistic controls. The initial login screen contains several infragistic buttons. When launching the app locally from on the resident server it appears to find these controls(dlls)in the bin folder containing the exe and dlls. But when lauching from another machine that uses a unc path or mapped drive to launch, the exe the app fails because it cannot find the infragistic dlls. The error message is from the "Common Language Runtime Debugging Service" stating the application has generated an exception that cannot be handled.

We even receive the same failure and error message when attempting to execute from the resident server console using a UNC path to its own share as opposed to its local "E" drive (database location)in which it will work fine. So in other words it runs fine if executed from a local path but fails when executing from a mapped or UNC path. Does anyone have a solution to this problem?

 

[ThatRickGuy]

This is were erading the post becomes important. To quote myself:

On any machine that you want to run the application on you need to open the control panel -> advanced tools -> .Net Wizards. Then use either the Adjust .Net Security tool to adjust the trust level of intranet apps to full, or us the Trust an Assembly to adjust the security of the app in question to full.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.