Print Page | Close Window

Vista related deployment problems.regarding write permisions on directories and files

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=153
Printed Date: 02-May-2025 at 1:16pm


Topic: Vista related deployment problems.regarding write permisions on directories and files
Posted By: Customer
Subject: Vista related deployment problems.regarding write permisions on directories and files
Date Posted: 12-Jul-2007 at 12:08pm

Please advise as to the proper redistrubition strategy for the DevForce dlls.  I have installed all of them in the GAC.

This allows the installing admin to run the product but noone else.

The documentation is very confuing on this issue.

I resolved the issue by setting write permissions for all users on the install directory. 

It seems that IdeaBlade creates a log in the install directory.

Is there a way to stop this behavior?




Replies:
Posted By: IdeaBlade
Date Posted: 12-Jul-2007 at 12:09pm
 

These seem to be Vista related installation issues.  We face these and similar issues ourselves.  For example, we install the IdeaBlade Tutorials in our installation directory.  This works fine on all platforms but Vista, but on Vista, a non-Administrator can not build the tutorials because of the write restrictions on the output directory.  The solution is to do as you have done and add write permissions to the install directory (thereby breaking one of the rules of Vista certification), or to copy the tutorials to a directory that your users can write to.  Everyone I know complains about this rule.

 

I am not sure that t know what you mean by the log in the install directory created by IdeaBlade.  Do you mean the DebugLog.xml file in C:\Program File\IdeaBlade DevForce?  If so, I don’t seem to see them any more.  Typically, if you run a DevForce application or utilty that uses a loose or embedded IdeaBlade.ibconfig, there will be a DebugLog.xml file deposited in the directory of the executable.   If you don’t want the log file, set the name of the Logging file to the empty string.




Print Page | Close Window