.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Help about making automated site solution

Posted By:      Posted Date: September 10, 2010    Points: 0   Category :ASP.Net
 Hello every one,   These days I started new ground in learning intellectual website for example I want to understand the number and name and type of tables and columns and make button and interface of website with all aspx and cs and classes and to cut long story short blank solution and sth like this but i do not know where I should start .I prefer to have suggestion of some good books whith functional example I searched in alot of website but I could not find anything ,now i am about losing my time and energy please help me? 

View Complete Post

More Related Resource Links

Office Space: Automated SharePoint Site Branding


Here's a custom branding solution for SharePoint sites that integrates Master Pages and CSS files at the level of the site collection.

Ted Pattison

MSDN Magazine July 2008

Video: Site Collection Solution Galleries in SharePoint 2010

This demonstration shows the solution gallery and solution management features of SharePoint 2010. (Length: 4:01)

SOLUTION: Renaming the Title list column globally across the site collection

So, you screwed up like I did, and modified the Title display name of the Item base content type and it has renamed ows_Title across every list in your site collection? Here's how you fix it: //WARNING //If you have come this far, be aware that this tool is a blunt axe. With it, you can cause //all sorts of mayhem and chaos in your site collection. So, to use this, you must be desperate. //or possibly dumb. Apparently, I'm just as dumb as you, because I did it. This is why I wrote //this stupid thing, so stupid people like us can go right on being stupid. //Your choice of weapon in this battle amuses me. Shall we begin? using System; using System.Collections.Generic; using System.Text; using Microsoft.SharePoint;   namespace RenameField {     class Program     {         static void Main(string[] args)         {             if (args.Length < 3)             {                 Console.WriteLine("Usage: RenameField <url-to-sitecollection> <internal-field-name> <new-fieldtitle>");               &n

Upgrade Solution using a .wsp file created from a site template

Hello, I'm creating a new site template that I will need to move from my development to production server. I have saved the template as a .wsp file and installed it on my staging server without any problems. However, I know once the site goes into production that changes will occur and I will need to upgrade the site template. I have tried to make changes to my development site and save a new site template, and then move to my staging server and upgrade the existing solution using the below PowerShell command, but I get an error that the GUIDS are different and the solution cannot be upgraded. Command: Update-SPUserSolution -Identity MyTemplate v1.wsp -Site http://webapplication/site  -ToSolution MyTemplate v2.wsp Error: Update-SPUserSolution : Given solution cannot be upgraded to the provided ToSolution because the solutions have different Guids. Does anyone know how I would upgrade the solution when using a site template as the bases for the solution? Thanks, wm5

How to migrate sharepoint site in 2007 with custom solution package and its content to sharepoint 20

Hi Experts, Recently, my organization is planning for SharePoint 2010 upgrade. We decide to go with Database content migration as it is less impact with down time due to hardware and software requirement (64 bit) in SharePoint 2010. We have a sub-site which contains a lot of customization such as master page, custom list, web parts and a lot of content. There is also a solution was built for that sub-site as well. However, as the time past by there quite a few update and manual creating from power users which concern to me that the solution package that we have does not up to date that can be use for SharePoint 2010 upgrade. I am planning to re-package the solution for the upgrade with all the changes users made for SharePoint 2010. But the question is how do I migrate the content of existing site when we upgrade to 2010? It is also possible that they want to change the sturction of the site when migrate eg: make this new upgrade site as top site collection instead of sub-site. Another concern is what happen after I finish making re-package the solution but during the re-package period users might make more change to the existing site? I would greatly appreciate for any ideas, suggestions as well as best methodology I should take.   Thanks praneth

Receiving error when saving site as template: [InvalidOperationException: Error generating solution

I am getting the following error when saving a site as a template (just this specific site is having this issue - other sites in collection successfully save as template): [InvalidOperationException: Error generating solution files in temporary directory.] Microsoft.SharePoint.SPSolutionExporter.ExportWebAsSolution() +26053165 Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl) +1778 Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent) +44 Microsoft.SharePoint.ApplicationPages.SaveAsTemplatePage.BtnSaveAsTemplate_Click(Object sender, EventArgs e) +331 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +140 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +29 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2981 I'm thinking it may have something to do with permissions, but other sites can save as a template. Also, it does not specify

Permission to use User Solution in Site Collection

Hello, is it possible to deploy a user solution in a site collection, and set permissions which users or groups can use the solution in the site collections or subsites in the site collection ?    

Site template uploaded to Solution Gallery, activated, not showing in Template Selection

I accidentally created a site on a path where I needed to create a site collection. After deleting the site and creating the site collection in its place, I arrived at the Template Selection page. I went to Solution Gallery, uploaded my solution (a package made by the consultants who built our SharePoint site) and activated it. When I activated it I got an error message, but the solution shows in the Gallery as active. I went back to Template Selection to select a template from the solution, but none are showing--just the standard templates. How do I fix this?

Create Custom Site Template & Deploy as Farm Solution


So I've seen a few posts and blogs about this, but nothing with the specific error I'm getting.  All I'm trying to do is create a custom site template from an existing site (now WSP), and make that custom template available in CA so I can create host-named site collections from that template in PowerShell.  Apparenly this was a lot easier in 2007, as you could just save your template as STP, and run some stsadm addsolution to get it in the farm.  With 2010, I've read there are 2 options:

  1. Install-SPWebTemplate
  2. Deploy via Visual Studio 2010

I've tried running Install-SPWebTemplate (which only takes CAB files), and NOTHING I do works.  I've created a cab from the WSP with makecab, I've renamed the WSP to CAB, and all I get is "cannot find or parse web template file".  So on to VS2010.

Using this article as a guide (http://msdn.microsoft.com/en-us/library/ff408263.aspx), I created a new 2010 Import existing solution project, left all items selected, and the import was successful.  I made a change or two to the ONET.xml to fix some things, and then I just try to deploy it to the farm.  Whether I set the URL to the root intranet site, or the CA URL, I get deployment conflict errors:

"The URL or

Can't deploy SharePoint solution even after changing Site Url property



I've developed a SharePoint 2010 solution in VS2010 and i've also deployed it on my site collection - everything works perfect, fine!

But when I try to deploy the same solution in another site collection (on local server not remote) by changing Site Url property of the solution to my new site collection, VS is not deploying the solution. I'm getting the following error:


Error 102 Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site: http://newsiteurl/. Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project.


I've packaged the solution and deployed it manually, it's working fine but i don't understand why i'm not able to deploy the solution on a different site collection on the same machine??

Does anyone else has experienced the same issue? 



Thanks & Regards,


how to make any aspx page in sharepoint site definition solution ghostable in sharepoint site?

how to make any aspx page in sharepoint site definition solution ghostable in sharepoint site?

Managed Metadata and Site Templates/Solution Packages


I have a new SP2010 site that uses managed metadata. There are multiple 1st level sub sites that contain doc libraries, doc centers, etc using site columns with the metadata. I am wanting to package up these sub sites as site templates. Each sub site will be it's own package.

My questions relate to how the new managed metadata fits in. Can I create a package that will deploy the managed metadata on an enterprise level to the other sites? I have dev, stage, and prod environments and what I am trying to do is create packages to deploy across all 3. Is there a way to package the metadata in this fashion so that when I create my stage and prod environments I can deploy the metadata without having to re-create it manually?

Then once the metadata is configured in stage and prod, I plan on using the new visual studio import solution package template to create site templates for each sub site and deploy that package to stage and prod. Anyone have any tips, tricks, possible road blocks, or suggestions with this approach?


how to delete custom site templates(solutions) still shows afert remove the solution in SharePoint 2


I created several version of site templates with different name.  Next I removed the older versions in solution gallery but in the list of template sites still  are showed.

I searched for cmdlet in PowerShell witho no luck.  The custom templates does not shown in SP-WebTemplate command.  So I don´t know how to remove this templates from SharePoint, if the gallery solution is empty.  I remove the solutions from recycle bin in the site and site colleciton scope but with the same results.  And I first deactivate the solution and next remove the solution but nothing works to remove the template from site template.

The odd thing is that in my SharePoint 2010 development Virtual Machine removing the solutions remove the site templates of the creation site option. But in  the Production Server recently migrate to 2010 it does not work.

Any solution in code, cmdlet or some else could help.

Thanks in advance!

Best Practices For Making Responsive Design Look Nice on Your Site

Designing a website featuring a respective layout has become a necessity that is hard to ignore. In fact, after the release of Google's mobile-friendly algorithm the demand for responsive web design has increased to a great extent. But remember that, a responsive design is more than compressing and expanding. A correct respective web design is one that makes a website accessible on countless devices based on the width of the screen of the device.

Changing the graphics on the home page of a SharePoint site

When you create a site in Microsoft Windows SharePoint Services by using the default Team Site template, the home page includes two default graphics. A Windows SharePoint Services graphic appears in the body of the page, and a picture of a house in a circle appears near the site title. You can change these graphics to customize your site. Changing the smaller graphic requires a Windows SharePoint Services compatible Web page editor

Take a tour of your SharePoint site

What is a SharePoint site for?
A SharePoint site is a Web site that provides a central storage and collaboration space for documents, information, and ideas. A SharePoint site is a tool for collaboration, just like a telephone is a tool for communication, or a meeting is a tool for decision making. A SharePoint site helps groups of people (whether work teams or social groups) share information and work together. For example, a SharePoint site can help you:

Coordinate projects, calendars, and schedules.
Discuss ideas and review documents or proposals.
Share information and keep in touch with other people.

Six easy ways to customize your site using Web Parts in SharePoint

Becoming familiar with Web Part customization techniques gives you a range of page-customization choices. For example, you can customize your site's home page so that it displays the specific information that your team needs. You can rearrange the list items on the home page, add lists, and even change the images on the home page. As you become more familiar with Web Part Page customization techniques, you can build interactive Web Part Pages that makes the data in lists more dynamic and useful, and you can add new Web Parts that provide access to external data and Web services.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend