Set-DefaultScaffolder : Operation unavailable

[korzh]

Still get the following message during installation of my package which references MvcScaffolding.VS2015:

Set-DefaultScaffolder : Operation unavailable (Exception from HRESULT: 0x800401E3 (MK_E_UNAVAILABLE))
At C:\Temp\TestMVC\packages\T4Scaffolding.Core.VS2015.1.0.3\tools\init.ps1:51 char:9
+         Set-DefaultScaffolder -Name CustomScaffolder -Scaffolder T4Scaffolding.C ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-DefaultScaffolder], COMException
    + FullyQualifiedErrorId : T4Scaffolding.Cmdlets.SetDefaultScaffolderCmdlet
 

The most strange thing is that it works well on some VS 2015 instances but fails on others. I don't see any consistent pattern in such behavior.
Scaffold command does not work we see this error during installation and performs just well if there was not such error during install.

The package I'm talking about is: EasyQuery.Mvc.Scaffolding and it worked well in VS 2012 with the old T4Scaffolding package.

[korzh]

An update.
I guess we found that "consistent pattern" (or at least I hope so). It happened that for the projects on which our package's installation failed we had old T4Scaffolding package folder in the \packages sub-folder.
After complete cleaning our package was installed without errors.
That "complete cleaning" includes:

1. Uninstalling our package
2. Removing all T4Scaffolding lines from package.config file (both for old and new ones)
3. Removing all T4Scaffolding folders from .\packages folder

So the question now: is there any to prevent errors when one of old packages is still installed in some project?

[processedbeets]

You could perhaps check for the minimum version that you do want to support and throw an exception with a meaningful error message if you don’t find the minimum version?? Sorry I’ve not looked at this code in over 2 years so will be a little rusty and I don’t have an environment setup that can test it just now I’m afraid. From: Sergiy Korzh Sent: 19 May 2017 15:47 To: processedbeets/ASP.NET-MVC-Scaffolding Cc: Subscribed Subject: Re: [processedbeets/ASP.NET-MVC-Scaffolding] Set-DefaultScaffolder :Operation unavailable (#5) An update. I guess we found that "consistent pattern" (or at least I hope so). It happened that for the projects on which our package's installation failed we had old T4Scaffolding package folder in the \packages sub-folder. After complete cleaning our package started installing without errors. That "complete cleaning" includes: 1. Uninstalling our package 2. Removing all T4Scaffolding lines from package.config file (both for old and new ones) 3. Removing all T4Scaffolding folders from .\packages folder So the question now: is there any to prevent errors when one of old packages is still installed in some project? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[processedbeets]

@cigano Has checked in updates to this repo which some of the more recent issues. Can I ask you to check if this is still an issue for you? Thanks