Home → Problems →

Upgrade to 0.4.6 problems

• Edit

nick.ryhajlo

11 Nov, 2013 08:02 PM

I was running 0.3.10 and I upgraded to 0.4.6 today by following the upgrade instructions. I extracted .zip file and copied all the files but the connectionString.config over, and now when I go to the root of the repository, I just get a blank page. When I go to http://mysite.tld/dashboard like I used to, I get a 404 not found error. What did I do wrong/what can I do to get it back? It seems like it will probably be a simple fix.

1. 1 Posted by nick.ryhajlo on 11 Nov, 2013 08:08 PM

   

   I should probably mention that I am running windows 8 with IIS version 8.0.9200.16384 Express. SQL Server Express 2012 version 11

   • Edit

2. 2 Posted by Andrey Bolibruk... on 12 Nov, 2013 01:38 AM

   

   I've got the same problem as Nick.
   Digging into logs turned up the following bits:

   05:06:26.2749 -  Info -            - octalforty.Structural.Framework.Web.MvcApplication - starting application
   05:06:26.3023 -  Info -            - octalforty.Structural.Framework.Web.MvcApplication - initializing service provider factory
   05:06:26.3023 -  Info -            - octalforty.Structural.Framework.Web.MvcApplication - initialized service provider factory
   05:06:26.3023 -  Info -            - octalforty.Structural.Framework.Web.MvcApplication - initializing middleware pipeline
   05:06:26.3169 -  Info -            - octalforty.Structural.Framework.Web.MvcApplication - initialized middleware pipeline
   05:06:26.3169 -  Info -            - octalforty.Structural.Framework.Web.MvcApplication - initializing service provider
   05:06:26.3169 -  Info -            - octalforty.Structural.ComponentModel.ServiceProviderFactory - started building container
   05:06:30.7886 - Error -            - octalforty.Structural.ComponentModel.ServiceProviderFactory - could not build container: System.TypeLoadException: Could not load type 'HgLab.Areas.Dashboard.Models.Setup.ErrorModel' from assembly 'HgLab, Version=0.4.6.0, Culture=neutral, PublicKeyToken=null'.
      at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
   

   If the full log would be helpful, I'll be happy to provide it.

   • Edit

3. Support Staff 3 Posted by Anton Gogolev on 12 Nov, 2013 04:50 AM

   

   Nick,

   What you need to do is first to _delete_ all files (sans connectionStrings.config), and only then copy new files over. This is an unfortunate consequence of how ASP.NET does compilation.

   There's an MSI installer in the works which makes installs and upgrades much easier.

   On 12.11.2013, at 0:02, "Nick Ryhajlo" <[email blocked]> wrote:

   • Edit

4. Support Staff 4 Posted by Anton Gogolev on 12 Nov, 2013 06:31 AM

   

   Andrey,

   Same applies to you as well: remove all old files and copy newer versions.

   • Edit

5. 5 Posted by Andrey Bolibruk... on 12 Nov, 2013 10:58 AM

   

   I guess I took "Upgrading instructions" too literally!

   Thanks Anton.

   • Edit

6. 6 Posted by nick.ryhajlo on 12 Nov, 2013 03:43 PM

   

   That fixed the problem. Thank you very much

   • Edit

7. nick.ryhajlo closed this discussion on 12 Nov, 2013 03:43 PM.

8. Anton Gogolev re-opened this discussion on 12 Nov, 2013 03:49 PM

9. Support Staff 7 Posted by Anton Gogolev on 12 Nov, 2013 03:49 PM

   

   Glad I could help!

   On 12.11.2013, at 19:43, "nick.ryhajlo" <[email blocked]> wrote:

   • Edit

10. Anton Gogolev closed this discussion on 13 Nov, 2013 10:16 AM.