Skip to main content

URL Rewriting Using global.asax File In ASP.NET (C#)

Here I will explain URL rewriting using global.asax file. URL is useful for hide query strings from URL, change the page name or URL.


Add one aspx page in your project and give name Login.aspx.
Then after add this namespace on your global.asax file,
using System.Web.Routing;

Add this code in your global.asax file.

protected void Application_Start(object sender, EventArgs e)   
{  
    RegisterRoutes(RouteTable.Routes);  
}  

public static void RegisterRoutes(RouteCollection routecollection) {  
    routecollection.MapPageRoute("Login", "Login", "~/Login.aspx");  
}  

Run the Login.aspx page without page extension as "Login".

For ex: 

http://localhost:51965/Login.aspx //before URL rewriting
http://localhost:51965/Login //after URL rewriting

Labels:
Location: Surat, Gujarat, India

Comments

Post a Comment

Popular posts from this blog

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...
Post a Comment
Read more

What to choose between .NET Core and .NET?

 .NET Framework is a better choice if you: you don't have enough time time to learn new technology. Need a stable environment to work in. Have nearer release schedules. you are already working on an existing app and extending its functionality. If already have an existing team with .NET expertise and building production-ready software. Do not want to deal with continuous upgrades and changes. Building Windows client applications using Windows Forms or WPF .NET Core is a better choice if you: IF you wanted to deploy your app on Windows, Linux, and Mac operating systems. Are not afraid of learning new things. Are not afraid of breaking and fixing things since .NET Core is not fully matured yet. When you are learning .NET. work on open source.
Post a Comment
Read more