+ Post New Thread
Results 1 to 2 of 2
Windows Thread, Subverting Software Resritction Policy for Visual Studio debugging in Technical; Hey all, looking for some advice. Environment : HIGH SCHOOL - Computing Students Network : Win 2K/2K3 Hosts: Win XP ...
  1. #1

    Join Date
    Nov 2011
    Location
    Blackpool
    Posts
    5
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Question Subverting Software Resritction Policy for Visual Studio debugging

    Hey all, looking for some advice.
    Environment : HIGH SCHOOL - Computing Students
    Network : Win 2K/2K3
    Hosts: Win XP with Visual Studio 2010

    Students can code a module, and run it with the debugger, and it works fine (when it has not yet been saved). As soon as you save the project, trying to run it from the debug command, or launching the built executable generates the Software Restriction Policy block.

    We can't take out .EXE from the Software restriction policy because that would cause free-for-all, and we can't realistically specify a single filename.exe as that would count on sutdents saving the project with the exact filename, and also would open up possibility for students understanding that filename.exe is not being blocked, and then renaming other applications we are trying to be blocked from running.

    I would assume there is someway to run code from the debugger that compiles the code inside it's own kind of virtual environment, free from policy settings.

    Does anyone know if there is a sensible way round this? I may be looking over something blatently obvious.

    Any contributions greatly appreciated.

    Regards
    Neil

  2. #2

    Steve21's Avatar
    Join Date
    Feb 2011
    Location
    Swindon
    Posts
    2,773
    Thank Post
    354
    Thanked 534 Times in 499 Posts
    Rep Power
    183
    Quote Originally Posted by NeilCotton View Post
    anyone know if there is a sensible way round this? I may be looking over something blatently obvious.
    I wouldn't call it "sensible" as there's many many a downside, but could always run .net studio as admin. But then anything run has admin credentials too.

    "As far as I knew" you could give SRP to certain area's, so can't you add a restriction that it's not done in "XYZ" folder, at least that way exe's could be run just without admin access. But then if anyone manages to add other exe's (games etc) those could run too?

    Steve



SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 1
    Last Post: 10th November 2010, 12:43 PM
  2. Help write a guide for Software restriction policies for USB
    By ChrisH in forum How do you do....it?
    Replies: 7
    Last Post: 28th January 2010, 10:40 AM
  3. Virtual PC for Visual Studio 2008
    By amyr in forum How do you do....it?
    Replies: 10
    Last Post: 24th August 2009, 10:18 PM
  4. Visual Studio 2005
    By russdev in forum Coding
    Replies: 14
    Last Post: 12th February 2007, 11:22 AM
  5. Visual Studio 2003
    By markwilliamson2001 in forum Windows
    Replies: 1
    Last Post: 15th September 2005, 01:28 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •