kirkhilles
asked on
.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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
PaulHews
Security policies for the .NET runtime are described in the documentation that comes with the runtime SDK.
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
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
ASKER