Visual Basic (Declaration) | |
---|---|
Public Shared Property IgnorePatterns As List(Of String) |
Visual Basic (Usage) | ![]() |
---|---|
Dim value As List(Of String) CompositionHost.IgnorePatterns = value value = CompositionHost.IgnorePatterns |
C# | |
---|---|
public static List<string> IgnorePatterns {get; set;} |
C++/CLI | |
---|---|
public: static property List<String^>^ IgnorePatterns { List<String^>^ get(); void set ( List<String^>^ value); } |
C# | ![]() |
---|---|
<code lang="C#"> // At application startup CompositionHost.SearchPatterns.Clear(); CompositionHost.SearchPatterns.Add("DomainModel.dll"); // Add whatever assemblies you need probed |
You may add and remove patterns from the list to suit your needs. You may supply a Regex pattern or a simple wildcard pattern. If you supply a simple pattern it will be converted to a Regex pattern. The conversion escapes the "." (dot) character, and changes "*" (wildcard) to ".*".
Use the SearchPatterns and IgnorePatterns to improve the startup time of your application. The only assemblies which must be probed for discovery purposes are those containing your entity models, extensible components and known types. If many unnecessary assemblies are probed the startup time of your application will suffer. However, if assemblies which should be probed are not, your application will not work correctly. Always check the debug log to see which assemblies have been probed.
You should avoid clearing the IgnorePatterns altogether, and instead add patterns as needed. If the "IdeaBlade.*" assemblies are probed your program will not work correctly, and if "System.*" and other system-related assemblies are probed performance will suffer. The default IgnorePatterns exclude these assemblies.
SearchPatterns are applied before IgnorePatterns.
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