We're already dogfooding 4.5 in a staging environment... (that means we've performed the upgrade on a copy of www.dotnetnuke.com).  That was done by simply copying the files/folders from the 4.5 upgrade package right over the top of the existing site --AND-- merging the web.config changes.  It was totally painless and fast.  The hardest part is ALWAYS merging the web.config changes, but there are only a few and I plan to provide some side-by-side change logs to help with that.

Scott Willhite, Co-Founder DNN

I've just followed the upgrade procedures - unzipped over exisitng folders and updated web.config and I get the following error.

[FileLoadException: Could not load file or assembly 'DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataPr' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]

   System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0

   System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +211

   System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +141

   System.Reflection.Assembly.Load(String assemblyString) +25

   System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +32

[ConfigurationErrorsException: Could not load file or assembly 'DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataPr' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]

   System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +596

   System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +3487321

   System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +46

   System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +177

   System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +180

   System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +347

   System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125

   System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +378

[HttpException (0x80004005): Could not load file or assembly 'DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataPr' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]

   System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +57

   System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +612

   System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +456

[HttpException (0x80004005): Could not load file or assembly 'DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataPr' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]

   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3435023

   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88

Help...

Had a family member try to "help" with an upgrade while I was out of the room...uploaded Upgrade package for 4.4.1 onto site running 4.3.7 but didn't rename the release.config file to web.config before going to the live site and kicking off the upgrade.

Upgrade screen reported that the upgrade was successful, but when trying to access the portal, just get a screen saying:  An error has occurred. An error has occurred.

Tried rerunning install after updating web.config, but don't get any activity, just a browser "done" message.

Any thouoghts?