Intersoft WebCombo Documentation
ScriptDirectory Property
See Also  Send Feedback
ISNet.WebUI.WebCombo Namespace > WebCombo Class : ScriptDirectory Property






Overriden.

Syntax

Visual Basic (Declaration) 
<CategoryAttribute("Client Script Directory")>
<BindableAttribute(Bindable=True, Direction=BindingDirection.OneWay)>
<DefaultValueAttribute()>
Public Overrides Property ScriptDirectory As String
Visual Basic (Usage)Copy Code
Dim instance As WebCombo
Dim value As String
 
instance.ScriptDirectory = value
 
value = instance.ScriptDirectory
C# 
[CategoryAttribute("Client Script Directory")]
[BindableAttribute(Bindable=true, Direction=BindingDirection.OneWay)]
[DefaultValueAttribute()]
public override string ScriptDirectory {get; set;}
Delphi 
public read-write property ScriptDirectory: String; override;
JScript 
CategoryAttribute("Client Script Directory")
BindableAttribute(Bindable=, Direction=BindingDirection.OneWay)
DefaultValueAttribute()
public override function get,set ScriptDirectory : String
Managed Extensions for C++ 
[CategoryAttribute("Client Script Directory")]
[BindableAttribute(Bindable=true, Direction=BindingDirection.OneWay)]
[DefaultValueAttribute()]
public: __property string* get_ScriptDirectory() override;
public: __property void set_ScriptDirectory( 
   string* value
) override;
C++/CLI 
[CategoryAttribute("Client Script Directory")]
[BindableAttribute(Bindable=true, Direction=BindingDirection.OneWay)]
[DefaultValueAttribute()]
public:
property String^ ScriptDirectory {
   String^ get() override;
   void set (    String^ value) override;
}

Remarks

In previous versions, resources of product such as scripts are stored in ScriptDirectory. For example, WebCombo's resources are stored in /CommonLibrary/WebCombo/V4_0_7200.

Since WebCombo.NET v4.0 uses a new SmartWebResources Framework, the resources in script directory are now embedded into .NET assembly. Unlike ASP.NET’s built-in Web Resources which embeds client resources in main assembly, SmartWebResources stores each product’s client resources in separate assembly. This enables flexible update (maintenance) to the client resources without has to rebuild the main server-side assembly.

With SmartWebResources enabled, you no longer need to aware what you should do to configure the client scripts virtual directory, or where to locate/store it. You simply ensure that the resources assemblies are in the Bin folder of your application. For more information, read How-to: Configure SmartWebResources in a web application.

The "Auto" mode of SmartWebResources will attempt to use SmartWebResources whenever possible. When it detects invalid configuration or usage of product that does not support SmartWebResources, it will automatically fallback to traditional physical client resources approach. For instance, if ScriptDirectory or SharedScriptDirectory has been changed (not default), SmartWebResources detects whether an existing web application was configured to use specific script directory other than the default (for best compatibility).  

If ScriptDirectory is customized, but ImagesDirectory is using default value (not customized), the SmartWebResources will fallback to ResourceOnly mode. That means, images and other client resources will still be handled by SmartWebResources. For more information, you can read the SmartWebResources™ modes.

Requirements

Target Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family, Windows Vista, Windows Server 2008 family

See Also

© 2012 Intersoft Solutions Corp. All Rights Reserved.