.Net Security Problems

[wki1234]

I made a simple .net vb app that accesses a sql database and I want
anyone on the domain to be able to use the app on their local pc or
remote desktop or run from a network drive.
It runs fine from a development server, but I can't run it from a
network drive and our other remote desktop servers don't have the .net
framework installed.
I tried re-creating the app using vb5, but vb5 grid controls don't
support ado and I don't want to mess with DAO.

Is there some way in Visual Studio 2005 to get around this security
crap, or make a project that is not dependent on .net?

Wyllys

 

[Guest]

It runs fine from a development server, but I can't run it from a
network drive and our other remote desktop servers don't have the .net
framework installed.

When you run an app from a network drive, .NET uses a higher-security
policy.

Try running it locally on the client PCs.

If your servers do not have .NET installed, you'll need to get the
framework installed

Is there some way in Visual Studio 2005 to get around this security
crap, or make a project that is not dependent on .net?

VS.NET 2003/2005 only supports .NET.

 

[Phill W.]

It runs fine from a development server, but I can't run it from a
network drive and our other remote desktop servers don't have the .net
framework installed.

Any machine that needs to run a .Net-written application *must* have the
..Net Framework installed on it.

Is there some way in Visual Studio 2005 to get around this security
crap, or make a project that is not dependent on .net?

Security? So you /do/ have the Framework installed.

Once you've got the Framework on each machine, if you want to run a .Net
application from anywhere outside the local file system then you either
have to
Write /very/ simple applications that can survive inside the security
"sandbox" into which they get loaded and run, or
Apply Code Access Security Policies (on each machine) to instruct the
Framework to allow code from your server to run.

Or re-write the application in C++, to remove the dependency on the .Net
Framework.

Regards,
Phill W.