When the SharePoint 2007 application is upgraded to SP 2010, it creates a lot of issues related to master page and themes. First one is related to the customized master page. If you open log file, you will see the errors something like below: Read more…
SharePoint 2010 has come up with a lot of new features and enhancements which are really cool. Yet there are some features 2010 do not even go for, which really surprises me. Here are these:
I have experienced an issue while working on SharePoint 2010. I was trying to use the object model of SharePoint 2010. I got an error message that “Web application cannot be found at the given URL”. I was quite surprised and embarassed as well. I created a windows based application and tried to create an object of SPSite but I got the error described above.
I have faced a weired issue while upgrading SharePoint Server 2007 to SP1 on one of our development servers. Whenever I executed WSS and MOSS upgrade installer, it gives me error “detection failed, this could be due to corrupted installation”. I tried following to overcome the issue but none of them actually worked:
I have been facing an issue after inserting quite much data for testing into one of my lists. It was really hard to get rid of the data and the deletion in sequence was just a nightmare. After some googling I figured out batch deletion would be a perfect solution. Sample code is shown in the following:
As my data was huge in size like 100,000+ records were there. I prepared batches of thousands and deleted one batch at a time. During each batch, I applied a sleep as well. This way deletion was so fast that I was able to delete all records in like less than an hour.
If you have been reading stuff about sharepoint, you must have read/listened these three terms invariably. Yeah template, theme and site definition. All these three are different, lets talk about each one of these:
Themes
Difficulty level for this entity is lower. This is a collection of stylesheets and images to help creating a skin for the site. It’s all about the look and feel of your site. There are several style sheets already available in “TEMPLATE\LAYOUTS\1033\STYLES” folder. But it is not recommended to modify these directly as it will effect other sites as well. Themes are available under “TEMPLATE\Themes” folder.
I had to pass through a scenario that may rare as far as working with MOSS is concerned, sharing it on my blog so it might help someone else. I had built an office automation application using MOSS. We need to pull legacy data within our application as well. In the application there were several sharepoint views.
Problem
After performing import for the legacy data, the total count of items was like more than 150k. I see the following problem opening up page in designer:
While configuring sharepoint server 2007 for form based authentication, I have came across a lot of issues. One site that was really helpful while configuring was:
http://www.codeproject.com/KB/sharepoint/FBA.aspx
After going through all the steps, whenever I try to access the site that was configured for form based authentication. The page just refereshes to itself and do not produce any errors. I read through a lot of blog items to find the result but none of them worked for me.
While trying different options, I came to know that the user provider database which contains all form users should have a windows local account in order to access the users. Once I had configured that, the login page started functioning
Problem
We have discussed automated deployment in another post, now let’s discuss how we can install a feature. Doing an automated feature installation contains some problems if we use SDK. For these problems, please keep on reading.
Solution
The following code snippet should install a feature on the form.
SPWebApplication app = SPWebApplication.Lookup(new Uri(DefaultZone));
SPFeatureDefinitionCollection col = farm.FeatureDefinitions;
SPFeatureDefinition def = col.Add(featurefile, id, true);
app.Features.Add(id, true);
The above code installs the feature but it do not activate the feature even if we try to activate it. The activation step needs to be performed manually.
If we wanted to somehow perform this step, we can do it using the following code (this does not use the SDK):
ProcessStartInfo pStartInfo = new ProcessStartInfo();
//specify gacutil.exe whith which to start the process
pStartInfo.FileName = @”.\stsadm.exe”;
pStartInfo.Arguments = string.Format(“-o installfeature -filename {0} -force”, featureName);
pStartInfo.UseShellExecute = false;
pStartInfo.CreateNoWindow = true;
pStartInfo.WindowStyle = ProcessWindowStyle.Hidden;
//start the process
Process process = Process.Start(pStartInfo);
//wait till the process completes
process.WaitForExit();
The above code will install the feature on the farm where this code is being executed. If we wanted to activate it as well, we can write down the same statements with activatefeature switch.
 |
I'm Waseem Arfi running this Blog. Thanks for visiting my Blog. Feel free to send your comments to Me |
Site Visit Count | |
|
|
|
Recent Discussions