Simply run this command in VS command prompt

wsdl /o:MyService.cs /n:namespace.goes.here http://localhost/Service.asmx

After publishing web project to production server i had this message:

The type or namespace name 'ProfileCommon' could not be found (are you missing a using directive or an assembly reference?)

I've deleted everything and re-published web project and now everything is ok.

Anybody knows why this is happening (sometimes)?

Are your SSL pages plagued by the IE warning "This page contains both secure and nonsecure items. Do you want to display the nonsecure items?"

Rather than changing all the links to https://, change them to just //

<img src="//www.domain.com/image.gif" alt="" />

Alternatively, if the images or scripts are located on the same domain, you can access them relatively, rather than absolutely:

<img src="image.gif" alt="" />

Using this method, the browser will know that it must load the image securely if the web page is being loaded securely but it will also load the image normally if the page is not being accessed securely. The image will still need to be available on the other server securely.

The %SystemRoot%\Assembly folder is the global assembly cache.

You cannot directly use Windows Explorer to edit ACLs for this folder. Instead, use a command prompt and run the following command:

Alternatively, prior to using Windows Explorer, unregister Shfusion.dll with the following command to give permissions via the GUI:

After setting permissions with Windows Explorer, re-register Shfusion.dll with the following command:

SYMPTOMS
When you use ASP.NET to create a new event source in the event log, you may receive the following error message:

 System.Security.SecurityException: Requested registry access is not allowed.

RESOLUTION

Follow this link for resolution.

The following code uses the static Regex.IsMatch method to verify that a string is in valid e-mail format.

The IsValidEmail method returns true if the string contains a valid e-mail address and false if it does not, but takes no other action.

You can use IsValidEmail to filter out e-mail addresses containing invalid characters before your application stores the addresses in a database or displays them in an ASP.NET page.

Nice article about Ajax, Virtual Earth and Windows Live.

Delegated Authentication is a new feature offered by Microsoft^® that gives Windows Live ID users the ability to consent to the scoped release of their personal information to particular Web sites in a reliable yet flexible manner.

Delegated Authentication is a way to permit access to personal information, but with more precise control over access and usage permissions than the current binary decision—that is, fully on or fully off—that comes with the generally bad practice of handing over your account credentials to another Web site.

Data providers (also known as resource providers) such as the Windows Live Contacts service can register delegation offers that describe the access that a Web application or site (also known as an application provider) can request to a user’s data. The application provider can then request consent from the user by means of the Windows Live consent user interface (the consent UI) to one or more of those resource offers.

Based on the consent decisions the user makes, Windows Live ID gives the application provider a consent token that enables the provider’s Web site to act on the user’s behalf to access the specified services for a period of time defined by the user.

The consent token contains a delegation token, which authorizes a resource provider to provide scoped access to the user’s data in accordance with that user’s consent decisions, even when the user is not signed in. Stated another way, a delegation token enables application providers to act ”on behalf of” Windows Live ID users within the limits of both consent and constrained scope.

Windows Live Delegated Authentication is both a powerful enabler of a new class of user-centered Web services, and also an opportunity for users to take back control of their own personal data and make informed decisions before releasing that data to other parties.

You can read more about it here.

Code below helped when I wanted to read customErrors configuration section from web.config.  

System.Configuration.Configuration configuration = System.Web.Configuration.WebConfigurationManager"~");
System.Web.Configuration.CustomErrorsSection section = (System.Web.Configuration.CustomErrorsSection)configuration.GetSection("system.web/customErrors");