1
Vote

Error installing patterns after nupattern update

description

Hi,
I have recently upgraded the version of NuPattern extension in my Visual Studio but it appears that the patterns that I developed in the past cannot be installed anymore. I get a weird error saying that installing the pattern would result in breaking the nupattern builder extension.

Any known solution for this kind of issue? Do I need to migrate my patterns? Can I install the previous version of nupattern back?

comments

jezzsa wrote Jun 22, 2014 at 5:11 AM

Hi eridac,

This might be the case if your patterns are from a older version that cannot be auto-updated.
What version of NuPattern did you build your old patterns with?

If before 1.3.20.0 we had significant platform (and binaries) changes from earlier versions to 1.3.20.0 in NuPattern that cannot be auto-migrated, but we do have explicit instructions on how from each version in the progression.
If that is the case, you need to read the 'Release Notes' for each version to migrate from your version in incremental steps.

Let us know what your specific case is, and we can guide you.

eridac wrote Jul 1, 2014 at 1:20 PM

Hi Jezzsa,
thanks for your reply.
I upgraded from v1.3.22 to the latest version of the extensions and yet I had issue installing previously developed patterns.
As a consequence, I did a rollback to the version i was using before. Uninstalled the latest version and installed clean v1.3.22.
I was hoping not to have any problem with this any longer but that is unfortunately not the case. I am now able to install the patterns that I have in my repository, but i encounter problems while editing patterns developed before. When trying to test the patterns using the VS experimental instance i get the following:

NuPattern.Runtime.UriProviders.TextTemplate Warning: 0 : Warning: Compiling transformation: Assuming assembly reference 'NuPattern.Runtime.Extensibility, Version=1.3.22.0, Culture=neutral, PublicKeyToken=24c7786d4a8b1a88' matches 'NuPattern.Runtime.Extensibility, Version=1.4.24.0, Culture=neutral, PublicKeyToken=24c7786d4a8b1a88', you may need to supply runtime policy. Line: 0 Column: 0
NuPattern.Runtime.UriProviders.TextTemplate Error: 0 : Error: Running transformation: System.IO.FileNotFoundException: Could not load file or assembly 'NuPattern.Runtime.Extensibility, Version=1.3.22.0, Culture=neutral, PublicKeyToken=24c7786d4a8b1a88' or one of its dependencies. The system cannot find the file specified.
File name: 'NuPattern.Runtime.Extensibility, Version=1.3.22.0, Culture=neutral, PublicKeyToken=24c7786d4a8b1a88'
at Microsoft.VisualStudio.TextTemplating637BDAAF445A2D552CF1A9EF2868F315BBA7544141BEF4EAD0290C38C9BEA5882E160050CA0130BCC9AB4ACC5A10A77D9EC74DBBB9FC0331F0B92D058AA47BC8.GeneratedTextTransformation.TransformText()
at System.Dynamic.UpdateDelegates.UpdateAndExecute1[T0,TRet](CallSite site, T0 arg0)
at Microsoft.VisualStudio.TextTemplating.TransformationRunner.PerformTransformation()

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: 0 Column: 0


Looks like there's still some confusion on the installed version, although I am sure that I have all freshly installed dlls.

Any suggestion?

jezzsa wrote Jul 2, 2014 at 9:22 AM

If the problem is only with the experimental instance you can reset that easily enough.
Simply run the 'Reset the Visual Studio 201X Experimental Instance' command line tool that visual studio installs for you.
Then rebuild your toolkit and CTRL+F5 to run in experimental again.

If that does not work, then just delete the whole directory: %localappdata%\Microsoft\VisualStudio\12.0Exp
and rebuild and CTRL+F5 again.

try that and let me know how it goes.

eridac wrote Jul 2, 2014 at 9:55 AM

It worked like a charm.
Thanks!