Difference between revisions of "User:Minooz/CanTire/Doc"
< User:Minooz | CanTire
(Created page with '== Development Steps == === Test on VM === * 1- Create the site * 2- Deploy the existing Sharepoint solution to the new site. * 3- 'Get' the project from the PVCS * 4- Do the cha…') |
(→Test on VM) |
||
Line 5: | Line 5: | ||
* 3- 'Get' the project from the PVCS | * 3- 'Get' the project from the PVCS | ||
* 4- Do the changes, build | * 4- Do the changes, build | ||
− | * 5- Copy the new .aspx page (if there is any change in this page) to the existing .aspx page in | + | * 5- Copy the new .aspx page (if there is any change in this page) to the existing .aspx page of the solution package in Sharepoint -> e.g. C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\CanTire.ContinuingEducation |
+ | * 6- Drag and drop the created .dll file from the /bin to the GAC -> (C:\Windows\Assembly) | ||
+ | * 7- Restart IIS from local admin account | ||
+ | * 8- In order to Debug, click on Debug -> Attach to process -> w3wp.exe -> Run the application on IE -> the breakpoints will be hi | ||
+ | * 9- After making sure the result is successful, Change the Solution Package (wsp): | ||
+ | : Note that not all of these steps might be necessary, it depends on the case and errors. | ||
+ | : 1. Deactive the feature | ||
+ | Stsadm.exe -o deactivatefeature -filename “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ViewFormPagesLockDown\feature.xml” -ur http://servername/ | ||
+ | : 2.Uninstall the feature | ||
+ | stsadm -o uninstallfeature -filename | ||
+ | : 3.Retract Solution | ||
+ | stsadm -o retractsolution | ||
+ | : 4. Add the solution | ||
+ | stsadm -o addsolution -filename {WSPFILENAME} | ||
+ | : 5. Deploy the solution | ||
+ | stsadm -o deploysolution -name {WSPFILENAME} -url {SITEURL} | ||
+ | : 6. Install the feature | ||
+ | stsadm -o installfeature -filename {FeatureFolder}\feature.xml | ||
+ | : 7. Activate the feature | ||
+ | stsadm -o activatefeature -id {FEATUREID} -url {SITEURL} -force |
Revision as of 10:05, 12 January 2012
Development Steps
Test on VM
- 1- Create the site
- 2- Deploy the existing Sharepoint solution to the new site.
- 3- 'Get' the project from the PVCS
- 4- Do the changes, build
- 5- Copy the new .aspx page (if there is any change in this page) to the existing .aspx page of the solution package in Sharepoint -> e.g. C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\CanTire.ContinuingEducation
- 6- Drag and drop the created .dll file from the /bin to the GAC -> (C:\Windows\Assembly)
- 7- Restart IIS from local admin account
- 8- In order to Debug, click on Debug -> Attach to process -> w3wp.exe -> Run the application on IE -> the breakpoints will be hi
- 9- After making sure the result is successful, Change the Solution Package (wsp):
- Note that not all of these steps might be necessary, it depends on the case and errors.
- 1. Deactive the feature
Stsadm.exe -o deactivatefeature -filename “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ViewFormPagesLockDown\feature.xml” -ur http://servername/
- 2.Uninstall the feature
stsadm -o uninstallfeature -filename
- 3.Retract Solution
stsadm -o retractsolution
- 4. Add the solution
stsadm -o addsolution -filename {WSPFILENAME}
- 5. Deploy the solution
stsadm -o deploysolution -name {WSPFILENAME} -url {SITEURL}
- 6. Install the feature
stsadm -o installfeature -filename {FeatureFolder}\feature.xml
- 7. Activate the feature
stsadm -o activatefeature -id {FEATUREID} -url {SITEURL} -force