It happens when a developer tries to deploy their first ASP.NET application to an ISP's or employer's shared web server environment. Take a close look at the graphic above, particularly the highlighted section. It's a helpful clue, though in most cases it's not exactly correct.
What's most likely is that the application folder was copied to the site on the production server, without configuring the folder as a virtual directory at all. See earlier IIS posts on automating the creation and configuration of virtual directories with VBScript. You can hand these off to your site administrator.
4 comments:
hi,
i have the same problem as what you are showing to your page, actually, i am not a network or computer wiz, i don't know how to configure the directory to a virtual machine, i don't know if i said it right, but can you please help he how to make my ASP.NET page work when i deploy it using a Win2K IIS?
thanks for the help.,
great post man :)
Nice to meet you!!!
[URL=http://superjonn.50webs.com/ct-restaurant-week-2010.html]ct restaurant week 2010[/URL]
Can anyone recommend the top Script Deployment system for a small IT service company like mine? Does anyone use Kaseya.com or GFI.com? How do they compare to these guys I found recently: N-able N-central network tools
? What is your best take in cost vs performance among those three? I need a good advice please... Thanks in advance!
Post a Comment