HI,

it's actually very easy. You need to change your component builder and override one function:

       public virtual IVerifierCollection BuildVerifierCollection(string name)

       {

           IVerifierCollection verifierCollection = FileTypeManager.BuildVerifierCollection();

           verifierCollection.BilingualVerifiers.Add(new GenericTagVerifier());

           return verifierCollection;

       }

Then you need to make sure the UI page is listed in you filter options so you adapt your list of UI pages by adding this ID:

info.WinFormSettingsPageIds = new string[] { "GenericVerifier_Settings" };

Regards

Patrik

HI,

it's actually very easy. You need to change your component builder and override one function:

       public virtual IVerifierCollection BuildVerifierCollection(string name)

       {

           IVerifierCollection verifierCollection = FileTypeManager.BuildVerifierCollection();

           verifierCollection.BilingualVerifiers.Add(new GenericTagVerifier());

           return verifierCollection;

       }

Then you need to make sure the UI page is listed in you filter options so you adapt your list of UI pages by adding this ID:

info.WinFormSettingsPageIds = new string[] { "GenericVerifier_Settings" };

Regards

Patrik

Thanks Patrik. I’ve tried this and I see this  error message:

Cannot load the plug-in defined in “.plugin.xml”. The plugin contains references to SDK assemblies that have not been validated for use with third party plug-ins.

This post shows that change of exposing this Generic Tag Verifier will be included in SP1. When is this supposed to be released? Is there a possible workaround?

community.sdl.com/.../2209.aspx

Hi,

are you sure that it's the generic verifier? It is on the whitelist now so it should not cause any issues.

Can you review the list of the references and make sure you don't reference any other SDL DLL?

Patrik

Patrik,

is this new? And since when? AFAIK it was not possible until "now". I'm pretty sure, this was not possible in 2011 and early 2014 versions. When we implement this in our plug-in: In which Studio versions will it work?

Cheers,

*Stefan.

Hi Patrik,

I added Sdl.FileTypeSupport.Filters.Verifiers.GenericTagVerifier and verified that is the dll causing the error.

I have installed CU3 to fix the same error for different dll, found here:

community.sdl.com/.../570.aspx.

Is there a different update I need to install?

Thanks,

Delfina

HI,

this change is only available in Studio 2014 SP1 which is currently in beta - I thought you are talking about this version.

Do you have access to it?

Patrik

Hi,

as I written below, it's going to be in Studio 2014 SP1

Patrik

Hi Patrik,

I installed the Beta of SP1 found here:

community.sdl.com/.../default.aspx.

I do get an error on this line:

info.WinFormSettingsPageIds = new string[] { "GenericVerifier_Settings" };

Error    1    'Sdl.FileTypeSupport.Framework.IntegrationApi.IFileTypeInformation' does not contain a definition for 'WinFormSetingsPageIds' and no extension method 'WinFormSetingsPageIds' accepting a first argument of type 'Sdl.FileTypeSupport.Framework.IntegrationApi.IFileTypeInformation' could be found (are you missing a using directive or an assembly reference?)  

Removing the GenericVerifier causes other errors that make the UI unusable.

Are these known issues with this Beta or am I missing something?

Thank you,

Delfina

Hi,

can you send me you component builder so I can have a look?

Regards

Patrik

Attached is the component builder and screenshots of the errors I am getting once I build the plugin.

HI,

looking into you component builder I realized that I made a mistake. Due to the fact that you deploy custom filter into a 3rd party components location where the Generic Tag Verifier is not available.

We have a plan to change the way the Generic Tag Verifier is exposed in Studio so till then this functionality will not be available out of the box.

Regards

Patrik