• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Beginning initialization...

ec) EXCEPTION CONTEXT

dec) DEFAULT EXCEPTION CONTEXT



ERROR
System.ComponentModel.Composition.ImportCardinalityMismatchException: No valid exports were found that match the constraint '((exportDefinition.ContractName == "SelfValidationCall") AndAlso (exportDefinition.Metadata.ContainsKey("ExportTypeIdentity") AndAlso "System.Void(Audax.Validator.Context,Hydrus.Scripting.ElementNode)".Equals(exportDefinition.Metadata.get_Item("ExportTypeIdentity"))))', invalid exports may have been rejected.
at System.ComponentModel.Composition.Hosting.ExportProvider.GetExports(ImportDefinition definition, AtomicComposition atomicComposition)
at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportCore[T](String contractName)
at Audax.Validator.Common.Validate(Context c, ElementNode module)
at Audax.Validator.Common.ProcessModuleBody(Context c, ElementNode module, Scope scope)
at Audax.Validator.Module..ctor(Context c, Scope scope)
at Audax.Validator.Module.Create(Context c, Scope scope)
at Audax.Validator.GameValidator..ctor(CFilePath path)
at Audax.Validator.ValidationManager.ParseGameFiles()


Failure was a MEF error.

Catalog is a directory catalog
Full path: C:\USERS\THOMAS\DESKTOP\VALIDATOR\AUDAX.VALIDATOR\EXTENSION\BIN
Path: ..\Extension\Bin
Search pattern: *.dll
Loaded file: C:\USERS\THOMAS\DESKTOP\VALIDATOR\AUDAX.VALIDATOR\EXTENSION\BIN\AUDAX.VALIDATOR.CLAUSEWITZ.DLL
Loaded file: C:\USERS\THOMAS\DESKTOP\VALIDATOR\AUDAX.VALIDATOR\EXTENSION\BIN\AUDAX.VALIDATOR.EXTENSION.DLL

Part listings are as follows:
Since there were problems with initial loading, validation cannot continue.

this is the error i get with the version 0.8.20

and this one is version 0.8.0

ERROR
System.ComponentModel.Composition.ImportCardinalityMismatchException: No valid exports were found that match the constraint '((exportDefinition.ContractName == "SelfValidationCall") AndAlso (exportDefinition.Metadata.ContainsKey("ExportTypeIdentity") AndAlso "System.Void(Audax.Clausewitz.Validator.Context,Hydrus.Scripting.ElementNode)".Equals(exportDefinition.Metadata.get_Item("ExportTypeIdentity"))))', invalid exports may have been rejected.
at System.ComponentModel.Composition.Hosting.ExportProvider.GetExports(ImportDefinition definition, AtomicComposition atomicComposition)
at System.ComponentModel.Composition.Hosting.ExportProvider.GetExportCore[T](String contractName)
at Audax.Clausewitz.Validator.Common.Validate(Context c, ElementNode module)
at Audax.Clausewitz.Validator.Common.ProcessModuleBody(Context c, ElementNode module, Scope scope)
at Audax.Clausewitz.Validator.Module..ctor(Context c, Scope scope)
at Audax.Clausewitz.Validator.Module.Create(Context c, Scope scope)
at Audax.Clausewitz.Validator.GameValidator..ctor(CFilePath path)
at Audax.Clausewitz.Validator.ValidationManager.ParseGameFiles()
Since there were problems with initial loading, validation cannot continue.
 
v0.8.21 b RC5 has been released

Download here

NOTE: Support for vanilla (i.e. non-VV) has been disabled by default. If you want to enable them, double-click on EnableOlderVersions.bat after unzipping. If everyone hates this, then post a lot of "I HATE YOU YOU LOSER" posts and I'll change it back.
 
The next version released will be v1.0 (with a number of release candidates). Unless patches or expansions come out, or there are other important issues, it will be the last version released that changes Rome validation, and future releases of the Validator will not be announced in this thread. So if there are any issues you want to bring up, now is the chance (because later on, it will be too late).
 
The 1.0 cycle has arrived. This will be the last version released for Rome (barring patches, expansions, or breaking issues). Therefore, your feedback, especially bug reports, is more important than ever.

Release Candidate 1 is available: Download here

The final v1.0 will be released when a release candidate has been out for three weeks and no issues have been reported (note: this includes issues for Hoi3, Vic2, Eu3, and Rome).
 
The 1.0 release cycle is continuing. This will be the last version released for Rome (barring patches, expansions, or breaking issues). Therefore, your feedback, especially bug reports, is more important than ever.

Release Candidate 4 is available: Download here

The final v1.0 will be released when a release candidate has been out for three weeks and no issues have been reported (note: this includes issues for Vic2, Eu3, and Rome).
 
A little something I've been working on that should make customizing the Validator much easier. Any requests are welcome.

Code:
# This is the settings file for EU3 and its expansions
# To use, copy this to your EU3 installation base or mod directory and name it "ValidatorSettings.txt"
# If you don't want to use it then don't copy it.
# By default, everything is commented out. Uncomment something to use it.

###########################################
# COUNTRY COLORS
###########################################

# Checks that all countries are included within the country colors file.
#AddFlag = CountryColors.ReportMissingCountries
 
The 1.0 release cycle is continuing. This will be the last version released for Rome (barring patches, expansions, or breaking issues). Therefore, your feedback, especially bug reports, is more important than ever.

Release Candidate 8 is available: Download here

You can tweak a number of validation settings by copying a text file from the SettingsFiles folder into the game directory or mod directory, and naming it ValidatorSettings.txt. Then just open it and modify. This is where many of the former settings got moved to.

Note that several bugs were fixed; however the fixes of these bugs may have caused some false positives to creep in. As always, please report them here.

The final v1.0 will be released when a release candidate has been out for three weeks and no issues have been reported (note: this includes issues for Vic2, Eu3, and Rome).
 
The 1.0 release cycle is continuing. This will be the last version released for this game (barring patches, expansions, or breaking issues). Therefore, your feedback, especially bug reports, is more important than ever.

1.0 Release Candidate 9 is available: Download here

You can tweak a number of validation settings by copying a text file from the SettingsFiles folder into the game directory or mod directory, and naming it ValidatorSettings.txt. Then just open it and modify. This is where many of the former settings got moved to.

Also, comment ignore is here! Simply put
Code:
# Audax Validator "." Ignore_XXXX
in front of the node causing the error that you want to ignore. XXXX is an error code, found in Information/errorCodes.txt. So far only a few errors are supported, so tell me which ones you really want to be able to ignore. For more information, see DidYouKnow.pdf, in the dowload.

The final v1.0 will be released when a release candidate has been out for three weeks and no issues have been reported (note: this includes issues for Vic2, Eu3, and Rome).
 
The 1.0 release cycle is continuing. This will be the last version released for this game (barring patches, expansions, or breaking issues). Therefore, your feedback, especially bug reports, is more important than ever.

1.0 Release Candidate 10 is available: Download here

You can tweak a number of validation settings by copying a text file from the SettingsFiles folder into the game directory or mod directory, and naming it ValidatorSettings.txt. Then just open it and modify. This is where many of the former settings got moved to.

Also, comment ignore is here! Simply put
Code:
# Audax Validator "." Ignore_XXXX
in front of the node causing the error that you want to ignore. XXXX is an error code, found in Information/errorCodes.txt. So far only a few errors are supported, so tell me which ones you really want to be able to ignore. For more information, see DidYouKnow.pdf, in the dowload.

The final v1.0 will be released when a release candidate has been out for three weeks and no issues have been reported (note: this includes issues for Vic2, Eu3, and Rome).