Visual Guard is a tool ready to use which implements Role Based Access Control in your .Net applications. By adding this security solution you will be able to easily manage users and their access to your applications and to confidential data. With Visual Guard you can define what each user can do, see and modify in it.
 
Visual Guard 2.6 adds Logging and Auditing features. You can keep track of users' activity and review it later. Visual Guard can log important actions in the application (financial transaction for instance) and the administration console (invalid connexion attempt, locked account, password modification).
 
Learn more about Visual Guard...
 
Try it now: ask for an evaluation version!

Tip:  The problem only exists in Appeon for .NET version. The cause of this error is that the user does not have sufficient permission of using .Net framework and IIS server. Usually you should follow the instructions below to resolve the issue.
 
Step one: Grant proper rights to use .Net Framework with the two commands in the CMD window. 1. Navigate to C:\WINDOWS\Microsoft.NET\Framework\2.0.****; 2. Execute the command line "aspnet_regiis -ga users"; 3. Execute the command line "aspnet_regiis -i ".
 
Step two: Grant Internet Guest Account and IIS Process Account proper rights to manipulate the Web Root folder.
 
1. Go to C:\Inetpub folder and right click the wwwroot folder, select the Properties items and select the Security tab page;
 
2. Add IIS_WPG group if it is not list in the box "Group or user names";
 
3. Allow the IIS_WPG group get the Full Control permission.
 

Note: this problem does NOT occur with the Appeon modified PFC 10.5 which can work seamlessly with Web deployment. This reported case only exists in the previous PFC support.
 
Tip:  Appeon can directly support PFC application without applying ACF since Appeon 5.0. However because of the ClassDefinition, an Appeon unsupported feature, two function points in the PFC application will not work correctly. To eliminate the influence caused by the ClassDefinition, you need do the following modifications.
 
Modification one: You need to apply this modification in the of_setresize function for the pfc_w_master object.
 
Original scripts:
 
classdefinition lcd_class
lcd_class = this.ClassDefinition
 
li_vars = UpperBound ( lcd_class.VariableList )
For li_v = 1 to li_vars
If lcd_class.VariableList[li_v].Name = "width" Then li_origwidth = Integer
( lcd_class.VariableList[li_v].InitialValue )
If lcd_class.VariableList[li_v].Name = "height" Then li_origheight = Integer
( lcd_class.VariableList[li_v].InitialValue )
If li_origwidth > 0 And li_origheight > 0 Then Exit
Next
inv_resize.of_SetOrigSize ( li_origwidth, li_origheight )
 
Modified scripts:
 
/* Get class definition for current window and extract the width and height */
inv_resize.of_SetOrigSize ( this.width, this.height )
 
Modification two: You need to apply this modification in several functions in the pfc_n_cst_luw object, including of_accepttext, of_postupdate, of_updateprep, of_updatespending, of_validation, of_update, of_isselfupdatingobject.
 
Original scripts:
 
lb_defined = inv_metaclass.of_isFunctionDefined & (lpo_tocheck.ClassDefinition, "of_PostUpdate", ls_args)
 
Modified scripts:
 
If lpo_tocheck.TriggerEvent("pfc_descendant") = 1 Then
lb_defined = True
Else
lb_defined = False
End If