lack of .NET project file on web server

[keith russell]

Hi,
I just transferred to another location at my company and am attempting to add some newly created webpages to their existing Windows Server 2003 Web Edition. I am new to ASP.Net, but have been coding ASP pages for a couple of years. The previous web admin apparently wasnt using a project file to work out of when he created all of the ASP.Net web pages. (The only instance of a project file that is loaded on the server isnt valid and doesnt apply to the web directory that the server is providing.) I created a couple of web pages in a new .Net project on my local machine. I realize there is a problem transferring files from one project to another on different machines, and I know of a way to do that, but as I mentioned, there is no valid project file in existence on the target machine (web server). Any suggestions on how to address that? I would just create a new project file on the server and somehow map the web directory to it, but being unfamiliar with the .Net environment, I dont know if that's a good/valid idea for fear of causing some change in configuration that might bump the server offline. I have already placed my .aspx. and .vb files into the correct directory (the .resx file is also included), but I get a parser error stating that the inherited file (referenced in the .aspx file) cant be parsed:

(<%@ Page Language="vb" AutoEventWireup ="false" Codebehind="tes t.aspx.vb" Inherits="plant _server.test" %>

I've checked the code references in my pages against the ones in the previous admin's, and everthing is identical. I even pasted a copy of one of his pages into a new file and saved it, but I get the same error. So I know there arent any errors in my code, but rather in the configuration of something.
Any help would be greatly appreciated. I've already written several pages in this new environment and can see that once I get it running, it will be a tremendous difference between writing things the old way (notepad or Interdev) vs. using the .Net environment for deveopment.
---
Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/

[Brad Roberts]

I think you need a good dose of "big picture" with .NET web development. This
is probably a large topic for this forum but I will try to help a little
without making myself seem foolish in the eyes of those who are more versed
in .NET than I am.

In ASP your HTML, ASP pages, images, etc. were all part of your web site
content and a code change on the web server was immediate if you used notepad
or something. The project file did not have to be deployed to the live web
server since it was only used by the deveopment environment. (or maybe
Frontpage something or other...).

Good news. The project file still does not get deployed to the live web
server because it is only used by the development environment(Stu dio). HTML
pages, images, and other static stuff remains the same.

However, all of the ".res", ".vb", or ".cs", depending on your language of
choice, files are compiled into a DLL . They may result in several DLLs,
depending on development choices and needs. In the end only the DLL(s),
".aspx", and ".config" files are deployed to the live server. Images, JScript
files, HTML pages, etc are not compiled into the DLL so they are deployed as
before.

In order to get your web content combined with that of the previous
developer of the web site you will need to add your new page(s) to the
existing project and recompile the project to create the web site DLL.

This is a little oversimplified to cover all web content but I hope it helps.

"keith russell" wrote:

Hi,
I just transferred to another location at my company and am attempting to add some newly created webpages to their existing Windows Server 2003 Web Edition. I am new to ASP.Net, but have been coding ASP pages for a couple of years. The previous web admin apparently wasnt using a project file to work out of when he created all of the ASP.Net web pages. (The only instance of a project file that is loaded on the server isnt valid and doesnt apply to the web directory that the server is providing.) I created a couple of web pages in a new .Net project on my local machine. I realize there is a problem transferring files from one project to another on different machines, and I know of a way to do that, but as I mentioned, there is no valid project file in existence on the target machine (web server). Any suggestions on how to address that? I would just create a new project file on the server and somehow map the web directory to it, but being unfamiliar with the .Net environment, I dont know if that's a good/valid idea for fear of causing some change in configuration that might bump the server offline. I have already placed my .aspx. and .vb files into the correct directory (the .resx file is also included), but I get a parser error stating that the inherited file (referenced in the .aspx file) cant be parsed:
(<%@ Page Language="vb" AutoEventWireup ="false" Codebehind="tes t.aspx.vb" Inherits="plant _server.test" %>

I've checked the code references in my pages against the ones in the previous admin's, and everthing is identical. I even pasted a copy of one of his pages into a new file and saved it, but I get the same error. So I know there arent any errors in my code, but rather in the configuration of something.
Any help would be greatly appreciated. I've already written several pages in this new environment and can see that once I get it running, it will be a tremendous difference between writing things the old way (notepad or Interdev) vs. using the .Net environment for deveopment.
---
Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/