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. General Programming
  3. C#
  4. Installing IIS by my installer project

Installing IIS by my installer project

Scheduled Pinned Locked Moved C#
csharpwindows-adminquestionworkspace
4 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.
  • I Offline
    I Offline
    Iftekhar Naim
    wrote on last edited by
    #1

    I am developing a project which has a web project as a part of it. Now to use it, i need to first install IIS. Is there any way, that my setup project will also install IIS if it does not already exist. Also, can i create virtual directory in IIS from C# code ? thanks

    Chayan

    V 1 Reply Last reply
    0
    • I Iftekhar Naim

      I am developing a project which has a web project as a part of it. Now to use it, i need to first install IIS. Is there any way, that my setup project will also install IIS if it does not already exist. Also, can i create virtual directory in IIS from C# code ? thanks

      Chayan

      V Offline
      V Offline
      Vasudevan Deepak Kumar
      wrote on last edited by
      #2

      IIS is part of Windows media. So I would suggest instead of bundling those files, you can just detect and prompt for IIS to the user. You can, however, create virtual directories from C# Code (using System.DirectoryServices)

      Vasudevan Deepak Kumar Personal Homepage Tech Gossips

      I 1 Reply Last reply
      0
      • V Vasudevan Deepak Kumar

        IIS is part of Windows media. So I would suggest instead of bundling those files, you can just detect and prompt for IIS to the user. You can, however, create virtual directories from C# Code (using System.DirectoryServices)

        Vasudevan Deepak Kumar Personal Homepage Tech Gossips

        I Offline
        I Offline
        Iftekhar Naim
        wrote on last edited by
        #3

        Thanks a lot for your great help. I found the way to create virtual directory using C#. And this is quite cool. Thank you very much. So you are suggesting not to bundle those IIS files in installer. Rather, give user a prompt to install IIS. Can you please tell me why ? I just need to know, does it have any bad consequences ? Is there any chance of License Related Legal issues or copy right infringement ? Also, is there any other system related problems ? or any other ? It will be a great help if you can please send some details. Thanks

        Chayan

        D 1 Reply Last reply
        0
        • I Iftekhar Naim

          Thanks a lot for your great help. I found the way to create virtual directory using C#. And this is quite cool. Thank you very much. So you are suggesting not to bundle those IIS files in installer. Rather, give user a prompt to install IIS. Can you please tell me why ? I just need to know, does it have any bad consequences ? Is there any chance of License Related Legal issues or copy right infringement ? Also, is there any other system related problems ? or any other ? It will be a great help if you can please send some details. Thanks

          Chayan

          D Offline
          D Offline
          Dave Kreskowiak
          wrote on last edited by
          #4

          Iftekhar Naim wrote:

          So you are suggesting not to bundle those IIS files in installer. Rather, give user a prompt to install IIS. Can you please tell me why ?

          Because different versions off IIS require different versions of Windows. On top of that, you'll probably also have to install service packs and hot fixes, which you would also have to bundle with your installer. Basically, you're taking on the responsibility of screwing up someones server when they install your app. Don't. You simply have to tell the end users that IIS is a requirement to install and run your application. Let the user decide how best to handle the installation of IIS and any fixes, so it doesn't screw up the rest of their server.

          A guide to posting questions on CodeProject[^]
          Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
               2006, 2007

          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