So you need to create a new aspnetdb database
If you do any development with ASP.NET you will run into the aspnetdb database. This database is an essential component to the membership and webparts framework.
If you are a developer like myself, I find that I add a number of test users (and data) to the database and don’t want the data being moved to the production application. You really have 2 options, delete the data out and hope you get it all, or start with a fresh db and add the needed accounts.
I won’t go through the first option because I usually just opt for the second. It is a much cleaner approach in my mind. To create a new database you can use one of the following commands executed at a command prompt from the “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\” directory:
Launch the wizard and go through the steps.
aspnet_regsql.exe
Create a database on a remote server using your current credentials.
aspnet_regsql.exe -S <server> -E
Or you can get crazy and create a database on the local server, only to be used for profiles, and authenticate with the current logged on user.aspnet_regsql.exe -A p -E
To get all the options and switches
aspnet_regsql.exe -?
Hopefully this information will help you when you are deploying your next application.
Determine the installation date of Windows
The following command helps you to determine the installation date and time of a Windows XP/2003 computer. It is a command which extracts info from the parent command "systeminfo." Here is how you go about displaying the installation date:
Go To Start —>Run —-> Type "cmd" and hit enter.
In the command line type systeminfo | find /i "install date"
Using Fiddler with Localhost traffic
Fiddler is an indispensable web application development tool. For those who might not know what Fiddler is, it is a tool that allows you to see the complete request and response between your browser and the web server.
I am afraid that many developers may dismiss it as useless when they are trying to troubleshoot .Net development because it doesn’t show the traffic between the the web browser and the development web server that listens on localhost.
While this page has a few solutions to the problem. The solution can be solved easily by adding a period after “localhost” in your URL.
Instead of http://localhost:1234/MyApp/…,
use http://localhost.:1234/MyApp/… ( notice the extra dot after localhost).
sometimes the little changes make all the difference.
UPDATE: Another solution would be to use the Hostname of your machine instead of “localhost”.
