Adding .net code to classic asp website, cannot reference namespaces in dll file
I have a pretty large classic asp website, with virtual directories configured to centralize certain resources. My problem is for some reason I cannot access any of my namespaces and classes. I tried to add a link to another project where I have classes in the "DAL" namespace and although intellisense sees the classes and the website compile fine, these are errors when I try to access any page that links to the class in the DAL namespace,
The following error message "CS0103: The name 'CMS' does not exist in the current context" appears in my browser. Part of the problem is that the website root is not the same folder / level as the website root in IIS. So my libraries are in the root "/ bin" folder of the website, but iis looks for these files in the IIS web browser, which is at a lower level. So how can I get .net to see my binaries without putting them in the bottom root of the IIS site? I tried to set up a virtual directory to mine. DLL file, but it doesn't seem to have any effect.
Thank you for your help!
================================================== ================================================== ================================================== ================================================== =========>
What I am trying to do is save the .dll files I want my website to use in a higher level directory and then in a folder that I have set as web -root in IIS. So tell the library that I want to use its "DAL" in the projects / bin folder, but in IIS the default Local Path is set to "/ site / default". The only way I can use the "DAL" library is to put the / bin folder in "/ site / default / bin", which is not an option for this project. Does it help?
source to share
Using NTFS junction point to achieve what appears to be the same goal works for me.
As an example, I have a website with 20+ IIS child applications that are pretty much identical (don't ask!), Instead of duplicating the "bin" folder in each one (they would be identical) each child application has a "bin" connection that points to the "bin" folder at the root of the website.
/bin <- this is the actual 'bin' folder
/app1
/app1/bin <- this is a junction point
/app2
/app2/bin <- this is a junction point
/app3
/app3/bin <- this is a junction point
/images
...
...
To create these junction points, if you are using Vista / Win2k8 or later you can use the built-in mklink command, for earlier Windows versions use the SysInternals junction.exe tool - available here .
source to share