The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
I thought with a ASP.NET application you complie the project in 'Release' mode which creates a DLL that resides in a bin folder under the home folder of your aspx files.
I've never uploaded both aspx and aspx.vb, just the DLL and the aspx files.
Taco Bell does win the franchise war according to the tome of knowledge that is Demolition Man. However, I've watched Demolition Man more then a few times and never once did I see WoW. In conclusion Taco Bell has more lasting power then WoW.
Yeah but the application should be compiling on the web server and creating that DLL there, should it not?
Not unless you're doing your hosting in a really weird way.
AngelHedgie's suggestion might work, but if it doesn't try either making the folder an application like I said (so that IIS treats sssclass as the root path for this app instead of the top-level folder), or putting it at the root level.
Posts
http://www.thelostworlds.net/
I thought with a ASP.NET application you complie the project in 'Release' mode which creates a DLL that resides in a bin folder under the home folder of your aspx files.
I've never uploaded both aspx and aspx.vb, just the DLL and the aspx files.
My classmates have had success with uploading just the file and codefile and having it work.
we also talk about other random shit and clown upon each other
EDIT: All I did was add the Control tag name, so that ASP.NET will realize that the ascx file defines a control, and parse it properly.
Not unless you're doing your hosting in a really weird way.
AngelHedgie's suggestion might work, but if it doesn't try either making the folder an application like I said (so that IIS treats sssclass as the root path for this app instead of the top-level folder), or putting it at the root level.
http://www.thelostworlds.net/