I have a new MVC app and a legacy ASP.NET app under a root website. They are isolated from one another in different application pools.Is it possible to leverage System.Web.Routing at the root website as an umbrella filter to seamlessly route (URL rewrite) requests to one app or the other to be transparent to the user?
View 3 Replieswe are experiencing big difficulties in the configuration of ASP.Net state service and II7. The service seems not working correctly because when the application pools recycles the applicatio loose the session.If we try the same configuration in IIS6 it works correcly.What is the correct way to configure the aspnet session state service in iis7?
View 2 RepliesIn my Web.config of my ASP.NET app I have set below:
<authentication
mode="Windows"/>
<identity
impersonate="true"
/>
Does anybody know if its possible to have your website run on multiple separate application poolsSome BackgroundI am looking into start a shopping center style site. I intend to set up100 folders, each folder on the site will be treated as a separate site.http://www.MyShoppingCentre/JohnsMenswear
http://www.MyShoppingCentre/GerrysGardeningCenterI would like to have JohnMenswear running in a separate application poolto GerrysGardeningCenter even though they are both webpages under MyShoppingCentre
We're using an Out-of-Process Session Provider (ScaleOut) for an ASP.NET application and we've noticed that when an object that's not correctly setup for de-serialization inadvertently makes its way into session it will eventually cause the entire process to terminate.
Reproducing and handling this scenario is where it gets even more interesting.
The exception that terminates the process is raised in AnyStaObjectsInSessionState whose implementation is pretty straightforward:
[code]....
We're currently deploying code to live pretty reguarly at the moment, but the down side is destroying user session data.
Is there a way of being able to recycle IIS without loosing session data, or is persisiting session state in SQL server or alike the only way?
I need to use routing with parameters in my ASP.NET application.
public class Global : System.Web.HttpApplication
{
void Application_Start(object sender, EventArgs e)
Then, by navigating to "/Profile" I want to get on Page_Load method Request.Params["Id"] as null and by navigating to "/Profile/1", Request.Params["Id"] as "1".
Thus far working with asp.net webforms was very easy .... But never implemented URL Routing in webforms... I know asp.net MVC Handles URL Routing pretty well... How to get started with URL Routing in an asp.net webform application? For EX: [URL] i want it to be like [URL] Any good article to start with URL Routing asp.net 3.5
View 1 RepliesI am trying to implement URL Routing for a non MVC application. Here's my original [URL] to [URL] I have difficulty when the page has query strings in the URL. This is the route handler I have so far:
public class CustomRouteHandler : IRouteHandler
{
public IHttpHandler GetHttpHandler(RequestContext requestContext)
{
return BuildManager.CreateInstanceFromVirtualPath("ProcessStuff.aspx", typeof(Page)) as Page;
}
}
I started using url routing for my web application. It's a dynamic website and it has more than 50k pages. It looks like now it works slower. how to optimize it, to improve it and make it more efficient?
View 1 RepliesTo clarify, the scenarios I am looking at involve deploying ASP.NET 4 Web Forms application that employ RouteTable.Routes.MapPageRoute:
public class Global : System.Web.HttpApplication
{
public static void RegisterRoutes(RouteCollection routes)
{
RouteTable.Routes.MapPageRoute("questionnaires", "questionnaires", "~/Pages/Questionnaires/List.aspx", false);
[Code]....
Scenario 1: The application is NOT hosted as a virtual directory in an existing website, but is a stand-alone website (it is its own starting point). It has its own application pool. When deployed, it worked without any tinkering.
Scenario 2: The application is hosted as a virtual directory underneath an existing website. It also has its own application pool. However, I received 404 errors when trying to access the routes I had mapped out. Fortunately, I had experience getting MVC to work in 3.5 sp 1, so I tried that method: opened the properties dialog of the virtual director, went to the "Directory" tab, click the "Configuration" button, and added a Wildcard application map to the aspnet_isapi.dll and unchecked the "Verify that file exists" checkbox. This made it work.
My question is why did I have to add a wildcard application map in the second scenario but not the first? If it helps, the root website that hosts the virtual directory in the second scenario is set up with ASP.NET version 2.0.50727.
In an asp.net mvc application, I would like to be able to generate views, where the routing engine will create all URLs that point to a different site, i.e. change the application path.
View 1 RepliesI've been developing a asp.net/c# web application that uses .net routing with Visual Studio 2008. The project is setup to use http://localhost:17315 as the server path. I'm trying to figure out a way for a co-worker to connect to my local project from their system. When I setup the project as a virtual directory in IIS (5.1) the .net routing doesn't work correctly and I get a 404 error (http://localhost/home).Is there anyway for a user on our local network to connect to my application remotely with my current configuration? I know they can't connect to the Visual Studio Development Server, but I would think they should be able to connect if the application is setup in IIS. Maybe IIS6+ is needed for this?
View 21 Replies to run asp.net and asp classic in separate app pools? The asp classic pages are mixed within the same asp.net application and its sub folders. Basically, I have a site and would like to run the asp.net portion in its own app pool and asp classic in a separate app pool. The intent is to run asp.net in a "web garden" configuration; we can not currently do this if asp.net and asp classic are in the same app pool, due to the fact that the classic portions rely on session variables in process.
We have considered rewriting the classic so that they are self contained in one directory, and switching to an SQL-based session storage for classic. We determined it was easier to attempt to split the app pools, as these two options would require a significant time investment.
I've used the ThreadPool.GetAvailableThreads to monitor the thread usage in a web site, and written the results to a performance counter. To do this, I've had a thread running in the site that does the monitoring. I'd like to be able to monitor this without modifying sites' code. Is there a way I can write a console app that would be able to access the thread pool of a given process, rather than the current process, and call GetAvailableThreads for that pool?
View 1 RepliesI am using ASP.NET 4.0 Web Forms. I learned that, in order to optimize my Web Application for Search Engine, I must implement custom 404 page. But the way Microsoft tell us to implement custom 404 (within Web.Config file), that is not good for SEO. Microsoft says,
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="404" redirect="Page-Not-Found.aspx" />
</customErrors>
But when the page is not found, IIS issue 302 redirect to Page-Not-Found.aspx page which is not good. So, I implemented custom 404 page using Routing technique that is available in ASP.NET 3.5 SP1 and 4.0. I used the following router in Global.asax page
Imagine a Web Forms application with routing.
A clean page name like:
[URL]
Might have an underlying of URL of:
[URL]
If a user enters [URL] into a browser, I need to redirect to [URL]
Is this possible to do?
I can't work out a way to do this as the routing engine is not executed for a physical page and in the page.aspx Page_Load method I have no way of knowing whether the URL was entered directly or was the result of a route.
I have a web application and I'm using asp.net routing. When I publish it with the Only files needed to run this application selected it gives me an error when I'm loading any of the page "HTTP Error 404 - File or directory not found."
but if I choose publish All files it works fine.
Do you know how to resolve this issue?
I tried everything I could find, but still does not work on IIS routing.
View 2 RepliesI am using:
ASP.NET 3.5 SP1 with Web Forms Routing thru Global.asax (System.Web.Routing and RegisterRoutes)IIS 7
Everything is working fine in my local machine, but it gives the following error in my hosting environment:
Could not load file or assembly 'System.Web.Routing, Version=3.5.0.0, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
I did everything inside my web.config file mentioned in the following link:
[URL]
But I am still getting the above error.
What else am I supposed to do fix the error?
I have a Web application where i have added a reference to a RESTful WCF. I got the WCF url Routing to work in my webapplication by adding Inherits="RestService.Global" to the Web applications Global.asax.
<%@ Application Codebehind="Global.asax.cs" Inherits="RestService.Global" Language="C#" %>
But then i tried to create url Routing for the Web application and it does not work with the Inherits="RestService.Global" in the Global.asax. If i take it away it works fine. Is there a correct way to do this.
I'm trying to create my own CMS and I've gotten a little bit stuck at the stage of URL routing.
I want clean URLs without extensions and I'd like to be able to create and modify them in a web based interface without any messing around with IIS or actual files.
I've seen how to create a static route, but for that I need to go into my Global.asax file and manually add it.I would like to have all of these routes stored in a database so that I can easily modify them later.
Does anyone know how this can be achieved?
Just for extra information, I will be attempting to create a feature so that if a path exists, but is later changed, a 301 redirect is created to the new URL, is this also possible? (My first problem is the main issue, but thought I might ask this as well just in case it makes a difference)
How to handle asp.net mvc routing along with asp.net webform routing. I have merged my mvc app into my existing web application. In my web application i have implement routing as below:
routes.Add("View Product Details", new Route("Product/{City}/{Manufacturer}/{Name}/{ProductID}/{*ProductType}"));
Similarly i have implemented routing in mvc as below
routes.MapRoute("Product Details",
"Product/{City}/{Manufacturer}/{Name}/{ProductID}/{ProductType}",
new
{
controller = "Home",
action = "ProductDetails",
City= UrlParameter.Optional,
Manufacturer= UrlParameter.Optional,
Name= UrlParameter.Optional,
ProductID= UrlParameter.Optional,
ProductType= UrlParameter.Optional
});
How to handle both pages, as one is custom web form while other is asp.net mvc view?
Response.RedirectPermanent(Url); can redirect permanently to a url.
However, during my SEO process, I decided to change my routhing rule.
For example,
I change "/tag/{tag}-quotes" routing rule to "quoes-about/{tag}", but I don't want to lose all the traffic to old routing url.
What is the best way to handle this permanent redirection?
I consider the following an error, and not a feature:
When posting a request, any parameters are held in the HttpContext.Request.Form as key/value pairs. This is perfectly fine for the recipient of the request. Unfortunately, however, further down the chain these values still exist and take precedent in binding over new parameters created during processing.
This is obvious in the RenderAction scenario. If a new parameter is created in a view and passed through RenderAction, if the parameter has the same name as one of the initial request parameters (or a form field for that matter), then MVC Binding will bind the initial request form value to the Action being called, and not the new parameter being defined in the RenderAction call. What's even more frustrating, is there is no easy way to override the initial form values.
It really does not make sense that a value defined in one context, should live throughout the entire processing context... at least without the developer being able to determine it should remain. At a minimum, any new parameter defined in the process with the same name should either a) be received as a parameter and not a form value; or b) override the form value.