Cannot bind source type USN.USNModels.USNBaseViewModel to model type USN.USNModels.USNBaseViewModel.
Umbraco Version: 7.14.0
Database: SQL Server 2017
Package Installed: USN Refresh Starter Kit 5.1
Created a new SurfaceController, APIController, Partial View and Dictionary values to implement a custom login logic. Created a package by selecting all the files and dictionary values.
While trying to install the package in the test website (Different site and DB), the installation gets stuck at restarting and the site goes down. Error in the log file is
Cannot bind source type USN.USNModels.USNBaseViewModel to model type
USN.USNModels.USNBaseViewModel.
After a bit of searching around, got around it by adding a space in USNBaseViewModel.cs to force it to recompile. The logged back into Umbraco and realized that the Dictionary values were'nt created. So uninstalled the package and this time got another error
Exception message: The template with Id 1051 does not exist, the page
cannot render
Finally has to restore the Website and DB from backup to get it to working.
What could be the reason behind this behaviour and not able to reproduce this in local IIS is the most annoying part.
Cannot bind source type USN.USNModels.USNBaseViewModel to model type USN.USNModels.USNBaseViewModel.
Umbraco Version: 7.14.0
Database: SQL Server 2017
Package Installed: USN Refresh Starter Kit 5.1
Created a new SurfaceController, APIController, Partial View and Dictionary values to implement a custom login logic. Created a package by selecting all the files and dictionary values.
While trying to install the package in the test website (Different site and DB), the installation gets stuck at restarting and the site goes down. Error in the log file is
After a bit of searching around, got around it by adding a space in USNBaseViewModel.cs to force it to recompile. The logged back into Umbraco and realized that the Dictionary values were'nt created. So uninstalled the package and this time got another error
Finally has to restore the Website and DB from backup to get it to working.
What could be the reason behind this behaviour and not able to reproduce this in local IIS is the most annoying part.
Thanks in advance.
is working on a reply...