You can use one virtual directory but you have to specify where to look for the DLLs if they are not in the root\bin directory. That is where you would use probing. You can't use the same names for the DLLs either. If you use a separate virtual directory then you have a separate domain and can't share information like session state between the applications. You need to decide how closly coupled the applications are to decide if creating a virtual directory makes sense or not.

>Ok, you were right. I really need a virtual directory. I created it and it works. I just can't understand why VS.NET requires it when it is simply under the root.