R5 source build problem

For general questions and discussions specific to the AbleCommerce GOLD ASP.Net shopping cart software.
Post Reply
arawis
Ensign (ENS)
Ensign (ENS)
Posts: 13
Joined: Tue Nov 20, 2012 8:05 am

R5 source build problem

Post by arawis » Thu Jun 27, 2013 7:37 am

hi all, has anyone tried building the CommerceBuilder.sln from the AbleCommerceGold-GoldR5-b5731-SRC files?
I can't get it to build, errors on the new CommerceBuilder.WebApi project included in the solution.
looks like a reference problem but I can't see it.
anyone?

i'm using vs2010 and not making any changes to the files or the configuration of the solution, using exactly as downloaded.
I've also tried adding my new R5 website project to the solution and setting it as the startup project but same errors(this all worked fine with R4 src files)

thanks,
Andrew.

arawis
Ensign (ENS)
Ensign (ENS)
Posts: 13
Joined: Tue Nov 20, 2012 8:05 am

Re: R5 source build problem

Post by arawis » Thu Jun 27, 2013 8:17 am

found error.
missing ref to system.web.routing
apologies if I troubled anyone.

User avatar
jmestep
AbleCommerce Angel
Posts: 8164
Joined: Sun Feb 29, 2004 8:04 pm
Location: Dayton, OH
Contact:

Re: R5 source build problem

Post by jmestep » Fri Jun 28, 2013 3:51 am

I had a compile error and reported to Able this week. I never change the source code, just use it as a reference so I don't really need to compile it but I always like to check.
Judy Estep
Web Developer
jestep@web2market.com
http://www.web2market.com
708-653-3100 x209
New search report plugin for business intelligence:
http://www.web2market.com/Search-Report ... -P154.aspx

User avatar
ForumsAdmin
AbleCommerce Moderator
AbleCommerce Moderator
Posts: 399
Joined: Wed Mar 13, 2013 7:19 am

Re: R5 source build problem

Post by ForumsAdmin » Fri Jun 28, 2013 10:46 am

The compile error reported here was reproduced. We have fixed it the same way as mentioned by arawis. However we were not able to reproduce the compilation error reported separately by Judy. We have concluded that it may have to do with .NET version/configuration on the particular system.

Post Reply