.NET and 'Administrative Rights'
Posted on 2005-05-12
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?