Creating Site using CMS, VS.NET, SQLServer2000, and [MCMS tools:Site Manager, Server Configuration Application and Database Configuration Application]

1. Create SQL Server database with name MCMSTest.
2. Add users (MCMS Admin and MCMS Sys Account) to database and give them rights of db_ddladmin, db_datareader and db_datawriter.
3. Goto "Database Configuration Application" tool of MCMS. Select MCMSTest database and copy MCMS schema through wizard (done automatically on "Next clicks").
4. Goto "Server Configuration Application"
in General tab, Click Configure... and then set "Map Channel Names to Host Header Names:" to Yes
in Access tab, click Configure... and select available domains except "workgroup".
in Security tab, click Configure... and set "Allow Guests On Site:" to Yes and add your local user account, for example, TIDREES\IUSR_TIDREES
Click "Close Application" button
5. Open VS.NET and create MCMS Web Project (in CMS Projects)
6. Give your application name as http://localhost:82/site as application name if your "Public site" is running on port 82.
7. Add default.aspx file in your project.
8. Goto MCMS Template Explorer and add new Gallary "News" and add new Template "NewsTemplate".
9. Goto properties of "NewsTemplate" and mention "TemplateFile" property as "/site/default.aspx"
10. In PlaceholderDefinition click "..." and add HtmlPlaceholderDefinition and set its Name property to "NewsHeading", then add another HtmlPlaceholderDefinition and set its Name Property to "NewsBody". Click Ok
11. Drag "DefaultConsole.aspx" to default.aspx.
12. In Toolbox, goto CMS tab and add two HtmlPlaceholderControl and set "PlaceholderToBind" property of one to NewsHeading and other to NewsBody.
13. Compile Project(don't give start page).

14. Open "Site Manager" tool of MCMS, login as your account (anyone that is added in MCMSTest database users).
15. In Template Gallery, templates made in VS.NET are shown (its because, VS.NET creates templates in MCMSTest db that is now accessed by Site Manager).
16. Goto Channels and add "New Channel". In "Web Authoring" select Template Gallery path as /Templates/News (that is what we created in VS.NET). Click OK
17. In "User Roles" select "Subscribers" and add "New Rights Group". Rename the right group to Subscribers. Goto its properties and in "Group Members" tab, add your user. In Group Rights tab, click on all red croses and make them green ticks. OK, and close Site Manager.

18. Open Browser and enter path http://localhost:82/news/ (its if your "Public" site is running on 82 port).
19. Login to site (if it asks for) and then "Create New Page", and select "News" folder and select "NewsTemplate".
20. Enter data, Click "Save and Exit", Enter name as "main" and then Submit and Approve.
21. Enter in browser http://localhost:82/news/main

Bingo ! your page is open (rather your channel is accessed).

Comments

Post a Comment

Feel free to give constructive feedback or let me know if it was helpful.

Popular posts from this blog

Unable to delete Shared Services Provider in SharePoint (MOSS)

Sometimes The SSP you create in MOSS are not created properly. This can be result of interruption while SSP was being created or in result of bad migration from SPS03 or MCMS to MOSS. Symptoms: 1. In left nav of SharePoint Central Administration, the name of your new SSP will not render rather, it will show up as text. 2. If you try to delete that from the Central Admin, the Delete option is disabled. Resolution: You should delete the SSP using stsadm command line tool (NOTE: My SSP's name is "SSP" which is specified after "title" in command: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa dm -o deletessp -title "SSP" However, if you have any dependencies, you will have to delete them first or you will get following error when you try deleting it through command line tool: An object in the SharePoint administrative framework, "SharedResourceProvider Na me=SSP Parent=SPFarm Name=SharePoint_Config&quo
Read more

The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

Image
  While configuring the SharePoint 2010 for Forms Based Authentication, I encountered above error. To get the problem, I had to change “IncludeExceptionDetailInFaults” to true somewhere. But WHERE? Here is what solved my problem: Go to following path: 1. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken 2. Open Web.config there. 3. Add following in the “behaviors > serviceBehaviors > behavior” node. <serviceDebug includeExceptionDetailInFaults="true"/> Now try to login and see what error it gives, off to a next error
Read more

Cannot add a SimpleContent column to a table containing element columns or nested relations

Recently I ran into a problem while dealing with DataSets. I was adding a colum to an XSD through Visual Studio desinger and it kept failing with following error: Cannot add a SimpleContent column to a table containing element columns or nested relations. This is a known issue. However, the solution is not well known :) To be simple and streight forward, I tell you the solution which I tried and it worked, 1. Note down the column names, datatypes and relationships of the table. 2. Delete the table. 3. Add new table and add columns to it. 4. Redefine relationships. Best of luck.
Read more