From: Tom Shelton on
On 2010-02-19, Mike Williams <Mike(a)WhiskyAndCoke.com> wrote:
> "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message
> news:5v3tn5hsbjg2jtg1h2rjkkk4b7im7skvop(a)4ax.com...
>
>> � Not if it's a .Net product. My app depends on drag and drop
>> � deployment with no install. .Net solutions don't allow for that.
>>
>> for XP it's a one-time deployment.
>
> Last time I checked, "one" was more than "none"!

Definately. And since most buisness are still using XP, then Vista or 7,
there is definately a possibility that you might have to install it...

--
Tom Shelton
From: Karl E. Peterson on
Tom Shelton wrote:
> On 2010-02-19, Mike Williams <Mike(a)WhiskyAndCoke.com> wrote:
>> "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message
>> news:5v3tn5hsbjg2jtg1h2rjkkk4b7im7skvop(a)4ax.com...
>>
>>> � Not if it's a .Net product. My app depends on drag and drop
>>> � deployment with no install. .Net solutions don't allow for that.
>>>
>>> for XP it's a one-time deployment.
>>
>> Last time I checked, "one" was more than "none"!
>
> Definately. And since most buisness are still using XP, then Vista or 7,
> there is definately a possibility that you might have to install it...

And even in Vista and 7, there's no certainty that the flamework
version your app is dependent upon is there, right?

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Tom Shelton on
On 2010-02-19, Karl E Peterson <karl(a)exmvps.org> wrote:
> Tom Shelton wrote:
>> On 2010-02-19, Mike Williams <Mike(a)WhiskyAndCoke.com> wrote:
>>> "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message
>>> news:5v3tn5hsbjg2jtg1h2rjkkk4b7im7skvop(a)4ax.com...
>>>
>>>> � Not if it's a .Net product. My app depends on drag and drop
>>>> � deployment with no install. .Net solutions don't allow for that.
>>>>
>>>> for XP it's a one-time deployment.
>>>
>>> Last time I checked, "one" was more than "none"!
>>
>> Definately. And since most buisness are still using XP, then Vista or 7,
>> there is definately a possibility that you might have to install it...
>
> And even in Vista and 7, there's no certainty that the flamework
> version your app is dependent upon is there, right?
>

Vista has 3.0 by default. So, you can just target 2.0 or 3.0 and your fine.
If you target 3.5, then you MAY have to install there as well.

--
Tom Shelton
From: Paul Clement on
On Fri, 19 Feb 2010 07:45:57 -0800, Tom Shelton <tom_shelton(a)comcastXXXXXXX.net> wrote:

� >> � Not if it's a .Net product. My app depends on drag and drop
� >> � deployment with no install. .Net solutions don't allow for that.
� >>
� >> for XP it's a one-time deployment.
� >
� > Last time I checked, "one" was more than "none"!

� Definately. And since most buisness are still using XP, then Vista or 7,
� there is definately a possibility that you might have to install it...

Or deploy it with other Windows Updates as many companies do.


Paul
~~~~
Microsoft MVP (Visual Basic)
From: Tom Shelton on
On 2010-02-19, Paul Clement <UseAdddressAtEndofMessage(a)swspectrum.com> wrote:
> On Fri, 19 Feb 2010 07:45:57 -0800, Tom Shelton <tom_shelton(a)comcastXXXXXXX.net> wrote:
>
> � >> � Not if it's a .Net product. My app depends on drag and drop
> � >> � deployment with no install. .Net solutions don't allow for that.
> � >>
> � >> for XP it's a one-time deployment.
> � >
> � > Last time I checked, "one" was more than "none"!
> �
> � Definately. And since most buisness are still using XP, then Vista or 7,
> � there is definately a possibility that you might have to install it...
>
> Or deploy it with other Windows Updates as many companies do.

Yes - that is an option. If the company it policy allows it. I've yet to run
into one that doesn't... But you never know :)

--
Tom Shelton