Change default Port for the ASP.NET Development Server

Change default Port for the ASP.NET Development Server

When you use the ASP.NET Development Server to run a file-system Web site, by default, the Web server is invoked on a randomly selected port for localhost. For example, if you are testing a page called Default.aspx, when you run the page on the ASP.NET Development Server, the URL of the page might be the following:

http://localhost:2049/Default.aspx

To specify a port for the ASP.NET Development Server

1. In Solution Explorer, click the name of the application.

2. In the Properties pane, click the down-arrow beside Use dynamic ports and select False from the dropdown list.

   This will enable editing of the Port number property.

3. In the Properties pane, click the text box beside Port number and type in a port number.

4. Click outside of the Properties pane. This saves the property settings.

   Each time you run a file-system Web site within Visual Web Developer, the ASP.NET Development Server will listen on the specified port.

Please note the above steps are based on WebSite/ WebServices project. For the Web Application project, we can fix the port number by following steps:

1. Right click the Project in the Solution Explorer, and then select “Properties”
2. Click “Web” tab.
3. Check “Specific port” instead of “Auto-assign Port”.

If you want to debug with IIS, please follow the first and second steps above, and then check “Use IIS Web Server” instead of “Use Visual Studio Development Server”. Also, click the “Create Virtual Directory” button.

Note:

Visual Web Developer cannot guarantee that the port you specify will be available when you run your file-system Web site. If the port is in use when you run a page, Visual Web Developer displays an error message.

How to Write an Effective Survey Questionnaire

Thinking about sending surveys in your email ?

Here are some survey writing tips at the ezquestionnaire.com website.

And we highly recommend Ezquestionnaire.com build and host your survey. We create our surveys on Ezquestionnaire, s.

They have templates with built-in color schemes and stuff, but if you’re a design-it-yourselfer, and you absolutely positively must customize everything , you can use HTML to rig the look and feel of your surveys virtually any way you want.

Spread this word...

Difference between @@IDENTITY and SCOPE_IDENTITY()

@@IDENTITY, SCOPE_IDENTITY, and IDENT_CURRENT

@@IDENTITY, SCOPE_IDENTITY, and IDENT_CURRENT are similar functions because they all return the last value inserted into the IDENTITY column of a table.

@@IDENTITY and SCOPE_IDENTITY return the last identity value generated in any table in the current session. However, SCOPE_IDENTITY returns the value only within the current scope; @@IDENTITY is not limited to a specific scope.

It took me a minute to find a good example to illustrate the difference between the two, but with a trigger I created the following example:

USE TempDB
GO
CREATE TABLE tst
( a int identity(1,1), s varchar(10))
GO
CREATE TABLE tst2
( a int identity(1000,1), s varchar(10))
GO
CREATE TRIGGER dbo.trgTst
ON tst
AFTER INSERT
AS INSERT tst2 SELECT inserted.s FROM inserted
GO
INSERT tst VALUES('a')
SELECT
@@IDENTITY AS [@@IDENTITY],
SCOPE_IDENTITY() AS [SCOPE_IDENTITY()]
GO
DROP TABLE tst2
DROP TABLE tst

SCOPE_IDENTITY() will give you the value of tst.$IDENTITY, ignoring the identity value that is generated for table tst2 with the trigger after the insert into tst. @@IDENTITY will give you that value from tst2.$IDENTITY.

So the function we actually need in our case is not @@IDENTITY but SCOPE_IDENTITY().