I am trying to build a setup project with VS 2005, running under Vista.
During the build process, I keep getting the error:
Error 14 Could not create the file
'C:\Users\kelly\AppData\Local\Temp\VSI49A.tmp' 'Access is denied.'
(The actual VSI... file name changes each time)
I have also tried importing into VS2008 and get the same error.
VS2005 is started with adminsitrator permissions, I have tried making new
setup projects, I have double checked I have permissions in the temp folder
and I have emptied the whole temp folder.
The only time it works, is if I do a reboot, and then a build. After this
time though, I get the error again.
I got something similar but with VS 2008 while building an MSI:
Packaging file 'Interop.ADODB.dll'...
ERROR: Could not create the file
'C:\Users\JTB\AppData\Local\Temp\VSIA76E.tmp' 'Access is denied.'
ERROR: Unrecoverable build error
Did you find any solution yourself?
Jimmy Bergmark
JTB World
Website: http://www.jtbworld.com
Blog: http://blog.jtbworld.com
> I am trying to build a setup project with VS 2005, running under Vista.
>
[quoted text clipped - 13 lines]
> The only time it works, is if I do a reboot, and then a build. After this
> time though, I get the error again.
JTB World - 21 May 2008 15:49 GMT
Here is the solution to the problem that worked for me.
I fired up cmd as administrator and run:
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\MSI
Tools\mergemod.dll"
Via http://msdn.microsoft.com/en-us/library/ms228633(VS.80).aspx and
http://support.microsoft.com/kb/329214
Jimmy Bergmark
JTB World
Website: http://www.jtbworld.com
Blog: http://blog.jtbworld.com
> I got something similar but with VS 2008 while building an MSI:
> Packaging file 'Interop.ADODB.dll'...
[quoted text clipped - 26 lines]
> > The only time it works, is if I do a reboot, and then a build. After this
> > time though, I get the error again.
Dave Kelly - 21 May 2008 17:36 GMT
I gave up trying and switched to ClickOnce for that app.
Thanks for the info and the link, I'll check it out.
> Here is the solution to the problem that worked for me.
> I fired up cmd as administrator and run:
[quoted text clipped - 39 lines]
> > > The only time it works, is if I do a reboot, and then a build. After this
> > > time though, I get the error again.