API Source customization

[zafu]

We had to purchase api source to implement full-text catalog for search and some other performance modifications for our client's large product catalog.

I was able to build CommerceBuilder.dll and the resulting release DLL is 1.48MB, but the original provided dll is 2.47MB.

The application seems to run fine in test environment, but is this going to be a problem on production? I feel a little uneasy that 1MB is unaccounted for from the DLL--it's like rebuilding a car engine and having a box of parts left over.

FYI:
1. The CommerceBuilder solution had a missing reference for CommerceBuilder.Configuration so I removed it and added it back after copying CommerceBuilder.Configuration.dll from CommerceBuilder.Web.UI solution into the lib folder.

2. The CommerceBuilder solution is still missing the AbleCommercePublicKey.snk, but it doesn't cause any build errors.

Thanks,
Zolt

[mazhar]

I was able to build CommerceBuilder.dll and the resulting release DLL is 1.48MB, but the original provided dll is 2.47MB.

The application seems to run fine in test environment, but is this going to be a problem on production? I feel a little uneasy that 1MB is unaccounted for from the DLL--it's like rebuilding a car engine and having a box of parts left over.

Its OK, the size difference is due to obfuscation.

[Jusedawg]

WTF - Stupid obfuscation adds a megabyte of code! Jeez

That is a lot of extra crap code lol.