Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

setting up asp.net server

Status
Not open for further replies.

kylemcna

Programmer
Joined
Dec 23, 2004
Messages
15
Location
US
Hello,

Sorry for complete newbie-ness:
1) Can I not just copy the whole myapp directory out of the on my local machine and put it in the same location on the server?

2) If not, do I have to go through the process of creating a deploy/release project?

3) If so, I tried that (selecting "Primary OUtput" and "Content files" in the process) and it creates two dirs "Debug" and Release". The only purported .msi fil is in the "Debug" directory along with a Setup.exe and a setup.ini...

.. then I run the "Release MyApp.msi" file on the target (new) server and it creates a directory MyApp with one sub dir "bin" and three DLLs... which encompass the class libraries... nothing apparently related to the web-part of the solution.

Is this overkill? Does it sound like I messed up?

Help!

tx,

k
 
You can just copy the files to a directory on your server. You only need the .aspx, .ascx, .config, and .asax files. Actually, you can use VS to just copy the files you need. You can find that tool under Project --> Copy.

The only gotcha will be that if you're copying the application to a sub-root, then you'll have to right click that directory in IIS, and on the general tab next to the application name (which is greyed out by default), you'll need to click "Create".

It's called x-copy deployment, and if you still have problems, post a specific error message back here.

-paul

penny.gif
penny.gif

The answer to getting answered -- faq855-2992
 
Hello,

I used the Project / Copy option, and it worked much better... I still get the same error though when trying to run the app:

"ORA-12154: TNS:could not resolve service name"

Now, I can successfully connect to the database via TOAD and other methods on that server, so I know the database and tnsnames file configuration is fine.

One possible clue is that for some reason I also got the same error on my development machine after fiddling all day with the server yesterday. I rebuilt the project and the error went away. I had never previously or since received that tnsnames error on my local dev machine.

Any thoughts on that?

thank you,

kyle
 
Where do you specify the conection string? Is it in web.config?

----------------------------------------------------------------------

Need help finding an answer?

Try the search facilty ( or read FAQ222-2244 on how to get better results.
 
Hmmm... double check that all your assemblies are in the /bin folder.

penny.gif
penny.gif

The answer to getting answered -- faq855-2992
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top