Results 1 to 3 of 3

Thread: Packaging VB.NET applications

  1. Jan 3rd, 2005, 08:33 AM #1
    Water Cooler v2
    Water Cooler v2 is offline

    Thread Starter
    Lively Member
    Join Date
    Nov 2004
    Posts
    65

    Packaging VB.NET applications

    I have coded and then also built the setup/msi installation package for my application. In the Debug folder I have two thingies I see:

    Myapp.msi
    Setup.exe

    Which one is the one that you ship to your clients? The MSI one or the Setup.exe?

    PS: I will of course change the Active Configuration and send the thingies from the Release folder, but the question is which file to send, the msi or the setup exe. Which one has the setup?
    Reply With Quote Reply With Quote
  2. Jan 3rd, 2005, 08:40 AM #2
    ntg
    ntg is offline
    Frenzied Member ntg's Avatar
    Join Date
    Sep 2004
    Posts
    1,449

    Re: Packaging VB.NET applications

    For Win2K, XP, Win2K3 ship only the msi file. For Win95/98/Me ship everything

    Cheers,
    NTG
    "Feel the force...read the source..."
    Utilities: POPFile • DebugView • Process Explorer • Wireshark • KeePass • UltraVNC • Pic2Ascii
    .Net tools & open source: DotNetNuke • log4Net • CLRProfiler
    My open source projects: Thales Simulator • EFT Calculator • System Info Reporter • VSS2SVN • IBAN Functions
    Customer quote: "If the server has a RAID array, why should we bother with backups?"
    Programmer quote: "I never comment my code. Something that is hard to write should be impossible to comprehend."
    Ignorant quote: "I have no respect for universities, as they teach not practicle stuff, and charge money for"
    Reply With Quote Reply With Quote
  3. Jan 3rd, 2005, 04:51 PM #3
    VB_Programmer13
    VB_Programmer13 is offline
    Junior Member
    Join Date
    Jan 2005
    Posts
    16

    Re: Packaging VB.NET applications

    Water Cooler v2,

    Did you use use the Setup Project Wizard to create the setup project? If so, you will need to create a Cab file in order to create a distributable package. You would ship the .exe file along with any other files required by your application (ex. help files, images, etc...).
    Philip de Oliveira
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width