I have an Umbraco 7.10.4 site that has worked well for a long time. Now I was curious to see how hard it would be to upgrade it to 8.x so I read all upgrade instructions. First I realized I should upgrade to a later 7.x so i tried to upgrade the UmbracoCms nuget package. Unfortunately this went for a straight upgrade to latest 8.x version which I realized was a bit too bold. So I interrupted and did a specified upgrade to 7.15. It failed to start. According to the instructions I needed at least 7.14.6 to be able to upgrade to 8.x so I tried with that version but it also failed.
Then I cleaned my git repository and went back to previous version of the site, but it still fails to launch. This surprises me. Are there some hidden version of other libs in locations that I am not aware of? That makes me a bit uneasy.
The rather lenghty error message says it fails to load Umbraco.Examine Version 8.0.0.0. Does that actually mean I have Umbraco 8 versions of some libs loaded in my 7.x site? How can that be? If so, how do I get rid of them?
Could not load all types from "Umbraco.Examine, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null" due to LoaderExceptions, skipping:
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.IO.FileLoadException: Could not load file or assembly 'Lucene.Net, Version=3.0.3.0, Culture=neutral, PublicKeyToken=85089178b9ac3181' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
. System.TypeLoadException on Examine.LuceneEngine.Providers.LuceneIndex: Could not load type 'Examine.LuceneEngine.Providers.LuceneIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.LuceneEngine.Providers.LuceneIndex: Could not load type 'Examine.LuceneEngine.Providers.LuceneIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.FieldDefinitionCollection: Could not load type 'Examine.FieldDefinitionCollection' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.LuceneEngine.Providers.LuceneIndex: Could not load type 'Examine.LuceneEngine.Providers.LuceneIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.ValueSet: Could not load type 'Examine.ValueSet' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.ValueSet: Could not load type 'Examine.ValueSet' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.ValueSet: Could not load type 'Examine.ValueSet' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
. System.TypeLoadException on Examine.FieldDefinition: Could not load type 'Examine.FieldDefinition' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
Now i erased the complete folder and tried again. This time I got a strange error saying: "CS1617 Invalid option '7.3' for /langversion; must be ISO-1, ISO-2, Default, Latest or a valid version in range 1 to 7.1". Apparently a mismatch in the Microsoft.Net.Compilers version. But how did that turn up? I removed a warning in the csproj file causing this and then it all worked again. But I really HATE when fully working projects suddenly don't work when launching them again after some months of passivity. It gives me a bad feeling I can't trust anything anymore. Umbraco keeps giving me this feeling over and over again. I just never feel I can trust it.
I feel the same way. The upgrade process in Umbraco is horrible. Sometimes it works and others, will have you spending hours trying to determine the cause. We have experienced issues after we have successfully upgraded a few times from back to back versions and then hit a version that breaks the site without any really reason.
After failed upgrade my site fails to start
I have an Umbraco 7.10.4 site that has worked well for a long time. Now I was curious to see how hard it would be to upgrade it to 8.x so I read all upgrade instructions. First I realized I should upgrade to a later 7.x so i tried to upgrade the UmbracoCms nuget package. Unfortunately this went for a straight upgrade to latest 8.x version which I realized was a bit too bold. So I interrupted and did a specified upgrade to 7.15. It failed to start. According to the instructions I needed at least 7.14.6 to be able to upgrade to 8.x so I tried with that version but it also failed. Then I cleaned my git repository and went back to previous version of the site, but it still fails to launch. This surprises me. Are there some hidden version of other libs in locations that I am not aware of? That makes me a bit uneasy. The rather lenghty error message says it fails to load Umbraco.Examine Version 8.0.0.0. Does that actually mean I have Umbraco 8 versions of some libs loaded in my 7.x site? How can that be? If so, how do I get rid of them?
Could not load all types from "Umbraco.Examine, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null" due to LoaderExceptions, skipping: . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IIndex: Could not load type 'Examine.IIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.IO.FileLoadException: Could not load file or assembly 'Lucene.Net, Version=3.0.3.0, Culture=neutral, PublicKeyToken=85089178b9ac3181' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) . System.TypeLoadException on Examine.LuceneEngine.Providers.LuceneIndex: Could not load type 'Examine.LuceneEngine.Providers.LuceneIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.LuceneEngine.Providers.LuceneIndex: Could not load type 'Examine.LuceneEngine.Providers.LuceneIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.FieldDefinitionCollection: Could not load type 'Examine.FieldDefinitionCollection' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.LuceneEngine.Providers.LuceneIndex: Could not load type 'Examine.LuceneEngine.Providers.LuceneIndex' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.IValueSetValidator: Could not load type 'Examine.IValueSetValidator' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.ValueSet: Could not load type 'Examine.ValueSet' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.ValueSet: Could not load type 'Examine.ValueSet' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.ValueSet: Could not load type 'Examine.ValueSet' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'. . System.TypeLoadException on Examine.FieldDefinition: Could not load type 'Examine.FieldDefinition' from assembly 'Examine, Version=0.1.89.0, Culture=neutral, PublicKeyToken=null'.
Now i erased the complete folder and tried again. This time I got a strange error saying: "CS1617 Invalid option '7.3' for /langversion; must be ISO-1, ISO-2, Default, Latest or a valid version in range 1 to 7.1". Apparently a mismatch in the Microsoft.Net.Compilers version. But how did that turn up? I removed a warning in the csproj file causing this and then it all worked again. But I really HATE when fully working projects suddenly don't work when launching them again after some months of passivity. It gives me a bad feeling I can't trust anything anymore. Umbraco keeps giving me this feeling over and over again. I just never feel I can trust it.
I feel the same way. The upgrade process in Umbraco is horrible. Sometimes it works and others, will have you spending hours trying to determine the cause. We have experienced issues after we have successfully upgraded a few times from back to back versions and then hit a version that breaks the site without any really reason.
is working on a reply...