Deployment Project - Creating Desktop Shortcut

[NaterPotater]

I can't seem to get my head around the Visual Studio's Deployment Projects:

I want the user, at install-time, to be able to specify if they want a icon
placed on the desktop or not (I'm trying to use Checkboxes(A)). Seemingly
you can just place the Checkbox1Property Name into the User's Desktop
Condition but that does not work. I actually saw an article that highlighted
this process as "the way to do it", so I downloaded the source and it didn't
work (it didn't conditionally add the shortcut...it always added the
shortcut). I created an Installer Class and I'm writing data back into it
through the use of Custom Actions, but I don't want to create shortcuts
programmatically if I can avoid it. Isn't there an easier way? Is there a
way to create a Custom Property so I can write a value to it? It doesn't
seem like the Condition property of the User's Desktop even works properly
(is this a bug?)...

(I'm running ms devenv 2003 ver 7.1.3088)

Thanks!!!

[amol.borkar]

I think you trying to create something like Installshield.
Unfortunately VS.NET deployment looks nowehere close to that and does
not have those features either but we dont have to shell out a large
chunk of our wallet for that. I think you might find this link helpful

http://www.vbdotnetheaven.com/Code/Jun2003/2006.asp

[NaterPotater]

Why then is there a Condition Property under the Properties for User's
Desktop?

"am*********@gmail.com" wrote:

I think you trying to create something like Installshield.
Unfortunately VS.NET deployment looks nowehere close to that and does
not have those features either but we dont have to shell out a large
chunk of our wallet for that. I think you might find this link helpful

http://www.vbdotnetheaven.com/Code/Jun2003/2006.asp

[Dave]

The condition property may be used for what you are attempting, only if, the condition is evaluated before the shortcut is created.
I'm not sure if it's occuring in that order and I'm almost positive that you don't have control over that in VS.NET.

Are you creating the shortcut in the file editor? Is the checkbox form you've added before the installation begins?

When defining the name of your checkbox, as PropName1, use it in the condition as [PropName1]. Note, it's case sensitive.

Hope it helps ;)

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"NaterPotater" <Na**********@discussions.microsoft.com> wrote in message news:58**********************************@microsof t.com...

Why then is there a Condition Property under the Properties for User's
Desktop?

"am*********@gmail.com" wrote:

I think you trying to create something like Installshield.
Unfortunately VS.NET deployment looks nowehere close to that and does
not have those features either but we dont have to shell out a large
chunk of our wallet for that. I think you might find this link helpful

http://www.vbdotnetheaven.com/Code/Jun2003/2006.asp

[NaterPotater]

I couldn't ever get it to work. So, I gave up. The user gets the shortcut
no matter what, I've noticed several "newer" installs have decided to do the
same thing; kinda makes you wonder...

Thanks!

"Dave" wrote:

The condition property may be used for what you are attempting, only if, the condition is evaluated before the shortcut is created.
I'm not sure if it's occuring in that order and I'm almost positive that you don't have control over that in VS.NET.

Are you creating the shortcut in the file editor? Is the checkbox form you've added before the installation begins?

When defining the name of your checkbox, as PropName1, use it in the condition as [PropName1]. Note, it's case sensitive.

Hope it helps ;)

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"NaterPotater" <Na**********@discussions.microsoft.com> wrote in message news:58**********************************@microsof t.com...

Why then is there a Condition Property under the Properties for User's
Desktop?

"am*********@gmail.com" wrote:

I think you trying to create something like Installshield.
Unfortunately VS.NET deployment looks nowehere close to that and does
not have those features either but we dont have to shell out a large
chunk of our wallet for that. I think you might find this link helpful

http://www.vbdotnetheaven.com/Code/Jun2003/2006.asp