(added 5 February 2006)
If you need to use the Microsoft debugger for .NET programming please follow one of the procedures below as we can not give you administrator rights or add people to the debugger group.
Some common problems are:
From Matt McCleary, 25 Apr 2005 09:47:59
This probably has something to do with debugger permissions. Visual Studio is likely expecting you to be a member of the Debuggers group to run a program from within Visual Studio, and we cannot make users members of that group because it effectively grants Administrator access.
Try going to
cmdand running your program from the command line. Another option would be to navigate to the program using Explorer and double-clicking on the executable.
From Karl Hendricks, 16 May 2005 16:21:18
Unfortunately we cannot grant access to the debugger group for normal users because it effectively gives them Administrator access. There are, however, ways that you can work around this. You can build and view code in VB.NET without being in the debugger group, and can execute those projects by navigating to them through the normal Windows environment. If you need help doing this, you can call or stop by the Help Desk in Speare room 5.
Joel Eidsath, 06 Feb 2006 08:44:22
Users can currently compile programs and execute them from the command line. They cannot execute their programs from within Visual Studio. There will be issues with the .NET runtime if users attempt to execute programs from a network drive (the U: drive). This will throw up a JIT debugging error that has nothing to do with the other problem.
Joel Eidsath, 08 Feb 2006 10:17:39
To be a bit more clear about how to use Visual Studio with user accounts as currently configured:
- Go to the Build menu and either build or compile your program.
- Go to the folder that has the built executable and run it by double-clicking.
Start Without Debuggingin the Debug menu do not work with current user account security settings, so use the steps above instead.