Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. asp.net application deployment problem?

asp.net application deployment problem?

Scheduled Pinned Locked Moved ASP.NET
visual-studiocsharpasp-netsysadminhelp
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    absprogrammer
    wrote on last edited by
    #1

    hi, i'm using asp.net(lang=vb). I my VS.net(not complete version) IDE dows not have web deployment option. i want deploy application on client's machine. is anyway to depoly application? is it possible? Thanks in advance.

    D 1 Reply Last reply
    0
    • A absprogrammer

      hi, i'm using asp.net(lang=vb). I my VS.net(not complete version) IDE dows not have web deployment option. i want deploy application on client's machine. is anyway to depoly application? is it possible? Thanks in advance.

      D Offline
      D Offline
      Daniel Santillanes
      wrote on last edited by
      #2

      You can always do a "dirty" install. That is, just copy/paste your project files (you don't need .vb / .resx / .vbproj / other Files from VB, only ASPX, ASCX, ASMX, web.config, and all other content you use. bin directory goes without saying) to your client's machine. After copying files, put necessary settings on IIS (Virtual Directory most important) and your deployment is pretty much finished. daniero

      V 1 Reply Last reply
      0
      • D Daniel Santillanes

        You can always do a "dirty" install. That is, just copy/paste your project files (you don't need .vb / .resx / .vbproj / other Files from VB, only ASPX, ASCX, ASMX, web.config, and all other content you use. bin directory goes without saying) to your client's machine. After copying files, put necessary settings on IIS (Virtual Directory most important) and your deployment is pretty much finished. daniero

        V Offline
        V Offline
        Vipin d
        wrote on last edited by
        #3

        along with the above thing ,the cliient machine must support .net frame works:) CrazySanker All I ever wanted is what others have....

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups