code behind not firing

  • Thread starter Thread starter segue
  • Start date Start date
S

segue

Hi - I've set up a 2003 server with .NET 1.4 and 2.0 and I have vs2003 and
vs2005.
When I load my project from a network computer I can't get the codebehind
using the src or codebehind attribute to fire.

I've read about making sure there is a debug directory and bin directory.
Do I have to install the vs2003 sdk on the server?

Suggestions appreciated - Segue
 
If I understand correctly, you are saying that when you try to open your
project in VS, that is located on a network drive, your compiled code
doesn't seem to execute.

First, by default, VS doesn't trust network locations for either compiled
..NET assemblies or VS projects, so the first thing to try is to just move
the project to your local drive and see if it works there.

If so, then you have your answer. You are running into the native code
access security/trust settings of .NET.

You should not have to do anything with debug and bin folders.

-Scott
 
Yes thank you - I am trying to open up a project on a network drive.
I've used .NET since 2002 on many projects.

I have tried this project on my local box and
remote box. When trying to debug the copied and the remote
project I get the same error:

Unable to start debugging on the web server. Unable to map the debug start
page URL to a machine name.

Any suggestions appreciated.
 
Thanks - I've evolved the problem to unable to start debugging access is
denied.
Security policy does not allow users to authenticate for themselves.
So I checked my (due to an online articel) Local Security Settings>Local
Policies>
Security Options>Network access: Sharing and security model for local
accounts>classic
and that hasn't helped.

In IIS I have integrated windows authentication set but I've tried turning
that off as well along with the firewall and installing the visual studio
environment on the server.

Suggestions appreciated
 
Back
Top