5 Replies - 57306 Views - Last Post: 28 January 2009 - 07:50 PM Rate Topic: -----

#1 Louisda16th  Icon User is offline

  • dream.in.assembly.code
  • member icon

Reputation: 15
  • View blog
  • Posts: 1,967
  • Joined: 03-August 06

Publishing a VB.NET project

Post icon  Posted 05 September 2006 - 08:57 AM

When i use the 'Publish <ProjectName>' feature in VB .NET, a setup file is created. When u run the setup, u cannot specify where u want to install ure program. Is there any way to change that. :unsure:
Is This A Good Question/Topic? 0
  • +

Replies To: Publishing a VB.NET project

#2 Amadeus  Icon User is offline

  • g+ + -o drink whiskey.cpp
  • member icon

Reputation: 248
  • View blog
  • Posts: 13,507
  • Joined: 12-July 02

Re: Publishing a VB.NET project

Posted 05 September 2006 - 09:04 AM

I think ClickOnce is pretty rigid, but you may be able to change the options. check this article:
http://visualbasic.a.../dplnet01_3.htm

http://visualbasic.a.../a/clkone01.htm
Was This Post Helpful? 0
  • +
  • -

#3 born2c0de  Icon User is offline

  • printf("I'm a %XR",195936478);
  • member icon

Reputation: 180
  • View blog
  • Posts: 4,667
  • Joined: 26-November 04

Re: Publishing a VB.NET project

Posted 06 September 2006 - 03:34 AM

That's why I always use a third-party Installer rather than the in-built installer.

You can use something as simple as SetupStream, or something advanced and professional as Ghost Installer and others.
Was This Post Helpful? 1

#4 Louisda16th  Icon User is offline

  • dream.in.assembly.code
  • member icon

Reputation: 15
  • View blog
  • Posts: 1,967
  • Joined: 03-August 06

Re: Publishing a VB.NET project

Posted 06 September 2006 - 04:16 AM

View Postborn2c0de, on 6 Sep, 2006 - 04:04 PM, said:

That's why I always use a third-party Installer rather than the in-built installer.

You can use something as simple as SetupStream, or something advanced and professional as Ghost Installer and others.


But VB 2005 also has setup projects, web setup projects and setup wizards which give u a lot more options than the clickonce method. Its a bit complicated but helps u can make damn gud setup applcations. the bad thing is, it uses windows installer 3.0 which doesnt work for windows 9x and NT. Also I never knew that even VB6 has a deployment wizard. :)
Was This Post Helpful? 0
  • +
  • -

#5 Myplace311  Icon User is offline

  • New D.I.C Head

Reputation: 1
  • View blog
  • Posts: 19
  • Joined: 28-January 09

Re: Publishing a VB.NET project

Posted 28 January 2009 - 04:54 PM

When using the publish the install location is set to [Program files]\[Company Name]\[Program name]

If this is a single solution project.
Right click on the project header and hit properties.
The first tabe should be applications properties.
Click the assembly info to change company name-program name and then the install location will adapt to that.
Was This Post Helpful? 0
  • +
  • -

#6 PsychoCoder  Icon User is offline

  • Google.Sucks.Init(true);
  • member icon

Reputation: 1642
  • View blog
  • Posts: 19,853
  • Joined: 26-July 07

Re: Publishing a VB.NET project

Posted 28 January 2009 - 07:50 PM

I'm moving this to the VB.NET forum :)
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1