Visual Studio not Showing Errors

Is your Visual Studio showing error line numbers and respective pages while you develop?
If not read on, recently I came up to a machine which was having Visual Studio error. Visual Studio was showing errors when a project is compiled but the error details (error code line number, error file) which we can use to identify the error are not displayed.
After trying out several things found the cause of it and thought to share it.
The problem was not with the project but with the path the project was kept.
In the machine the failing project was stored under a folder which was having parenthesis or brackets "(".
For example the solution path was like C:\ProjectsA(V1)\MyProj\.
The (V1) part was confusing Visual Studio making it stop displaying the error details.
If you also have the same problem simply remove the brackets by renaming the folder and reload your project to Visual Studio from the new path. The error details will be shown correctly.

Regular Expressions

In the resent past I had to write some simple regular expressions.
So thought of sharing them with you.

An EMail Address Validator

^([a-zA-Z0-9_\-\.]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)(([a-zA-Z0-9\-]+\.)+))([a-zA-Z]{2,4}[0-9]{1,3})(\]?)$
This will validate the entered EMail address.

A Password Validator

(?=.{6,})[a-zA-Z]+[^a-zA-Z]+[^a-zA-Z]+[a-zA-Z]+
This will validate the password to have at least 1 alphabetic character and 1 numeric digit, and altogether the password will be more than 6 characters long.

A Telephone Number Valdator

\d{4}\s\d{3}\s\d{6}
This will expect the telephone number to be in international format. For example (0094 777 123456).

A Simple Length Validator

[\s\S]{1,200}
This will allow only only 200 or lesser characters for input.

A Length Validator Which Works With Linefeed (Return, Enter)

^(.\n){0,500}$
This will validate and allow only 500 input even in a multi line field when linefeed (enter) is used in between.

A Date Validator

(0[1-9]1[012])[- /.](0[1-9][12][0-9]3[01])[- /.](1920)\d\d

This will check for the date validness. The date format should be mm/dd/yyyy to correctly validate by this.

If the date format is required as yyyy/mm/dd then use the following.

(1920)\d\d[- /.](0[1-9]1[012])[- /.](0[1-9][12][0-9]3[01])

Following are some good sites that you can refer for regular expression help.

http://www.visibone.com/regular-expressions/

http://books.google.lk/books?hl=en&id=NYEX-Q9evKoC&dq=Regular+expressions&printsec=frontcover&source=web&ots=qok1lUQubw&sig=XVd8_Z3hM_CWqk5r9dupyAWIllk&sa=X&oi=book_result&resnum=6&ct=result#PPP1,M1

http://regexlib.com/CheatSheet.aspx

Installing HyperV Integration Services

I think at least some of you might have started using Hyper V.

Did you feel how difficult to move from your Host Operating System (OS) to Guest OS (You have to click some keyboard combinations to move in and out).

To make our life easier you can install HyperV Integration Services to the guest OS.

To install, after starting your virtual machine click on the Action menu and click Insert Integration Services Setup Disk. This will start the installation process. After this finishes you no need to click key sequences to go back and forth among the OSs.

This will also install the required components so that the virtual machine will be able to communicate with local area networks and internet.

Please note that you need to install the Integration Services in each and every virtual machine separately.

Google Video Chat

Check out the new Google Video chat.
Now you can video chat using GMail.

http://mail.google.com/videochat

Hyper-V

Hyper-V is the name for the next generation hypervisor-based server virtualization technology from Microsoft.
This is included in Windows Server 2008 as a role and enables you to create and manage virtual servers or machines.
A free version of this also available which is named as Microsoft Hyper-V Server 2008. This is a Windows core having only the Hyper-V functionality enabled.
If interested better visit the following sites.
http://en.wikipedia.org/wiki/Hyper-V
http://www.microsoft.com/windowsserver2008/en/us/hyperv-overview.aspx
http://www.microsoft.com/windowsserver2008/en/us/hyperv-faq.aspx

Enabling Forms Authentication in SharePoint

Recently I needed to change the authentication of one of the application that I did using SharePoint to forms. I needed to authenticate users using Active Directory (AD). Even there are many sources explaining how to do it I found most of them are not full. So thought to put an article my self.

The default authentication method of SharePoint is Windows. It will use a window to get the user information while logging in.

To change the authentication first you need to login to the Administrator site.

Now select Application Management and click on the link Authentication Providers under Application Security.

In the Authentication Providers screen first make sure the correct web application is selected. If not, select the correct application using the drop down in the top left corner of the page.

After selecting the correct application click on the Default zone (Please note that here I am going to change the default zones' authentication. If you are to change in another zone simply select the required zone).

In the Edit Authentication page select Forms as the Authentication Type then in Membership Provider Name type AD, which we are to setup later. Then click the Save button.

As of the result of changing the authentication providers the Web.Config file will be changed accordingly automatically. But this is not enough we need to enter the membership provider details ther in site Web.Config file and Administrator site Web.Config files.
To do the necessary changes open both Web.Config files. Both files needed to be updated with the same information.

1. In the connection strings section add the following line.

This specifies the connection string to the AD. (Please note that my full computer name is 'ironone-ms-t01.MS.TEST' and my domain is 'MS.TEST'. You definitely need to change them according to your domain details.

2. Inside System.Web add a membership provider by entering the following text.

You should change the details of the connection according your settings but make sure you do not change the name from 'AD' to anything else, otherwise it will not work.

Application Web.Config

SharePoint Administration Site Web.Config

Save both Web.Configs and do an IIS reset.

Go back again to the administration site and select Application Management. Now select Policy for Web application under Application Security.

After making sure that the correct web application is selected, click on Add Users.

Select the Default as the zone and click next.

When choosing users type the full user name preceding AD:. For example to add administrator type AD:Administrator. Under the permission section select the Full Control - Has full control check box and click Finish.

As the final step you have to change the site collection administrators. For this click on Site Collection Administrators under SharePoint Site Management in Application Management.

After verifying the selected application enter Primary Site Collection Administrator as AD:Administrator. If you want you can fill in Secondary Site Collection Administrator as well. After finishing click Ok.
Now go back to the site and try to login, you will see that the traditional windows login page is replaced with a simple login web page. Since this login page is too simple I did some improvements to the login page and created my own one as you can see below.

Correcting the error at User Control

Recently I got an error in an user control which I used to create users in Active Directory. This user control started to fail in SharePoint after deploying it in to a different server. It threw the following error,

• Exception has been thrown by the target of an invocation.

The Inner Exception was

• Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

After a bit of a struggle I found that the error was due to inappropriate setting in Web.Config file.

To correct it set identity impersonate to false.

<identity impersonate="false" />