Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

I need take a web application and send it from one machine to another. Both machines have IIS installed and running.

Do i need to just put it in the wwwroot folder on the other machine?

i'm not lazy i'm just resting before i get tired.
  • Administrators
Posted

As long as the other machine has the FrameWork installed you just need to copy certain files over (*.aspx, *.asmx, *.ascx, web.config, *.css, *.xml and the contents of the bin folder - not 100% this is all that is required though).

Easiest way is from Visual Studio on the project menu there is a copy project option that can do this for you.

Posting Guidelines FAQ Post Formatting

 

Intellectuals solve problems; geniuses prevent them.

-- Albert Einstein

Posted

copy project button?

 

i do not see a copy project button where do you find this?

i understnad i don't have to use that but if it's there i'd like too ya know.

 

and when it comes to using data connections on web apps.. i've heard there are some problems... any ideas on what i can do to avoid trouble before i get into the nitty gritty, transfer it and find out it doesn't work somewhere else?

i'm not lazy i'm just resting before i get tired.
  • Administrators
Posted

If you've got a web project open then it should be aboult half-way down the project menu (from the menu bar at the top).

 

If you've created a data connection through one of the wizards the connection components it puts on the form have a ConnectionString property. If you look at the property window there should be an entry for dynamic properties - this will store the connection string in the web.config file so it can be easily modified later without needing a re-compile.

Posting Guidelines FAQ Post Formatting

 

Intellectuals solve problems; geniuses prevent them.

-- Albert Einstein

Posted

Deployment Project

 

Another better way is to create a deployment project ... can build everytime you build your main prject and just transfer the installer over to the other machine ... can be installed even by a non-programmer and layman ...

Posted
Another better way is to create a deployment project ... can build everytime you build your main prject and just transfer the installer over to the other machine ... can be installed even by a non-programmer and layman ...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...