Member Avatar for SiahCheePing

Erm, do I need Visual Studio in my Windows Server 2008 to make my website work? Somehow,I've set my Content Directory and my Visual Directory to the same folder with all my ASP.NET pages + codes inside but it doesn't work at all. Tried switching authentication mode to forms authentication. Enable directory browsing and all that but it doesn't work too. How am I suppose to go about doing it?

This is my web.config codes

<?xml version="1.0"?>
<configuration>
<configSections>
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
</sectionGroup>
</sectionGroup>
</sectionGroup>
</configSections>
<appSettings/>
<connectionStrings/>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.

Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<compilation debug="true" strict="false" explicit="true">
<assemblies>
<add assembly="System.Core, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Data.DataSetExtensions, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Xml.Linq, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.DirectoryServices, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
</assemblies>
</compilation>
<pages>
<namespaces>
<clear/>
<add namespace="System"/>
<add namespace="System.Collections"/>
<add namespace="System.Collections.Generic"/>
<add namespace="System.Collections.Specialized"/>
<add namespace="System.Configuration"/>
<add namespace="System.Text"/>
<add namespace="System.Text.RegularExpressions"/>
<add namespace="System.Linq"/>
<add namespace="System.Xml.Linq"/>
<add namespace="System.Web"/>
<add namespace="System.Web.Caching"/>
<add namespace="System.Web.SessionState"/>
<add namespace="System.Web.Security"/>
<add namespace="System.Web.Profile"/>
<add namespace="System.Web.UI"/>
<add namespace="System.Web.UI.WebControls"/>
<add namespace="System.Web.UI.WebControls.WebParts"/>
<add namespace="System.Web.UI.HtmlControls"/>
</namespaces>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</controls>
</pages>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Forms">
<forms path="/" loginUrl="Login.aspx" protection="All" timeout="30">
</forms>
</authentication>
<identity impersonate="true"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
<httpHandlers>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
</httpHandlers>
<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</httpModules>
</system.web>
<system.codedom>
<compilers>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089">
<providerOption name="CompilerVersion" value="v3.5"/>
<providerOption name="OptionInfer" value="true"/>
<providerOption name="WarnAsError" value="false"/>
</compiler>
</compilers>
</system.codedom>
<!--
The system.webServer section is required for running ASP.NET AJAX under Internet
Information Services 7.0. It is not necessary for previous version of IIS.
-->
<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules>
<remove name="ScriptModule"/>
<add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</modules>
<handlers>
<remove name="WebServiceHandlerFactory-Integrated"/>
<remove name="ScriptHandlerFactory"/>
<remove name="ScriptHandlerFactoryAppServices"/>
<remove name="ScriptResource"/>
<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
</handlers>
</system.webServer>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-" newVersion=""/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-" newVersion=""/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>


My login code behind codes

Imports System.DirectoryServices
Partial Public Class Login
Inherits System.Web.UI.Page

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

End Sub
Private Function ValidateActiveDirectoryLogin(ByVal Domain As String, ByVal Username As String, ByVal Password As String) As Boolean
Dim Success As Boolean = False
Dim Entry As New System.DirectoryServices.DirectoryEntry("LDAP://" & Domain, Username, Password)
Dim Searcher As New System.DirectoryServices.DirectorySearcher(Entry)
Searcher.SearchScope = DirectoryServices.SearchScope.OneLevel
'Try
' Dim Results As System.DirectoryServices.SearchResult = Searcher.FindOne
' Success = Not (Results Is Nothing)
'Catch
' Success = False
'End Try

Dim Results As System.DirectoryServices.SearchResult = Searcher.FindOne
Success = Not (Results Is Nothing)
Return Success
End Function
Protected Sub btnLogin_Click(ByVal sender As Object, ByVal e As EventArgs) Handles btnLogin.Click
Dim isauthenticated As Boolean = AuthenticateUser()
If isAuthenticated Then
Response.Redirect("Default.aspx?")
Else
'code here to display incorrect login details
lblError.Text = "Please enter correct username and password"
End If
End Sub

Private Function AuthenticateUser() As Boolean
Dim username As String = txtUsername.Text
Dim password As String = txtPassword.Text
'Dim domain As String = this can be in a config file, hard coded (I wouldnt do that), or inputed from the UI
Dim domain As String = ""

Dim isAuthenticated As Boolean = ValidateActiveDirectoryLogin(domain, username, password)

Return isAuthenticated
End Function
End Class

  • 3 Contributors
  • 3 Replies
  • 274 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by iis74u

Dani AI

Generated

No — Visual Studio is not required on the server. is correct: IIS plus the correct .NET runtime and IIS configuration are what make an ASP.NET site run. Visual Studio only helps with development and publishing, not with IIS hosting.

Quick checklist and concrete fixes that solve the vast majority of IIS7 + ASP.NET problems:

  • Make sure the correct .NET Framework is installed and registered with IIS. For .NET 3.5 the CLR is v2.0; if registration is needed run:

    %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

    (For .NET 4 use the v4.0.30319 path.)

  • In IIS Manager, point the site to the physical folder and then convert that folder to an Application (right‑click -> Convert to Application). Do not create multiple virtual directories or apps that point at the same physical folder — that causes config inheritance and allowDefinition errors.

  • Set the Application Pool correctly: pick the matching CLR version (v2.0 for 3.5), choose Integrated vs Classic based on your app, and set an appropriate identity. Grant that identity NTFS read (and write if needed). Example permission commands:

    icacls "C:\inetpub\wwwroot\mysite" /grant "NT AUTHORITY\NETWORK SERVICE":(OI)(CI)RX /T

    (On Server 2008 R2 / IIS 7.5 you can grant to "IIS AppPool\MyAppPool" instead.)

  • Authentication: Forms authentication requires Anonymous enabled (the ASP.NET pipeline handles login). If you want Windows/AD authentication use the IIS Windows Authentication feature and disable Anonymous. Directory browsing has no effect on running .aspx code.

  • AD/LDAP binding: ensure the web server can reach the domain controller (ports 389/636), use correct DN/credentials for binding, and be aware of impersonation — impersonate="true" changes which account the code runs under and can break access if permissions are missing.

  • Troubleshooting: turn off customErrors for local testing, check Event Viewer and Failed Request Tracing, and verify handler/module registration if ASP.NET handlers are not mapped.

Common root causes are: wrong app pool CLR, site not converted to an application, missing ASP.NET registration, NTFS permissions, and incorrect authentication setup. These steps will address those issues in almost every case.

Recommended Answers

All 3 Replies

Member Avatar for sknake

>>Erm, do I need Visual Studio in my Windows Server 2008 to make my website work?
No

>>Somehow,I've set my Content Directory and my Visual Directory to the same folder with all my ASP.NET pages + codes inside but it doesn't work at all
Visual directory? Do you mean virtual directory? You shouldn't have multiple directories pointed to the same physical store (certain exclusions apply).

>>Tried switching authentication mode to forms authentication. Enable directory browsing and all that but it doesn't work too
What is your question? In general are the changes made inside of IIS not being reflected when you browse the site?

Member Avatar for SiahCheePing

Thanks. I've solved the issue

Member Avatar for iis74u

Can you please let us know how you solved this issue?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.