InstallAware Studio Admin X10 9.27.2019 Free Download
Iberico Dillard
Silent Install Builder allows you automate the process of installing various applications. This comes very handy especially for IT admins whose task is maintaining and administering a group of computers in a given enterprise or school. It is also a...
I'm developing a C# WinForms app with VS2010 and its target audience are kids ages 8-14. I estimate about 30% of my users will not have administrative access on their computers, and therefore will not be able to install my app without having their parents install it for them.
Is there any way I can have the .NET Framework install without requiring administrative rights, or somehow bundle the required .NET components with my app? I'm currently developing for .NET Framework 4, but I could easily change my code up to have it work with .NET 2 or 3.5, if needed.
There is no way to run .NET applications without installing .NET on your machine first and yes, the installation does require admin rights. Allowing that for regular users would undermine the whole point of having access restrictions in the first place.
It is entirely possible, though not necessarily practical, to install an application including the .net framework without the end user having admin privileges. The general category for what you want to do is called Application Virtualization. We use VMWare ThinApp, an application virtualization technology similar to Spoon mentioned in an earlier post in this thread. Other applications in the category include Cameyo (www.cameyo.com) and InstallAware (www.installaware.com/virtualization/).
This is an old question but it seems that Microsoft is planning a .NET Native feature that will at some point allow you compile self-contained C# apps that do not depend on the .NET Framework being installed, so that would theoretically end the huge headache involved in trying to distribute .NET applications targeted at newer versions of the Framework to users that do not have admin rights.
We aren't allowed to install software on our workstations either, but we are able to use the SDK binaries (not the installers, as they require admin rights) and dev in dotNet Core on our workstations and do all of this with no admin perms.
All materials posted on the site are obtained from open sources on the Internet or sent by site visitors. All rights to the programs belong to their authors and are provided for information only. The administrator of this site is not responsible for material posted on the site.
Update a Visual Studio instance via the command line with progress displayed and no interactive prompts. You can run these series of commands in two steps by using a bootstrapper found on either the client or in a layout. The first command updates the installer on the client, and the second command updates the Visual Studio product. You'll need to run this in an elevated command prompt, because updating the installer requires administrator permissions. The following example simulates updating a client using an evergreen bootstrapper in the layout.
The Admin version requires administrator permissions on the machine. It can be run by all users on the machine and installs in the system Program Files directory. The Admin version also includes Alteryx Scheduler which requires a license.
If you purchased a Network License (managed by the Embarcadero License Center, FLEXnet or AppWave), copy the network license file (named*.slip or concurrent*.slip) received from the license server administrator to the system where you want to install RAD Studio.
a. Connect with Object Explorer using Windows Authentication, which includes your Administrator credentials. Expand Security, expand Logins, and double-click your own login. On the Server Roles page, select sysadmin, and then click OK.
b. Instead of connecting with Object Explorer, connect with a Query Window using Windows Authentication (which includes your Administrator credentials). (You can only connect this way if you did not connect with Object Explorer.) Execute code such as the following to add a new Windows Authentication login that is a member of the sysadmin fixed server role. The following example adds a domain user named CONTOSO\PatK.
c. If your SQL Server is running in mixed authentication mode, connect with a Query Window using Windows Authentication (which includes your Administrator credentials). Execute code such as the following to create a new SQL Server authentication login that is a member of the sysadmin fixed server role.
If your computer does not prompt you for a password, you are already logged on with an administrator account. Click Cancel two times to close the Date and Time dialog box. You are ready to fix the Windows Installer issues.