Hi,

You do not need to install your dnn instance inside C:\DotNetNuke_2 for production web site! This is a requirement only for the dev (source) version.

You'r right, this references are used for copying required files to the installation folders (WWStore_02.00.00_Install and WWStore_02.00.00_SkinObjects). Thus, when you have finish your modifications inside code, you just have to make a zip file from the installations folders for produce installation packages. In some cases (add/remove: controls, files, etc.), you must update the manifest file (DNN WWStore.dnn) too.

You can change all references if you have inspected deeply how the module is build. I give this instructions only for obtain a "working" version in minutes. But experienced Visual Studio developers can change anything they want inside the projects.

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.

Hi,

You are welcome.

When you say "you just have to make a zip file from the installations folders for produce installation packages", do you mean the "WWStore_02.00.00_Installation" folder?

Yes! 1 point ;-)

So, if i make changes (for example source, controls and database), i have to rebuild the solution and create the apporpriate sql data provider script file.

Yes! 2 points

After that, i have to overwrite the source (dll) and control files, add the new sql script file and modify the dnn file inside this installation folder and finally zip it. Have i understood correctly?

Biiiiiipppppp! You loose! NO POINT ;-) You don't have to overwrite dll and controls files inside WWStore_02.00.00_Install, this is done by post build procedures.

In your case, because you have change database structure, you need to:

• Increase the version number (02.00.09) of each projects (21 C# projects) inside the properties tab
• Create a new sqldataprovider file like 02.00.09.SqlDataProvider with your sql commands
• Correct the manisfest file (DNN WWStore.dnn) inside WWStore_02.00.00_Install folder:
  • Search for 02.00.07.sqldataprovider, then add this lines:
    •     <file>
              <name>02.00.09.sqldataprovider</name>
          </file>
• Create a new zip file (WWStore_02.00.09_Install.zip) with the content of the folder WWStore_02.00.00_Install
• Install this new PA to the production server

As a general rule:

• When you modify anything inside the projects, use a new version number!
• If you add or remove a file (sqlprovider, controls, graphics, etc.), YOU HAVE TO CORRECT the manifest file. Remember that post build procedure copy all dll and controls into the folder WWStore_02.00.00_Install. Look at the properties tab of each C# projects for understood what is done by the post build procedures.
• If you just modify some part of code, then rebuild the solution and recreate a zip file with the content of the folder WWStore_02.00.00_Install.

Also, does the skin package needs to be installed as a separated module on the DNN deployment portal and is it necesary to install it?

Yes, the skin package need to be installed as a separate module. This is because, you can't have two manifest files inside a PA.
No, it's not a mandatory part of the WWStore module. This is used for adding two skin objects [WWSTORELINKS] and [WWSTOREMICROCART]. The first one create a link to the cart (View Cart) or the store (View Store) tab with the corresponding icon. The second, create a very small cart with just the number of products and the total.

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.