[dba-SQLServer] Starting an ASP.NET Project (may be OT)

Ron,

Visual Studio uses FrontPage server extensions to publish to a web site. This means that your local wwwroot folder needs to match up with the remote wwwroot folder or else you won't be able to publish your app to the remote web server using VS.NET. Instead you will have to settle for the old FTP approach using an FTP client.

Basically when you use VS.NET you just need to point the project to a local folder on your machine. It will of course expect you to be running a web server on your local machine since it will take care of creating the virtual folder on the web server root folder.

For example: app name = MyApp

This translates to the physical location (assuming you have IIS defaults) = C:\INETPUB\WWWROOT\MYAPP\

Your project files will then be saved to this physical location. The DLL for the web app will be in C:\INETPUB\WWWROOT\MYAPP\BIN\

VS.NET will try to publish your app to the remote web server by first trying to create a virtual folder called MyApp on the web server root. If it can't do that then you will need to use manual FTP methods to publish it to F:\INETPUB\WWWROOT\MYAPP\ (assuming that F:\INETPUB\WWWROOT\ *is* the remote web server root).

When you publish your app you just need to copy over the ASPX page and the DLL to the MYAPP and MYAPP\BIN folder respectively. The .NET framework will recognize a compiled version (DLL) of your app and run it accordingly.

Hope this helps.

Eric

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of
chizotz at mchsi.com
Sent: Friday, January 14, 2005 10:18 AM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Starting an ASP.NET Project (may be OT)


Apologies if this is completely OT.

I've been told that as a company we would like to start moving to ASP.NET 
applications rather than Windows Forms applications. Windows forms apps I 
know, and have been doing for years. I have never done anything with ASP. The 
IT department is being incredibly difficult about helping me get started. This 
is political, they resent an "outsider" (i.e. a developer not in their 
department) being able to do, well, anything.

I'm not stupid, but I am almost completely ignorant when it comes to ASP.NET.

IT told me that I could publish my test projects to http://intranet/artestweb 
and use my network login. When I start up Visual Studio and try to start a C# 
ASP.NET Web Application, it tells me that the path 
\\intranet\wwwroot$\artestweb\rallen\WebApplication1 either does not exist or 
that I do not have access. When I ask IT about this, their response is "I took 
a look at the folder and there is no directory rallen.  Check to see if you 
have a local version."

They are being deliberately difficult. I have no idea how to create the 
directory, where it is on our file system, anything. Trying to create a local 
project, i.e. on the filesystem of my work station results in an error that 
says that the file path and URL do not map to the same server location. I 
simply don't understand (yet) what I need to do. Earlier in this mess, they 
asked if I had made a DNS. Well, yes, I have a DNS that supposedly connects to 
the Intranet database, but it, too, does not like my username/password.

If someone could explain what I should be looking for, or what I should ask, 
or anything at all that would let me deal with this situation from a position 
of just a little more strength, I would surely appreciate it.

Thanks,

Ron


 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com



                                                                                                                                                                                                             ----------------------------------------------------------------
The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted 
herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be 
disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the 
sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner.  If you 
are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any 
disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY 
PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of 
email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not 
to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is 
contrary to company policy. The company will not accept any liability in respect of such communication.