13. januar 2006 - 11:27Der er
11 kommentarer og 1 løsning
vs 2005 pro
nu har jeg fået vs 2005... men har lidt start problemer... når jeg opretter et nyt website får man hverken bin mappe, global fil , config fil osv... skal man lave en solution først?? og hvofor kan man ikke lave et web project??
når du har oprettet en website er det præcist som et webproject. prøv at trykke f5. så spørge den om du vil tilføje en config fil. Bin mappe oprette kun hvis du tilføjer referencer. og global fil skal du selv tilføje. Taktikken er nu at tilføje så lidt som muligt i stedet for at tilføje en masse skidt
hvor er så dll'en hvis man ikke har en bin mappe? når jeg kører en aspx side kommer der en fejl at den ikke kan loade min codebehind?? linie 1 i aspx filen: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>
It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.
IIS versions earlier than 6.0 use the ASP.NET process model (Aspnet_wp.exe). Under the ASP.NET process model, each unique application version automatically runs in a separate process at run time. All applications that target the same version of the runtime share the same process (or processes in Web garden mode). However, IIS 6.0 uses the IIS 6.0 process model (w3wp.exe) and introduces a new isolation feature called application pooling. Application pooling allows applications to run together in one or more processes, as long as they share the same pool designation. Applications that are assigned different application pools never run in the same process.
When multiple versions of the .NET Framework are installed on a computer that uses IIS 6.0, you might encounter the following error message in the Application Event log.
It is not possible to run different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.
This error occurs when more than one version of ASP.NET is configured to run in the same process. Different versions of the .NET Framework and runtime cannot coexist side-by-side in the same process. Therefore, an ASP.NET application that uses a particular version of the runtime must not share a process with an application that uses a different version. This error commonly occurs when two or more applications are mapped to different versions of ASP.NET, but share the same application pool.
To use application pooling, first make sure IIS 5.0 isolation mode is disabled. Next, navigate to the desired application in the Internet Information Services management console and assign it an application pool. If you want to isolate your application from the existing application pools, create a new pool designation.
Note The process isolation for each application is configured manually.
To disable IIS 5.0 isolation mode in IIS 6.0
1. Open the IIS management console and expand the local computer by clicking the plus sign. 2. Right-click the Web Sites folder and click Properties. 3. On the Service tab, clear the Run Web service in IIS 5.0 isolation mode check box.
To assign a pool designation to an ASP.NET application in IIS 6.0
1. Open the IIS management console, expand the local computer by clicking the plus sign, and navigate to the folder that contains the ASP.NET application. 2. Right-click the application and then click Properties. The application's properties dialog box appears. 3. On the Directory tab, select the desired pool designation from the Application Pool list.
To create a pool designation in IIS 6.0
1. Open the IIS management console and expand the local computer by clicking the plus sign. 2. Right-click the Application Pools folder, point to New, and then click Application Pool. The Add New Application Pool dialog box appears. 3. Enter the new pool designation in the Application pool text box, and then click OK.
Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.