A very nice break through showing all the new features inside Visual studio 2010 helping with the Agile methods and daily scrums … really amazing how it facilitates alot of staff ;- )
Enjoy
Posts Tagged ‘Visual Studio’
Abdel-Rahman Awad
May 20
|13:48
Abdel-Rahman Awad
Feb 7
|13:50
copy $(TargetPath) $(ProjectDir)gac\
"C:\ToolPath\WSPBuilder.exe" -solutionpath $(ProjectDir) -outputpath $(ProjectDir) -WSPName $(TargetName).wsp -buildwsp
cd $(ProjectDir)
"C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\STSADM.EXE"-o upgradesolution -filename $(TargetName).wsp -name $(TargetName).wsp -immediate -allowgacdeployment -allowCasPolicies
By adding this few lines to your projects build events..
you will do all these things in one step
you will build your project
will copy the out put to the gac of your project
will build new wsp solution
will update the wsp solution in the administration site.
Happy coding
Abdel-Rahman Awad
Oct 31
|12:00
Abdel-Rahman Awad
Oct 30
|20:22
This Trick Allan showed me…
You can add a menu tool to your visual studio to add/upgrade/delete your WSP solution If it located in the same folder for your VS Project
Open your Visual Studio Select Tools > External Tools then Click ADD
Tool 1 :"Add WSP" this tool Adds Your WSP solution to the Share Point Solutions List … How Ever It Adds it Without Deployment So you need to Open Administration site for share point and open Central Administration > Operations > Solution Management to deploy the project after using this tool
back to what we were saying
Too1:
Write the following
Title : Add WSP
Command : system Drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\STSADM.EXE
Arguments : -o addsolution -filename $(TargetName).wsp
Initial Directory : $(ProjectDir)
Check Use Out Put window Option
Tool2: UpGrade WSP (Only Works When Your Solution is Deployed Already on share Point Used Up Grade the WSP Solution)
Title : UpGrade WSP
Command :system Drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\STSADM.EXE
Arguments : -o upgradesolution -filename $(TargetName).wsp -name $(TargetName).wsp -immediate -allowgacdeployment
Initial Directory : $(ProjectDir)
Check Use Out Put window
Tool3:(Removes the WSP Solution From the share point Solutions how ever the solution must be retracted before using this tool, to retract your solution open Administration site for share point and open Central Administration > Operations > Solution Management )
Title : Remove WSP
Command : system Drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\STSADM.EXE
Arguments : -o deletesolution -name $(TargetName).wsp
Initial Directory : $(ProjectDir)
Check Use Out Put window
To Make any of These Tools Work You must First Select the Project in the Solution Explorer window In the VS before selecting the tool from the tools menu … Also the WSP solution must be in your project Directory.
To Generate the WSP solution from Your VS you can see the tool I mentioned in my Previous Post
I made tool for the WSPBuilder From my Previous Post to generate the Wsp in the project folder
Tool4:(generate Wsp file from VS project in the project`s folder)
Title : WSP Build
Command : WSPBuilder Tool Path\WSPBuilder.exe
Arguments :
Initial Directory : $(ProjectDir)
Check Use Out Put window
So you can develop your project use tool4 to generate the wsp solution use too1 to add it to the share point solutions ,deploy it from the administration site and if you made some modifications to the project you simply rebuild it and then use tool 4 and finally use tool 2.
Abdel-Rahman Awad
Oct 30
|19:16
There is a Tool That Automatically creates SharePoint Solutions files based on a folder structure. WSPBuilder will automatically traverse a "12" folder structure
and creates a SharePoint solution manifest.xml and the wsp file based on the files it finds.
Lets say that you have created a SharePoint feature and you want to create a SharePoint Solution
for this feature. Then you just need to create the following folder structure in you project directory:
"[MyProject]\12\Template\Features\MyCustomFeature\"
and put your feature files in the MyCustomFeature folder, that being your feature. Then run the WSPBuilder from the your project directory and it will automatically create the manifest.xml and pack it into a wsp file with the content of the "\12" folder.
To get the latest version of WSPBuilder Visit All Releases
For more Information About WSPBuilder and how to use it Visit the Orgional Topic
More Over you don’t have to paste the WSPBuilder.exe in your project directory … you can read my previous post and you will know the way to do that 
My Previous Post
Abdel-Rahman Awad
Oct 29
|15:49
While I was installing SP1 for VS 2005 on the new MOSS 2007 Virtual PC An Error Appeared To me that said
"Error 1718.File C:\Windows\Installer\7ceed.msp did not pass the digital signature check.
http://go.microsoft.com/fwlink/?linkid=73863"
After a some searches I knew the solution for the problem as this problem appears because the virtual pc doesn’t have enough memory for the temp files generated during the installation progress
Solution :
This workaround applies to Windows Server 2003 and to Windows XP.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To work around this problem, change the PolicyScope registry value to 1 before you try to install the package. To do this, follow these steps.
Note If the computer is joined to a domain, a domain policy update may override the registry changes that you make. We strongly recommend that you disconnect the computer from the domain before you follow these steps.
1.Click Start, click Run, type regedit, and then click OK.
2.In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers
Note Before you modify this key, we recommend that you back up this key. To do this, right-click CodeIdentifiers, and then click Export. Save the file to a location where you can find it on the computer.
3.Change the PolicyScope registry value. To do this, double-click PolicyScope, and then change the setting from 0 to 1.
4.Close Registry Editor.
5.Click Start, click Run, type cmd, and then click OK to open a Command Prompt window.
6.At the command prompt, type the following command, and then press ENTER:
net stop msiserver
This command stops the Windows Installer service if the service is currently running in the background. When the service has stopped, close the Command Prompt window, and then go to step 7.Note If you receive the following message at the command prompt, close the Command Prompt window, and then go to step 7: The Windows Installer service is not started
7.Install the package that you were trying to install when you received the error message that is mentioned in the "Symptoms" section.
8.After you install the package, repeat steps 1 and 2. Then, change the PolicyScope registry value back to 0.
9.If you disconnected the computer from a domain, re-join the domain, and then restart the computer.
Note If you did not disconnect the computer from a domain, you do not have to restart the computer.
If the previous steps do not resolve the issue, follow these steps:
1.Click Start, click Run, type control admintools, and then click OK.
2.Double-click Local Security Policy.
3.Click Software Restriction Policies.
Note If no software restrictions are listed, right-click Software Restriction Policies, and then click Create New Policy.
4.Under Object Type, double-click Enforcement.
5.Click All users except local administrators, and then click OK.
6.Restart the computer.
Important After you follow the previous steps, local administrators can install the .msi package or the .msp package. After the package is installed, reset the enforcement level by following the previous steps. In step 5, click All users instead of All users except local administrators.
Notes
•The workaround may not work in an Active Directory domain environment. In an Active Directory domain environment, a domain policy refresh operation will overwrite the local Software Restriction Policies.
•Adding more RAM to the computer will not resolve the problem.
For seeing the original topic please visit this
