Setup Project

[mike]

Hi there,

This may be simple once I find out how, but I'm trying to add a desktop
icon for one of our laptop/desktop setup and deployment projects that
will put it on all users desktops.

As usual the MSDN documentation is a joke and there doesn't seem to be
much available on the net that helps.

I can easily do it for the logged on user, but all users is proving
difficult. I've read about the 'ALLUSERS' property needing to be set.
How do I set this, where and what else do I need to do?

Also, can I add a desktop icon for another application onto the
desktop. In other words, just add a shortcut and manually configure the
..exe it points at etc?

Nice one,
Mike.

 

[Cor Ligthert [MVP]]

Mike,

As usual the MSDN documentation is a joke and there doesn't seem to be
much available on the net that helps.

I don't agree with you about the "as usual". The documentation is normally
very good. A problem is how to find it. In this case I have to agree with
you . I have not checked it a while but about the deployment project it was
very bad, mainly because all action buttons are hide all over the place of
the IDE. If you are a while busy with it, you are supprised what is possible
with that part of Visual Studio Net.

Right clicking in the right pain on the program gives you the possibility to
add a shortcut.
Richt clicking on that shortcut gives you the possibility to add an image.
Dragging it than to the startup or the desktop folder creates that shortcut.
(Therefore normally you have to do it twice, don't try to use the same
shortcut).

I hope this helps sofar.

Cor

 

[Guest]

cor, care to reply to my 'Post-Install operations from the MSI' on 5/9/06?
There seem to be quite a few developers that agree that the documentation for
..NET Setup and Deployment Projects is severely lacking.
--
KMG Software, Inc.
Thinking Beyond, Above, and Before
http://www.kmgsoftware.com

 

[Cor Ligthert [MVP]]

Brandon,

What you want to say.

There seem to be quite a few developers that agree that the documentation
for
.NET Setup and Deployment Projects is severely lacking.

I am already a very long time one of those and never forget to write that,
despite that the developers of the product are such nice devoted guys/girls
and their product is not bad.

I did that as well in the previous message. But I don't agree that the MSDN
documentation is "as usual bad is a joke" as the OP wrote.

Therefore what do you mean, should I communicate that more?

Cor