Very troubling problems running on Vista Beta

> If this is the wrong NG to post this please point me to the correct
> place...
>
> I've had a few people try my VB app on Vista Beta installations. One of
> the problems I'm seeing is that my app can't seem to write information to
> the installation folder. Yet no error is being raised when it tries to
> write out information. As far as the app is concerned there's no problem.
> I noticed this when people who tested the app couldn't find the app's log
> file. When they send me directory listings of everything in the
> installation folder it was clear that there was nothing present that
> wasn't put there by the installation utility.
>
> This really has me troubled. I don't have a Vista Beta installation of my
> own to test with. My app writes both a log file and the user's data file
> to the installation folder by default. Not only that, my app frequently
> needs to be updated. I handle this through a utility that downloads the
> newer .exe and deletes the old. If it can't download and write out the
> new .exe then my app can't be updated! I can handle (though not be happy
> with) the need to write both the log and data file to the \Documents and
> Settings\(user name)\Application Data\ folder if Microsoft forces me to
> do so. But if the app can't be updated I'm really in a world of hurt.
>
> Has anyone else encountered this problem? Anyone know why an app would
> not be allowed to write data to its installation folder yet not get an
> error from Vista when it isn't allowed to do so?
>
>
>

> This is really a developer issue, its best if you post it at the following
> link:
> http://forums.microsoft.com/msdn/sho...d=120&siteid=1

> If this is the wrong NG to post this please point me to the correct
> place...
>
> I've had a few people try my VB app on Vista Beta installations. One of
> the problems I'm seeing is that my app can't seem to write information to
> the installation folder. Yet no error is being raised when it tries to
> write out information. As far as the app is concerned there's no problem.
> I noticed this when people who tested the app couldn't find the app's log
> file. When they send me directory listings of everything in the
> installation folder it was clear that there was nothing present that
> wasn't put there by the installation utility.
>
> This really has me troubled. I don't have a Vista Beta installation of my
> own to test with. My app writes both a log file and the user's data file
> to the installation folder by default. Not only that, my app frequently
> needs to be updated. I handle this through a utility that downloads the
> newer .exe and deletes the old. If it can't download and write out the
> new .exe then my app can't be updated! I can handle (though not be happy
> with) the need to write both the log and data file to the \Documents and
> Settings\(user name)\Application Data\ folder if Microsoft forces me to
> do so. But if the app can't be updated I'm really in a world of hurt.
>
> Has anyone else encountered this problem? Anyone know why an app would
> not be allowed to write data to its installation folder yet not get an
> error from Vista when it isn't allowed to do so?
>
>
>

>If this is the wrong NG to post this please point me to the correct
>place...
>
>I've had a few people try my VB app on Vista Beta installations. One of
>the problems I'm seeing is that my app can't seem to write information to
>the installation folder. Yet no error is being raised when it tries to
>write out information. As far as the app is concerned there's no problem.
> I noticed this when people who tested the app couldn't find the app's log file. When they send me directory listings of everything in the installation folder it was clear that there was nothing present that wasn't put there by the installation utility.
>
>This really has me troubled. I don't have a Vista Beta installation of my
>own to test with. My app writes both a log file and the user's data file
>to the installation folder by default. Not only that, my app frequently
>needs to be updated. I handle this through a utility that downloads the
>newer .exe and deletes the old. If it can't download and write out the
>new .exe then my app can't be updated! I can handle (though not be happy
>with) the need to write both the log and data file to the \Documents and
>Settings\(user name)\Application Data\ folder if Microsoft forces me to
>do so. But if the app can't be updated I'm really in a world of hurt.
>
>Has anyone else encountered this problem? Anyone know why an app would
>not be allowed to write data to its installation folder yet not get an
>error from Vista when it isn't allowed to do so?

> something in place for this scenario too.

> It's all part of the UAP/LUA stuff - since users generally should not be
> running with administrative privileges, they don't have the right to write
> to an application's own folder, ergo an application loaded by them has the
> same restriction.

> Dan wrote:
>

>>If this is the wrong NG to post this please point me to the correct
>>place...
>>
>>I've had a few people try my VB app on Vista Beta installations. One of
>>the problems I'm seeing is that my app can't seem to write information to
>>the installation folder. Yet no error is being raised when it tries to
>>write out information. As far as the app is concerned there's no problem.
>>I noticed this when people who tested the app couldn't find the app's log
>>file. When they send me directory listings of everything in the
>>installation folder it was clear that there was nothing present that
>>wasn't put there by the installation utility.
>>
>>This really has me troubled. I don't have a Vista Beta installation of my
>>own to test with. My app writes both a log file and the user's data file
>>to the installation folder by default. Not only that, my app frequently
>>needs to be updated. I handle this through a utility that downloads the
>>newer .exe and deletes the old. If it can't download and write out the
>>new .exe then my app can't be updated! I can handle (though not be happy
>>with) the need to write both the log and data file to the \Documents and
>>Settings\(user name)\Application Data\ folder if Microsoft forces me to
>>do so. But if the app can't be updated I'm really in a world of hurt.
>>
>>Has anyone else encountered this problem? Anyone know why an app would
>>not be allowed to write data to its installation folder yet not get an
>>error from Vista when it isn't allowed to do so?

>
> Vista has mechanisms to automatically redirect writes to an application
> folder to a folder within the user's own space. So you should find the log
> files have been auto-relocated to somewhere deep within \Users\<username>.
>
> I don't know about application updates - but I imagine that MS have
> something in place for this scenario too.
>
> It's all part of the UAP/LUA stuff - since users generally should not be
> running with administrative privileges, they don't have the right to write
> to an application's own folder, ergo an application loaded by them has the
> same restriction.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.

>> I don't know about application updates - but I imagine that MS have
>> something in place for this scenario too.

>
> You can do this using Visual Studio 2005, and the "Publish" settings of
> your application. You can configure your applications to look on a web
> server to download the latest build of your product - it's really easy to
> set up, and with Windows Server 2003 running with IIS, work's an absolute
> treat.
>

>> It's all part of the UAP/LUA stuff - since users generally should not be
>> running with administrative privileges, they don't have the right to
>> write to an application's own folder, ergo an application loaded by them
>> has the same restriction.

>
> Couldn't have said it better myself ) So yeh, if you can get TechNet or
> TechNet Plus, you can then get yourself a copy of Vista to test with. If
> you check out the UAP Guidelines,
> http://www.microsoft.com/technet/win...at/uaprot.mspx -
> you might find that useful.
>
> All the best )
>
> --
> Zack Whittaker
> Microsoft Beta (Windows Server R2 Beta Mentor)
> » ZackNET Enterprises: www.zacknet.co.uk
> » MSBlog on ResDev: http://msblog.resdev.net
> » ZackNET Forum: www.zacknet.co.uk/forum
> » VistaBase: www.zacknet.co.uk/vistabase
> » This mailing is provided "as is" with no warranties, and confers no
> rights. All opinions expressed are those of myself unless stated so, and
> not
> of my employer, best friend, mother or cat. Let's be clear on that one!
>
>
> --- Original message follows ---
> "Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
> news:xn0eji09yb6wqt001y@msnews.microsoft.com...

>> Dan wrote:
>>

>>>If this is the wrong NG to post this please point me to the correct
>>>place...
>>>
>>>I've had a few people try my VB app on Vista Beta installations. One of
>>>the problems I'm seeing is that my app can't seem to write information to
>>>the installation folder. Yet no error is being raised when it tries to
>>>write out information. As far as the app is concerned there's no
>>>problem. I noticed this when people who tested the app couldn't find the
>>>app's log file. When they send me directory listings of everything in
>>>the installation folder it was clear that there was nothing present that
>>>wasn't put there by the installation utility.
>>>
>>>This really has me troubled. I don't have a Vista Beta installation of
>>>my own to test with. My app writes both a log file and the user's data
>>>file to the installation folder by default. Not only that, my app
>>>frequently needs to be updated. I handle this through a utility that
>>>downloads the newer .exe and deletes the old. If it can't download and
>>>write out the new .exe then my app can't be updated! I can handle
>>>(though not be happy with) the need to write both the log and data file
>>>to the \Documents and Settings\(user name)\Application Data\ folder if
>>>Microsoft forces me to do so. But if the app can't be updated I'm really
>>>in a world of hurt.
>>>
>>>Has anyone else encountered this problem? Anyone know why an app would
>>>not be allowed to write data to its installation folder yet not get an
>>>error from Vista when it isn't allowed to do so?

>>
>> Vista has mechanisms to automatically redirect writes to an application
>> folder to a folder within the user's own space. So you should find the
>> log files have been auto-relocated to somewhere deep within
>> \Users\<username>.
>>
>> I don't know about application updates - but I imagine that MS have
>> something in place for this scenario too.
>>
>> It's all part of the UAP/LUA stuff - since users generally should not be
>> running with administrative privileges, they don't have the right to
>> write to an application's own folder, ergo an application loaded by them
>> has the same restriction.
>>
>> --
>> Steve Foster [SBS MVP]
>> ---------------------------------------
>> MVPs do not work for Microsoft. Please reply only to the newsgroups.

>
>

> Is it that thing called Click Once? I remember Microsoft pushing it a lot
> at PDC 2003.
> --
> --
> Andre
> Windows Connect | http://www.windowsconnected.com
> Extended64 | http://www.extended64.com
> Blog | http://www.extended64.com/blogs/andre
> http://spaces.msn.com/members/adacosta
>
> "Zack Whittaker (R2 Mentor)" <admin@zacknet.co.uk> wrote in message
> news:%23XGS2ExQGHA.5728@tk2msftngp13.phx.gbl...

>>> I don't know about application updates - but I imagine that MS have
>>> something in place for this scenario too.

>>
>> You can do this using Visual Studio 2005, and the "Publish" settings of
>> your application. You can configure your applications to look on a web
>> server to download the latest build of your product - it's really easy to
>> set up, and with Windows Server 2003 running with IIS, work's an absolute
>> treat.
>>

>>> It's all part of the UAP/LUA stuff - since users generally should not be
>>> running with administrative privileges, they don't have the right to
>>> write to an application's own folder, ergo an application loaded by them
>>> has the same restriction.

>>
>> Couldn't have said it better myself ) So yeh, if you can get TechNet or
>> TechNet Plus, you can then get yourself a copy of Vista to test with. If
>> you check out the UAP Guidelines,
>> http://www.microsoft.com/technet/win...at/uaprot.mspx -
>> you might find that useful.
>>
>> All the best )
>>
>> --
>> Zack Whittaker
>> Microsoft Beta (Windows Server R2 Beta Mentor)
>> » ZackNET Enterprises: www.zacknet.co.uk
>> » MSBlog on ResDev: http://msblog.resdev.net
>> » ZackNET Forum: www.zacknet.co.uk/forum
>> » VistaBase: www.zacknet.co.uk/vistabase
>> » This mailing is provided "as is" with no warranties, and confers no
>> rights. All opinions expressed are those of myself unless stated so, and
>> not
>> of my employer, best friend, mother or cat. Let's be clear on that one!
>>
>>
>> --- Original message follows ---
>> "Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
>> news:xn0eji09yb6wqt001y@msnews.microsoft.com...

>>> Dan wrote:
>>>
>>>>If this is the wrong NG to post this please point me to the correct
>>>>place...
>>>>
>>>>I've had a few people try my VB app on Vista Beta installations. One of
>>>>the problems I'm seeing is that my app can't seem to write information
>>>>to the installation folder. Yet no error is being raised when it tries
>>>>to write out information. As far as the app is concerned there's no
>>>>problem. I noticed this when people who tested the app couldn't find the
>>>>app's log file. When they send me directory listings of everything in
>>>>the installation folder it was clear that there was nothing present that
>>>>wasn't put there by the installation utility.
>>>>
>>>>This really has me troubled. I don't have a Vista Beta installation of
>>>>my own to test with. My app writes both a log file and the user's data
>>>>file to the installation folder by default. Not only that, my app
>>>>frequently needs to be updated. I handle this through a utility that
>>>>downloads the newer .exe and deletes the old. If it can't download and
>>>>write out the new .exe then my app can't be updated! I can handle
>>>>(though not be happy with) the need to write both the log and data file
>>>>to the \Documents and Settings\(user name)\Application Data\ folder if
>>>>Microsoft forces me to do so. But if the app can't be updated I'm
>>>>really in a world of hurt.
>>>>
>>>>Has anyone else encountered this problem? Anyone know why an app would
>>>>not be allowed to write data to its installation folder yet not get an
>>>>error from Vista when it isn't allowed to do so?
>>>
>>> Vista has mechanisms to automatically redirect writes to an application
>>> folder to a folder within the user's own space. So you should find the
>>> log files have been auto-relocated to somewhere deep within
>>> \Users\<username>.
>>>
>>> I don't know about application updates - but I imagine that MS have
>>> something in place for this scenario too.
>>>
>>> It's all part of the UAP/LUA stuff - since users generally should not be
>>> running with administrative privileges, they don't have the right to
>>> write to an application's own folder, ergo an application loaded by them
>>> has the same restriction.
>>>
>>> --
>>> Steve Foster [SBS MVP]
>>> ---------------------------------------
>>> MVPs do not work for Microsoft. Please reply only to the newsgroups.

>>
>>

>
>

>> I don't know about application updates - but I imagine that MS have
>> something in place for this scenario too.

>
> You can do this using Visual Studio 2005, and the "Publish" settings of
> your application. You can configure your applications to look on a web
> server to download the latest build of your product - it's really easy to
> set up, and with Windows Server 2003 running with IIS, work's an absolute
> treat.

>> It's all part of the UAP/LUA stuff - since users generally should not be
>> running with administrative privileges, they don't have the right to
>> write to an application's own folder, ergo an application loaded by them
>> has the same restriction.

>
> Couldn't have said it better myself ) So yeh, if you can get TechNet or
> TechNet Plus, you can then get yourself a copy of Vista to test with.

> check out the UAP Guidelines,
> http://www.microsoft.com/technet/win...at/uaprot.mspx -
> you might find that useful.