Jon's answer is fine, but also, you can make things easier like this:
sqlComm.Parameters.AddWithValue("@join_date", DateTime.Now);
It will automatically use the correct data type, based on the type of the value.
Also - You said you were calling this from ASP.Net. In web applications, DateTime.Now is usually not appropriate - because it uses the time zone of the server, and it doesn't retain any offset information so it can be ambiguous during daylight saving time fall-back transitions. I recommend storing UTC-based values in the database (DateTime.UtcNow).
If you feel that the server's local time zone is relevant in your use case, then consider switching your database column to the datetimeoffset type and using DateTimeOffset.Now. That will avoid problems with DST transitions.
See also: The case against DateTime.Now