• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

.NET and 'Administrative Rights'

We've developed a Visual Basic 6 application (connecting to an Access database) that we're trying to market, but we frequently run into problems where 'Administrative Rights' are a problem and trying to get a software package approved through IT Departments is frequently becoming a challenge.

I'm trying to get my hands around the whole .NET concept. If we were to upgrade/rewrite the application down the road in .NET, would that mean that any computer that had the .NET Framework installed would be able to run the application without needing an Install routine (we currently use Installshield X)? I'm guessing the install routine is what most IT managers worry about (some stray DLL causing system instability). Our application uses mostly standard Microsoft components (Graphs, DAO, Exporting to Excel/Word).

I presume 'Administrative Rights' would be necessary to run the application, though.

We've used Citrix before and that's worked well, but the costs are so high per user.

Also, how has everyone's experience been upgrading applications from VB6 to VB.NET?

Thanks guys!

Kirk Hilles
HillesTech.com
0
kirkhilles
Asked:
kirkhilles
  • 2
1 Solution
 
PaulHewsCommented:
Administrative rights aren't necessary to run the programs, however assembly security policies may have to be altered when deploying, and that is the administrators job.

Deployment can be as easy as xcopy deployment.  Even third party components will generally allow this option when they are refererenced with Copy Local = True.  However, security policies have to be in place to allow your application to function properly.  For example, an untrusted assembly will not be allowed to access a Sql Server... the policy must be adjusted to either give trust to the assembly, or give all assemblies a certain level of trust.  

>Also, how has everyone's experience been upgrading applications from VB6 to VB.NET?

For us, it required a total rewrite.  The process to upgrade existing code would have resulted in a lousy code base and, to my thought, would have limited our options for future changes.
0
 
PaulHewsCommented:
Security policies for the .NET runtime are described in the documentation that comes with the runtime SDK.
0
 
Geo123Commented:
Well I rolled out my first Net app to server location and Security told me to get stuffed. So I developed a wee loader exe that sits on the the drive... and copys all files from a folder (actual app exe and word dll) down to C drive... and runs it from there.

If you change the exe then you put it in the Network folder... and loader checks to see if date stamp is newer... if it is its copied down

I did not have time to learn Security polices... and did not want to battle Administrator to change it.

This is short term solution that worked for me

cheers George
0
 
kirkhillesAuthor Commented:
Thanks for your help!

Kirk Hilles
www.HillesTech.com
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now