How to allow Visual Studio to open projects on a server?

[mjpmsa]

What permissions are necssary to allow developers to open an ASP.Net
project so that they can compile it through Visual Studio? They can do
this fine on their local machines, but not on a somewhat locked down
server that they are accessing through shares. I'm investigating what
would be necessary to open this up to them. Hopefully it doesn't
require Front Page extensions or Web Dav.

Alternatively, are there any utilities like make that would allow
command line compilation of a project?

Thanks,
Matthew

[Cowboy (Gregory A. Beamer) - MVP]

1. You SHOULD NOT be running projects remotely. While it is possible to give
permissions for this, it is a pain in the butt and generally ends up with
some frustrated network guy opening a huge security hole on the remote box
because he does not want to make you an admin. Either that or you never gain
access.

2. As long as you set the proper PATH statement in a .bat file, you can
easily command line compile on a remote box. You need to have a path to the
command line compiler. NOTE: If this is not possible, copy the compiler to
the project directory (vbc for VB.NET and csc for C#) - the command line
syntax for the compiler(s) is contained in the .NET help file.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
"mj****@yahoo.com" wrote:

What permissions are necssary to allow developers to open an ASP.Net
project so that they can compile it through Visual Studio? They can do
this fine on their local machines, but not on a somewhat locked down
server that they are accessing through shares. I'm investigating what
would be necessary to open this up to them. Hopefully it doesn't
require Front Page extensions or Web Dav.

Alternatively, are there any utilities like make that would allow
command line compilation of a project?

Thanks,
Matthew

[mjpmsa]

Thanks for the reply. I'm the system admin, not the programmer. I'm
hoping to find some safe alternative for the developers who are
complaining that they need this ability.

1. I've been leaning toward the "you never gain access", because I'm
noticing that URLScan is complaining:

[07-08-2005 - 11:41:46] Client at xxx.xxx.xxx.xxx: URL contains
extension '.exe', which is not specifically allowed. Request will be
rejected. Site Instance='10', Raw URL='/_vti_bin/shtml.exe/_vti_rpc'

That looks like default IIS virtual directories which do not exist any
more, and of course .exe will not be allowed through URLScan.

2. The developers can map the shared folders that their websites exist
in, so they should be able to use their local compiler to command line
compile whatever is in those folders. What they have told me is that
because they have many files in many folders, it would "take too long"
to command line compile. I am thinking that a batch file or something
as simple as "dir /s | csc" or something similar might work to
recursively compile all of it. Or perhaps there is a utility for
compiling entire projects. I will look more carefully at the syntax
for csc and vbc.

Thanks,
Matt