Page 1 of 1

Compile errors when Publishing Website to server

Posted: Thu Mar 05, 2009 12:20 am
by joebeazelman
I am using the latest version of AC7 7.0.2. I can compile the application fine and it will run, however, when I try to use Publish Website under the build menu, I get the following compile error:

Error 1 'System.Web.UI.UserControl' does not contain a definition for 'CategoryId' and no extension method 'CategoryId' accepting a first argument of type 'System.Web.UI.UserControl' could be found (are you missing a using directive or an assembly reference?) D:\test\AbleCommerce\Admin\Catalog\Browse.aspx.cs 520

The code it is complaining about is:


protected void BindBreadCrumbs()
{
this.CategoryBreadCrumbs.CategoryId = CurrentCategoryId;
}

If pertinent, here is more info on the build:
PLATFORM: ASP.NET
VERSION: 7.0.2
BUILD: unknown

AjaxControlToolkit: 1.0.10301.0
CommerceBuilder: 7.2.11602.0
CommerceBuilder.AbleCommerceTax: 7.2.11310.0
CommerceBuilder.AcTestProvider: 1.0.0.0
CommerceBuilder.AustraliaPost: 7.1.0.0
CommerceBuilder.AuthorizeNet: 7.0.9764.0
CommerceBuilder.CanadaPost: 7.0.0.0
CommerceBuilder.CCH: 7.0.0.0
CommerceBuilder.Configuration: 7.2.11602.0
CommerceBuilder.CyberSource: 7.0.9310.0
CommerceBuilder.Data: 7.2.11602.0
CommerceBuilder.DataClient.Api: 7.0.2.1
CommerceBuilder.DataClient.Csv: 7.0.34.0
CommerceBuilder.DHL: 7.2.11307.0
CommerceBuilder.DHLInternational: 7.2.11307.0
CommerceBuilder.ECB: 7.0.0.0
CommerceBuilder.FedEx: 7.0.9725.0
CommerceBuilder.FRBNY: 7.0.0.0
CommerceBuilder.GoogleCheckout: 7.0.10052.0
CommerceBuilder.InternetSecure: 7.0.9764.0
CommerceBuilder.LinkPoint: 7.0.9764.0
CommerceBuilder.Paradata: 7.0.9764.0
CommerceBuilder.PayFlowPro: 7.0.10061.0
CommerceBuilder.PayJunction: 7.2.11284.0
CommerceBuilder.PayPal: 7.2.10840.0
CommerceBuilder.Protx: 7.1.10124.0
CommerceBuilder.Services: 7.2.11602.0
CommerceBuilder.SkipJack: 7.0.9764.0
CommerceBuilder.UPS: 7.0.10041.0
CommerceBuilder.USPS: 7.0.9728.0
CommerceBuilder.Web: 7.2.11602.0
ComponentArt.Web.UI: 2008.2.1175.3
CyberSource.Base: 2.0.0.0
CyberSource.Clients: 5.0.2.0
CyberSource.Clients.XmlSerializers: 5.0.2.0
CyberSource.WSSecurity: 2.0.0.0
CybsWSSecurityIOP: 1.0.0.0
edtFTPnet: 1.2.4.0
FredCK.FCKeditorV2: 2.5.2912.21007
ICSharpCode.SharpZipLib: 0.85.5.452
itextsharp: 4.1.2.0
LinkPointTransaction: 1.0.1797.29766
log4net: 1.2.10.0
Microsoft.Practices.EnterpriseLibrary.Common: 2.0.0.0
Microsoft.Practices.EnterpriseLibrary.Data: 2.0.0.0
Microsoft.Practices.ObjectBuilder: 1.0.51205.0
Microsoft.Web.Preview: 1.2.61025.0
NVelocity: 7.2.0.0
PaygatewayNET: 3.0.0.0
PayPal.Web.Controls: 1.0.22.18680
paypal_base: 4.2.1.0
PFProCOMLib: 1.0.0.0
PFProdotNET: 0.0.0.0
Validators: 1.0.0.0
WebChart: 1.1.1.6
wwHoverPanel: 1.85.0.0

Re: Compile errors when Publishing Website to server

Posted: Fri Mar 06, 2009 9:17 am
by joebeazelman
I noticed that there wasn't a classname for CatalogBreadCrumb.aspx:

<%@ Control Language="C#" EnableViewState="false" >

So I changed it to this:

<%@ Control Language="C#" EnableViewState="false" ClassName="CatalogBreadCrumbs"%>


I am still have the same problem. Can anyone out there help??? Thanks in advance.

Re: Compile errors when Publishing Website to server

Posted: Fri Mar 06, 2009 9:40 am
by mazhar
Do you have made any customization?

Re: Compile errors when Publishing Website to server

Posted: Fri Mar 06, 2009 11:44 am
by joebeazelman
I haven't made any customizations to that part of the code, but I have made customizations. Again, the error only shows up when I perform a "Publish Web Site" under the build menu of VS2008. I don't get an error however, when I uncheck the "Allow this precompiled site to be updatable"

Re: Compile errors when Publishing Website to server

Posted: Fri Mar 06, 2009 12:12 pm
by jmestep
Why do you want to compile and publish it? Try just copying it up and see if that helps.

Re: Compile errors when Publishing Website to server

Posted: Fri Mar 06, 2009 12:22 pm
by joebeazelman
I can copy the files to the server as you mentioned, but it would be nice if the .cs files were compiled before hand. I've found there to be quite a long delay when I first hit the site. Sometimes it can take several seconds.