locked
DSL: Problem after update to VS 2019 RRS feed

  • Question

  • Hi to everybody reading this,

    wen have a problem after updating VS to 2019 (16.0.1): Our DSL doesnt compile anymore. Exception: A processor named 'DslDirectiveProcessor' could not be found for the directive named 'Dsl'. (Complete Exception attached further down)

    Things I tried:

    Find an information about upgrading to VS2019 Modelling Tools - Nothing

    Find information about the exception - Nothing

    Reinstalled Text Templating and Modeling SDK - Nothing.

    Now I hope somone here can help me out with a hint to the solution.

    Thanks a lot in advance!

    Soenke Pries

    Complete Exception:

    Error A processor named 'DslDirectiveProcessor' could not be found for the directive named 'Dsl'. The transformation will not be run.  The following Exception was thrown:
    System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\DSL SDK\Dsl Designer\16.0\Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.16.0.dll' or one of its dependencies. Das System kann die angegebene Datei nicht finden.
    File name: 'file:///C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Extensions\Microsoft\DSL SDK\Dsl Designer\16.0\Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.16.0.dll'
       at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
       at System.Reflection.Assembly.LoadFrom(String assemblyFile)
       at Microsoft.VisualStudio.TextTemplating.Sdk.Host.GenericTextTemplatingHost.GetDirectiveProcessorType(DirectiveProcessorRecord record)
       at Microsoft.VisualStudio.TextTemplating.Sdk.Host.GenericTextTemplatingHost.ResolveDirectiveProcessor(String processorName)
       at Microsoft.VisualStudio.TextTemplating.Engine.ProcessCustomDirectives(ITextTemplatingEngineHost host, TemplateProcessingSession session, IEnumerable`1 directivesToBeProcessed)

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    . Line=1, Column=4 Nevaris.EntityDesign.DslPackage

    Tuesday, April 16, 2019 3:45 PM

All replies

  • Hi Soenke,

    Welcome to MSDN forum.

    In which way have you added the reference to "Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.16.0.dll". Nuget or 'add reference' ?

    After I check on my side, now we have 'Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.15.0.dll' for both VS2017 and VS2019.

    Have you checked if the 'Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.16.0.dll' exists in the specific path(C:\Program Files (x86)\Microsoft Visual Studio\2019\xxx\Dsl Designer\16.0\)?

    Please check this point, and make changes to make your project add ref to the 'Microsoft.VisualStudio.Modeling.Sdk.DslDefinition.15.0.dll' instead of xxx.16.0.dll. To check if same issue persists.

    Looking forward to your reply.

    Best Regards

    Lance


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Wednesday, April 17, 2019 7:51 AM