A very Good topic explaining how to create site column and Content type and CustomPageLayout for sharepoint publishing Site.. can be located Here
Posts Tagged ‘Deployment’
Abdel-Rahman Awad
Mar 6
|09:37
If You want to make an application that mange An IIS Virtual paths or application a very Good Reference will be at that link Mange IIS
Abdel-Rahman Awad
Mar 6
|09:24
If You want to deploy your dll directly to the windows assembly
when ever you build you visual studio project
use those build events
Pre Build Events :
"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /u $(TargetName),Version=1.0.0.0,Culture=neutral,PublicKeyToken=7f94b68bc5abf6e5
Post Events
copy $(TargetPath) $(ProjectDir)gac\
"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /i "$(TargetPath)"
iisreset
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
Feb 7
|09:00
Configuring Web application to have Two zones windows and forms Authentication
Create the extranet site.
..Application Management -> Create or Extend Web Application > Extend
i. Set the Description
ii. Set the Port [80]
iii. Set the Host Header to [ISSExtra]
iv. Pick NTLM as the Authentication Provider (we’ll change this later)
v. Specify Anonymous Access to No (and this!)
vi. Set the Load Balanced URL Zone to [ISSExtra]
vii. Set the zone to extranet
b. Go back to Application Management and choose Authentication providers
c. Click on the Windows authentication provider link and
ii. Change the authentication to Forms
iii. Add the following as the membership provider: ISSMembershipProvider
iv. Add the following as the role provider: ISSRoleProvider
v. Save
vi. Note: Disabling client integration will remove features which launch client applications. Some authentication mechanisms (such as Forms) don’t work well with client applications. In this configuration, users will have to work on documents locally and upload their changes.
Add the host headers to DNS / hosts file!
a. For DNS (if you have access) add resolvers for ISSExtra. It should resolve to the IP address of your MOSS 2007 server.
b. If you don’t have access to the DNS server edit your hosts file to resolve the addresses.
i. Open the hosts file in notepad, this exists in the [C:\Windows\System32\drivers\etc] directory, assuming Windows is your OS directory.
ii. Make the changes to reflect the following
[MOSS Server IP Address] ISSExtra
Changes in the web config
For forms Authentication using database
i. Create sql database
ii. Run the following programme and choose the targeted database and run through the wizard. <WindowsDirectory>\Microsoft.NET\Framework\<version>\aspnet_regsql.exe
iii. In the web.config of the central administration
Add the following tags with your configuration
After </SharePoint> tag.
<connectionStrings>
<add name="MembershipDatabaseISS" connectionString="SERVER=localhost;DATABASE=ISSBasic; TRUSTED_CONNECTION=true;"/>
</connectionStrings>
Inside <system.web> tag
<membership>
<providers>
<add name="ISSMembershipProvider "
type="System.Web.Security.SqlMembershipProvider,System.Web, Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="MembershipDatabaseISS" enablePasswordRetrieval="false"
enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/"
requiresUniqueEmail="false" passwordFormat="Hashed"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10"
passwordStrengthRegularExpression=""/>
</providers>
</membership>
<roleManager>
<providers>
<add name="ISSRoleProvider " connectionStringName="MembershipDatabaseISS"
applicationName="/" type="System.Web.Security.SqlRoleProvider,
System.Web,Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"/>
</providers>
</roleManager>
iv. On both the intranet and the extra net application web config add the following
After </SharePoint> tag.
<connectionStrings>
<add name="MembershipDatabaseISS" connectionString="SERVER=localhost;DATABASE=ISSBasic; TRUSTED_CONNECTION=true;" />
</connectionStrings>
Inside <system.web> tag
<membership defaultProvider="ISSMembershipProvider">
<providers>
<add name="ISSMembershipProvider"
type="System.Web.Security.SqlMembershipProvider,System.Web, Version=2.0.0.0,
Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="MembershipDatabaseISS" enablePasswordRetrieval="false"
enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/"
requiresUniqueEmail="false" passwordFormat="Hashed"
maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7"
minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10"
passwordStrengthRegularExpression="" />
</providers>
</membership>
<roleManager enabled="true" defaultProvider="ISSRoleProvider">
<providers>
<add name="ISSRoleProvider" connectionStringName="MembershipDatabaseISS"
applicationName="/" type="System.Web.Security.SqlRoleProvider,
System.Web,Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
/>
</providers>
</roleManager>
For forms Authentication using AD
Same as forms Authentication using database section but with modifying
The connection string to
<add name="MembershipDatabaseISS" connectionString="LDAP://testdomain1.test.com/CN=Users,DC=testdomain1,DC=test,DC=com" />
2. Add the attribute for both the <add name="ISSMembershipProvider "…
And <add name="ISSRoleProvider "…
connectionUsername="testdomain2\administrator"
connectionPassword="password"
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
|18:44
If you are using the STSADM command to make any operation on WSP File … You don’t need to copy the Stsadm.exe to the same folder of the WSP file You can make the following steps and then use the stsadm command from any path you want on your PC.
in the last step add the path of the folder containing the stsadm.exe which is system Drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\
Now you can use stsadm.exe from any path in your local PC.
for more information Visit this
