More in this section

Forums / Bugs & Issues / Compilation/type already contains definition for 'C000' Error when upgrading from 4.0 to 4.2

Compilation/type already contains definition for 'C000' Error when upgrading from 4.0 to 4.2

19 posts, 0 answered
  1. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    04 Nov 2011
    Link to this post
    We are working on a Sitefinity upgrade from 4.0 to build version 4.2.1733.0

    Some of our pages are receiving the error below.  The control being mentioned is a custom control added to the page, but it works fine on other pages.  Also, if i save and republish the page, it works again, but we have literally a hundred such pages in production and don't want to have to re-publish them one by one, nor can we afford the downtime.


    Compilation Error

    Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. 

    Compiler Error Message: CS0102: The type 'ASP.sfpageservice_17a293cc_ec89_430b_a42e_0057e220e8d6_14_notheme_aspx' already contains a definition for 'C000'

    Source Error:

    Line 14: <p></p> <a class="AppointmentLink lp_action">Choose a date for your free in-home consultation</a></h3>" ID="C002"  runat="server">
    Line 15: <BrowseAndEditableInfo ControlDataId="ad91b69c-26a6-49c7-893e-8197d2d58ebc" PageId="3dd7562b-e49a-4afa-9d91-bf301f0f7cc6" ControlType="Telerik.Sitefinity.Modules.GenericContent.Web.UI.ContentBlock" /></sf:ContentBlock></asp:Content><asp:Content ContentPlaceHolderID="CalloutContent" runat="Server">
    Line 16: <sf:AppointmentCallout BottomLine="WHEN YOU MAKE AN APPOINTMENT ONLINE" TopLine="Save $200 On Your Purchase" ID="C000" PromoCode="PPC100"  runat="server">
    Line 17: </sf:AppointmentCallout></asp:Content><asp:Content ContentPlaceHolderID="ScriptContent" runat="Server">
    Line 18: </asp:Content>

    Source File: /SFPageService/17A293CC-EC89-430B-A42E-0057E220E8D6_14_NoTheme.aspx    Line: 16 



    c:\windows\system32\inetsrv> "C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe" /t:library /utf8output /R:"C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Routing\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Routing.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_uyuzfvi3.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\a9944cdf\10718324_1b9bcc01\Telerik.Sitefinity.Analytics.Server.GoogleAnalyticsPlugin.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\b96f117b\464e4525_1b9bcc01\Telerik.Sitefinity.Model.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.Activities.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\ce71ce15\610e1e6a_1d9bcc01\Enilon.Luna.Business.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activities\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activities.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_xc1ff5mv.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\46e3b2a6\07999124_1b9bcc01\Telerik.Sitefinity.Resources.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Entity\v4.0_4.0.0.0__b77a5c561934e089\System.Web.Entity.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\815bcb54\f6f4071c_297dcc01\Microsoft.Practices.ServiceLocation.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\d0d07930\ab589924_1b9bcc01\Telerik.Sitefinity.Utilities.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\86678fdc\28dc161d_297dcc01\log4net.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\0201249c\7e77061c_297dcc01\DocumentFormat.OpenXml.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\adac55f0\5e2ea324_1b9bcc01\Microsoft.WindowsAzure.StorageClient.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\4200c845\21dd7825_1b9bcc01\Telerik.Sitefinity.Analytics.Server.Infrastructure.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\d44aff50\28194d1c_297dcc01\ActiveUp.Net.Dns.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\6228d757\7640d41c_297dcc01\ActiveUp.Net.Common.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\517c1ded\83397725_1b9bcc01\Telerik.Web.UI.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\675a7236\fa4f8024_1b9bcc01\Microsoft.WindowsAzure.Diagnostics.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.WebPages.Deployment\v4.0_1.0.0.0__31bf3856ad364e35\System.Web.WebPages.Deployment.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\7bd17ad3\91dc1d1c_297dcc01\MySql.Data.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\607a045d\cc8d881c_297dcc01\ActiveUp.Net.Smtp.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.DynamicData\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.DynamicData.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\93cea442\d5d2501c_297dcc01\AjaxControlToolkit.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\5a490fff\605c071c_297dcc01\Facebook.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\100e88be\fb97dd24_1b9bcc01\Telerik.OpenAccess.Config.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Activation\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Activation.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\ad1cc52c\311c3d25_1b9bcc01\Telerik.Sitefinity.Analytics.Server.Core.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\da928234\4013a424_1b9bcc01\Microsoft.WindowsAzure.ServiceRuntime.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.WorkflowServices\v4.0_4.0.0.0__31bf3856ad364e35\System.WorkflowServices.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\98c51941\92804c1c_297dcc01\DirectShowLib-2005.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\b2d510b7\9034ee55_269bcc01\Enilon.Luna.Web.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\f9b08e15\dbfab924_1b9bcc01\Telerik.Sitefinity.Analytics.Server.DependencyResolution.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\63022313\8198b724_1b9bcc01\Telerik.ReportViewer.WebForms.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\7bf6b3bb\9940811c_297dcc01\Twitterizer2.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\ac9dc272\36f5871c_297dcc01\Facebook.Web.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.ApplicationServices.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\8314e752\45ad8524_1b9bcc01\Telerik.Sitefinity.MigrationContracts.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Web\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_global.asax.4imk3yks.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\1ceb6279\38e1131d_297dcc01\Enilon.Internal.Web.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\5814c5ca\e49a171d_297dcc01\WilsonORMapper.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\f7135990\c8b43d25_1b9bcc01\Microsoft.Http.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\5ce81ee0\f659cd24_1b9bcc01\Telerik.Web.Design.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\2ace2f15\fe53c924_1b9bcc01\Telerik.OpenAccess.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\a4cb30eb\7417121d_297dcc01\HDAPI.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\f36496c1\4f373c25_1b9bcc01\Telerik.OpenAccess.35.Extensions.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\96abc73c\23d69a24_1b9bcc01\Telerik.Windows.RadUploadHandler.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\3fb30082\31fda124_1b9bcc01\Telerik.OpenAccess.Runtime.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\a48aa097\4473be24_1b9bcc01\Telerik.OpenAccess.Web.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\4d750ecb\a53c9324_1b9bcc01\Payflow_dotNET.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\1d25db27\e4331f1c_297dcc01\Newtonsoft.Json.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\4fb53979\dfb33625_1b9bcc01\Telerik.Sitefinity.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\d05c181f\9e6b5924_1b9bcc01\Telerik.Reporting.DLL" /R:"C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ComponentModel.DataAnnotations\v4.0_4.0.0.0__31bf3856ad364e35\System.ComponentModel.DataAnnotations.dll" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\64a4ff48\a159181d_297dcc01\LitJson.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\367bde30\28ce801c_297dcc01\System.Windows.DLL" /R:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\assembly\dl3\faf60366\8ad11c1c_297dcc01\Telerik.OpenAccess.Adonet2.DLL" /out:"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_17a293cc-ec89-430b-a42e-0057e220e8d6_14_notheme.aspx.d63928b6.lydaeri0.dll" /D:DEBUG /debug+ /optimize- /w:4 /nowarn:1659;1699;1701 /warnaserror-  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_17a293cc-ec89-430b-a42e-0057e220e8d6_14_notheme.aspx.d63928b6.lydaeri0.0.cs" "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_17a293cc-ec89-430b-a42e-0057e220e8d6_14_notheme.aspx.d63928b6.lydaeri0.1.cs"
    
    
    Microsoft (R) Visual C# 2010 Compiler version 4.0.30319.1
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    http://server/SFPageService/17A293CC-EC89-430B-A42E-0057E220E8D6_14_NoTheme.aspx(16,70): error CS0102: The type 'ASP.sfpageservice_17a293cc_ec89_430b_a42e_0057e220e8d6_14_notheme_aspx' already contains a definition for 'C000'
    http://server/SFPageService/17A293CC-EC89-430B-A42E-0057E220E8D6_14_NoTheme.aspx(6,89): (Location of symbol related to previous error)
    c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_17a293cc-ec89-430b-a42e-0057e220e8d6_14_notheme.aspx.d63928b6.lydaeri0.0.cs(555,68): error CS0111: Type 'ASP.sfpageservice_17a293cc_ec89_430b_a42e_0057e220e8d6_14_notheme_aspx' already defines a member called '__BuildControlC000' with the same parameter types
    c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\7039fa1f\73ba4d29\App_Web_17a293cc-ec89-430b-a42e-0057e220e8d6_14_notheme.aspx.d63928b6.lydaeri0.0.cs(267,87): (Location of symbol related to previous error)
    



  2. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    07 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    This is a known issue regarding the upgrade process from 4.0.

    You can check the following thread:

    http://www.sitefinity.com/devnet/forums/sitefinity-4-x/general-discussions/project-upgrade-from-4-0-to-4-1-errors.aspx

    This KB article can be also useful to you.

    Kind regards,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    09 Nov 2011
    Link to this post
    I am going to ask a very stupid, snotty question.

    Why do we always have to do stuff like this with sitefinity upgrades?  We have also had to run some other, undocumented "recompileUrls" script in order to make this work.  The edit pages also have all kind of javascript and css issues that make editing in the project impossible right now.  

    I cannot remember an upgrade that went fairly smoothly with sitefinity (which i've used since 2.5.)  With other CMS's, its overwrite this folder, run this db script, done.  

    Sorry, just a bit frustrated as this will mean unbillable hours we'll just have to eat for our client.  
  4. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    10 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    We are sorry for the caused inconvenience. However we are constantly improving the product and try to eliminate such issues. I should also note that in order for the upgrades to proceed as expected they must be conducted properly. For example if you are upgrading from 4.0 1098 to 4.2 SP1 1733 you should go through:

    4.0 -> 4.1 1339

    4.1 1339 - 4.2 1650

    4.2 1650 - 4.2 SP1/ 4.3

    All the best,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  5. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    11 Nov 2011
    Link to this post
    So should i start over and go from 4.0 to 4.1 and so on?  I thought the project manager could upgrade you several steps at once?

    I was able to run that script but now certain pages will not edit.  the content is "jumbled" with some of at the top and then the control editors and everything at the bottom.  None of the Edit buttons work nor can you drag and drop controls.

    For clarification, i should say the content was jumbled when i first upgraded from 4.0 to 4.2, not after i ran the above scripts.  I also tried applying 4.3 but its still jumbled.  
  6. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    11 Nov 2011
    Link to this post
    Hello Fregas Baratis,

    In order to properly upgrade your project it is highly recommended for you to follow the steps that were previously mentioned as there were many changes throughout the different versions of Sitefinity and jumping from 4.0 to 4.3 directly is not supported as it may corrupt your project database or files.

    Regards,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  7. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    11 Nov 2011
    Link to this post
    so i have upgraded from 4.0 to 4.1.  Some things are broken but at least the admin lets you edit pages.

    Here is my question.  I am doing this against a production copy of the database.  If i upgrade at each step against this copy of my database and then upgrade the code, when I go to production, will I have to upgrade the database each step, or will Sitefinity upgrade me automatically from 4.0 to 4.3 as long as my code is working?
  8. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    14 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    When you are upgrading your site, the upgrade scripts are doing all necessary changes to your files and database. So if you upgrade your production site ( locally I assume ) what you need to do is to deploy it back to your server, once the upgrade process has been finished.

    Best wishes,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  9. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    14 Nov 2011
    Link to this post
    So I'm not sure you answered my question.  I can't just overwrite the production database, because the client may have made changes in sitefinity.  I'll have to point my upgraded code to the production database and upgrade it that way.  My question is this, lets say I upgrade against a copy of production db working locally:

    I upgrade the files from 4.0 - 4.1 using my local db.
    then 4.1 - 4.2
    then 4.2 - 4.3

    Each step, using only my local database.  

    When I have all the files upgraded to 4.3, can I just copy the files out to production and sitefinity will upgrade my database from 4.0 to 4.3?  Or do I need to upgrade the production database at each step, from 4.0 to 4.1, 4.1 to 4.2 and so on?
  10. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    15 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    The best option is to upgrade your production website if you cannot do it locally and then replace the database and the files. Upgrading the files locally and then replacing them on the live server will directly upgrade the database and might mess up the configs as they are already upgraded.

    Therefore I can suggest you to create a backup copy of the website ( files and db ) before upgrading and follow the provided steps.

    Regards,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  11. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    15 Nov 2011
    Link to this post
    So you're saying:

    a) that i should ask the client to stay out of the production sitefinity, get a copy, and then upgrade that?  Can I do that even though I have upgraded the code already?

    and

    b) I can't get sitefinity to upgrade the database from 4.0 to 4.1.  I AM going  to have to do this step by step.  

  12. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    15 Nov 2011
    Link to this post
    So just upgrading from 4.0 to 4.1, just like you said, i'm getting the following error on a page that uses a nested master page:

    Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

    Exception Details: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace: 

    [ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index]
       System.Text.StringBuilder.Insert(Int32 index, String value, Int32 count) +4040015
       Telerik.Sitefinity.Abstractions.VirtualPath.SitefinityPageResolver.WriteAllHolders(CursorCollection placeHolders, StringBuilder output, String name) +198
       Telerik.Sitefinity.Abstractions.VirtualPath.SitefinityPageResolver.WriteAllHolders(CursorCollection placeHolders, StringBuilder output, String name) +159
       Telerik.Sitefinity.Abstractions.VirtualPath.SitefinityPageResolver.RenderPage(StringBuilder output, PageData pageData, RequestContext context, String virtualPath) +215
       Telerik.Sitefinity.Abstractions.VirtualPath.SitefinityPageResolver.Open(PathDefinition definition, String virtualPath) +215
       Telerik.Sitefinity.Abstractions.VirtualPath.PathDefinition.OpenFile(String virtualPath) +32
       Telerik.Sitefinity.Abstractions.VirtualPath.VirtualPathManager.OpenFile(String virtualPath) +42
       Telerik.Sitefinity.Abstractions.VirtualPath.SitefinityVirtualFile.Open() +22
       System.Web.Hosting.VirtualPathProvider.OpenFile(String virtualPath) +31
       System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) +133
       System.Web.UI.TemplateParser.ParseInternal() +86
       System.Web.UI.TemplateParser.Parse() +160
       System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() +110
       System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) +65
       System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() +218
       System.Web.Compilation.BuildProvidersCompiler.PerformBuild() +40
       System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) +8941618
       System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +320
       System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) +111
       System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) +125
       System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) +52
       Telerik.Sitefinity.Web.PageRouteHandler.GetHttpHandler(RequestContext requestContext) +621
       System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context) +8886120
       System.Web.Routing.UrlRoutingModule.OnApplicationPostResolveRequestCache(Object sender, EventArgs e) +86
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1

  13. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    16 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    It seems that the problem is coming from one of your controls on the templates and is related to the virtual path provider, probably to the template of the actual control.

    In 4.1 we introduced the Virtual Path provider which when used correctly should not give you troubles.

    Please check the following articles which can give you an idea how to fix your controls:

    http://www.sitefinity.com/blogs/slavoingilizov/posts/11-04-18/taking_advantage_of_the_virtual_path_provider_in_sitefinity_4_1.aspx


    http://www.sitefinity.com/devnet/forums/sitefinity-4-x/bugs-issues/error-parsing-the-template---data-doesn-t-appear-on-website.aspx

    Regards,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  14. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    17 Nov 2011
    Link to this post
    The first link you sent me gave me an error, a 404 page.  I did not see my error specifically in the second post.  I am not sure i understand what you mean about virtual path manager.  

    I did some more experimenting.  I edited this problem page and that works fine, but if i republish it still errors on the front end.  I looked for any controls on this page and I have no custom controls in it--only content controls.  I looked at the template its using and that did have a custom control in it, which i took out, but same error.  I made a new page with that same template and that page worked fine, even with the custom control on it.  Other pages in the site seem to work fine.  

    I also tried adding the VirtualTemplatePath property in my one custom control the way you had it in the second post but that did not seem to change anything.  How should I calculate the VirtualTemplatePath?  Is it just like a normal embedded resource using dot notation or do i have to prefix it with "~/" and the project name like you have?  Also, do i have to put it in a resources directory?
  15. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    21 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    I am sorry for the incorrect link. Here it is:

    http:/www.sitefinity.com/blogs/slavoingilizov/posts/11-04-18/taking_advantage_of_the_virtual_path_provider_in_sitefinity_4_1.aspx


    The article explains in details how to correctly work with path provider.

    Also if there was a problem in your sysytem with a content control on your page, the easiest way is to remove it and drop it again on a page.

    Best wishes,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  16. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    21 Nov 2011
    Link to this post
    If its just one page to drop and recreate the control, then thats fine.  But we can't do that for dozens or hundreds of pages we have in production.  We may not even know certain pages are broken until error reporting comes in.  That's not really acceptable.  You can't make change that could potentially break tons of pages on a production site, and then expect developers or content editors to manually fix them on one by one on a production server.  I'm making all these changes on my development copy, and I'm not really sure what's going to happen once i get the code fixed and attempt to push it all out to production.  The upgrade process isn't really safe or easily repeatable.  

    I will look at the path provider and see if that solves the problem.

    Craig
  17. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    21 Nov 2011
    Link to this post
    Ok, i tried deleting the control entirely.  And i still get the same error.  This is a different error from the two links you sent me to:

    Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index


    I have not tried messing with the Virtualpathprovider yet because I have no controls on the page or its template.  Also, the link you just sent me says that you need this when using embedded controls in a DLL.  This is not the case here.  My control is in a standard usercontrol and does not inherit from simpleview.  It does have a designer for editing the control's properties in sitefinity however.  Do i need to use the VirtualPathProvider stuff for that?  

    I'm going nowhere fast with this.  
  18. Victor Velev
    Victor Velev avatar
    1345 posts
    Registered:
    06 Jul 2015
    24 Nov 2011
    Link to this post
    Hi Fregas Baratis,

    Can you please open a support ticket and send us the project ( before any upgrades applied to it ) so we can inspect it locally and perform the upgrade process as the project may have been already corrupted judging by the errors you are getting.

    Best wishes,
    Victor Velev
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  19. fregas baratis
    fregas baratis avatar
    185 posts
    Registered:
    14 Nov 2002
    28 Nov 2011
    Link to this post
    okay, will do.  
19 posts, 0 answered