Problem with "Publish"

[Rajesh Soni]

Hello!

I'm trying to publish my application, but when i try to install it at the
end-user's computer, i don't know where it places the EXE, it appears in the
start --programs (executed perfectly!)... But i want to define a folder
where the EXE should be placed at the end-user's computer.

Thanks in advance.
Rajesh

[Freddy Coal]

Rajesh Soni, I have the same funny problem, you have this solution:

Put a line in your program that send you a message about where is the
executable (I use Vb.Net)

MsgBox(Application.ExecutablePath)

The program is inside of the Documents and Settings folder.

Freddy Coal.

"Rajesh Soni" <ra*********@yahoo.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...

Hello!

I'm trying to publish my application, but when i try to install it at the
end-user's computer, i don't know where it places the EXE, it appears in
the start --programs (executed perfectly!)... But i want to define a
folder where the EXE should be placed at the end-user's computer.

Thanks in advance.
Rajesh

[lord.zoltar]

Are you guys using a CLickOnce deployment? I am too and I get the same
thing. Also, I don't think there's any way around it.
Bothers me a lot, but until I can persuade manager to get the full
version of VS2005, it looks like I'm stuck with it. ;)

[Jim Wooley (MVP)]

I'm trying to publish my application, but when i try to install it at

the end-user's computer, i don't know where it places the EXE, it
appears in the start --programs (executed perfectly!)... But i want
to define a folder where the EXE should be placed at the end-user's
computer.

Click once deploys the application to a hidden location under Documents and
Settings. This allows for ease of deployment in a Terminal Services environment
to keep multiple users from installing applications over already running
versions. The down side is if you have multiple users on a single box, the
application will be installed multiple times. Installing it to the local
user directory, we can better sandbox the application to improve security
and keep from having to have administrative permission to install the application.
Even if you distribute a compiled application via the old setup mechanisms,
the recommendation is to NOT require an application to be installed in a
specific location.

Jim Wooley
http://devauthority.com/blogs/jwooley