BV Commerce Forum
»
BV Commerce Support
»
General Support
»
Please Help - Just purchased BVCommerce5, can't get the files to compile
Rank: Member
Joined: 10/7/2008(UTC)
Posts: 17
|
<SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana; mso-bidi-font-family: 'Times New Roman'">I recently purchased BVCommerce5.<SPAN style="mso-spacerun: yes"> I need to customize the code a little.<SPAN style="mso-spacerun: yes"> I followed the instructions in http://www.bvsoftware.com/BVCommerce5Manual/How%20To's/VisualStudioSetup.aspx . However, when I try to build with VS2008, set to Net 2.0, I get numerous build errors and I haven’t changed any of the code yet.<SPAN style="mso-spacerun: yes"> I think the developer pack that I downloaded must be missing files.<SPAN style="mso-spacerun: yes"> The build errors refer to things like such as anthem-2005.csproj.<SPAN style="mso-spacerun: yes"> I can’t find that file in the developer pack that I downloaded.<SPAN style="mso-spacerun: yes"> I’m on version 5.3.2 and downloaded that same developer pack. (Those are the only files that I can find to download.)<SPAN style="mso-spacerun: yes"> If anyone knows how to get the additional files or what I might be doing wrong, I’d greatly appreciate the help.<SPAN style="mso-spacerun: yes"> I’m desperate to get this implemented and I haven’t heard back from BVSoftware support. <SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana; mso-bidi-font-family: 'Times New Roman'"> <SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana; mso-bidi-font-family: 'Times New Roman'">Thanks! <SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Verdana; mso-bidi-font-family: 'Times New Roman'">Joyce<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>
|
|
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC)
Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
Anthem is an open source project available from SourceForge. But if you are not planning on changing any Anthem code, it would be easier to remove the reference to the Anthem project and then add a reference to Anthem.dll.
The same advice applies to the other referenced projects. If you don't plan on changing them, then remove the reference to the project and replace it with a reference to the corresponding dll. |
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.