I think it is created when the Visual Basic logging mechanism fires up. You
can work around it but that is a lot of hassle too. I'm not using isolated
storage.
The assembly name is just morphed because of code signing (so I can get the
code into the GAC for a quicker first run).
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: 20 April 2008 21:27
To: 'Ryan O'Neill'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Recursive folder deletion
That folder is the folder you get when you use Isolated Storage in .NET 2.0.
I'd have to say that an application installed to the local disk isn't really
the target market for that - it's more for code running in restricted
security, such as applications run from the network or IE plugins.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan O'Neill
Sent: 16 April 2008 16:08
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Recursive folder deletion
I'm adding a cleanup routine to the installer we have and the .Net framework
is making it difficult by adding a folder under AppData that is based on the
strong name of the assembly.
This means that I get a folder named MyApp_StrongName_657235673256732765
which changes each time I compile as the hash changes too.
I know the parent folder is mine so it is safe to delete all below that. Has
anyone else come across deleting directory trees? I appreciate it is
dangerous but I can't see an easy way around it.
Regards
Ryan
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
