1. Use trusted SQL connections with integrated authentication
To make the production environment more secure, one of the things we looked into was securing the database connection information between the web server and SQL server.
2. Use the Aspnet_setreg.exe utility to encrypt the connection string and store it in the registry.
How to use this utility – Refer http://msdn.microsoft.com/en-us/library/aa302406.aspx
3. Using DPAPI (Data Protection application programming interface) to secure the connection string
How to use this DPAPI – Refer http://msdn.microsoft.com/en-us/library/aa302403.aspx
4. Set retail=”true” in your machine.config in the production server
<configuration>
<system.web>
<deployment retail=”true”/>
</system.web>
</configuration>
It will force the ‘debug’ flag in the web.config to be false, disable page output tracing, and also force the custom error page to be shown to remote users rather than the actual exception or error message. Refer http://mossjenkins.blogspot.com/2009/12/deployment-element-force-debug-flag-in.html
5. Create a new application pool for your site
When setting up your new site for the first time do not share an existing application pool. Create a new application pool which will be used by only by the new web application.
6. Set the memory limit for your application pool
When creating the application pool, specifically set the memory limit rather than the time limit which is set by default. Asp.net has a good whitepaper (http://www.asp.net/learn/whitepapers/aspnet-and-iis6/ ) which explains the value of this: By default IIS 6.0 does not set a limit on the amount of memory that IIS is allowed to use. ASP.NET’s Cache feature relies on a limitation of memory so the Cache can proactively remove unused items from memory. It is recommended that you configure the memory recycling feature of IIS 6.0.
7. Create and appropriately use an app_Offline.htm file
There are many benefits to using this file. It provides an easy way to take your application offline in a somewhat user friendly way (you can at least have a pretty explanation) while fixing critical issues or pushing a major update. It also forces an application restart in case you forget to do this for a deployment.
8. Develop a repeatable deployment process and automate it
It is way too easy to make mistakes when deploying any type of software. This is especially the case with software that uses configuration files that may be different between the development, staging, or production environments. I would argue that the process you come up with is not nearly as important as it being easily repeatable and automated. You can fine tune the process as needed, but you don’t want a simple typo to bring a site down.
9. Build and reference release versions of all assemblies / Version Your Assemblies
In addition to making sure ASP.NET is not configured in debug mode, also make sure that your assemblies are not debug assemblies. There are of course exceptions if you are trying to solve a unique issue in your production environment … but in most cases you should always deploy with release builds for all assemblies
Make sure you have a solid versioning policy in place. You can apply a version stamp using the AssemblyVersion attribute at compile time, for example:
[assembly: AssemblyVersion(”1.0.12.34″)]
It’s usually best to apply the same version number to all the assemblies in an application during the build process.
10. Give Assemblies Strong Names
An assembly is the smallest unit of versioning, security, deployment, version control and reusability of code in .NET. Each assembly contains:
Assembly Identity information (name, version, etc.)
Manifest and metadata information
MSIL code
Type and security information
Resources
An assembly with a strong name can be uniquely identified by a combination of its assembly version, culture information, and a digital signature.
You can create a strong name for your assembly using the strong name utility (sn.exe) provided by the .NET framework.
The utility requires you to provide the name of a strong name key file as a parameter. The resulting file is called a “strong-named” file. You can use the sn.exe tool from the command line to create a strong-named key file as follows: sn –k MyCompany.snk,
Creating a Strong-Named Key File: Running the sn.exe file from the command line as shown creates a strong-named key file.
When you create a project in Visual Studio, you’ll see a default file called AssemblyInfo.cs that you can use to specify the related attributes.
Here is how you can specify the strong name information in the AssemblyInfo.cs file.
[assembly: AssemblyCulture(”")]
[assembly: AssemblyVersion(”1.0.0.0″)] [assembly: AssemblyKeyFile(”MyCompany.snk”)]
11. Obfuscate Your Assemblies
It’s good practice to obfuscate your assemblies before you deploy them; obfuscation makes assemblies more difficult to decompile, and impedes reverse-engineering efforts, thus protecting your source code to some degree from potential threats. In addition, obfuscation reduces the size of your assemblies; thereby boosting the application’s performance.
12. Deploy Shared Assemblies to the GAC
You should deploy assemblies used by multiple applications to the Global Assembly Cache (commonly known as the GAC), which allows them to be shared by all applications that use the assembly. Deploying an assembly to the GAC improves its load performance compared to assemblies not located in the GAC. Strong-named assemblies load faster from the GAC because they’re verified at install time rather than at runtime—the .NET framework skips verification at runtime for GAC-loaded assemblies. The runtime always checks strong-named assemblies to verify their integrity. .NET refuses to load assemblies that are not trusted or that may have been tampered with. Note that you must provide a strong name for assemblies you want to install in the GAC.
You place an assembly into the GAC using the GACUtil tool. The following command places MyProject.dll into the GAC, thus making it globally accessible.
GacUtil /i MyProject.dll
To uninstall the assembly from the GAC, you would use: GacUtil /u MyProject.dll
Note that you can even make your strong-named assembly globally accessible without placing it in the GAC. For this, you need to deploy your assembly using the XCOPY command.
13. Pre-Compile Your Sites
You can use the ASP.NET 2.0 Pre compilation feature to minimize the initial load time of your web pages, and avoid having to deploy your source code to the server. Pre compilation is a great new feature that can detect and provide warnings about any compilation failure issues. It lets you deploy applications without having to store any source code on the deployment server. Pre compilation can both reduce application response time and improve performance. Learn more about pre compile http://www.devx.com/dotnet/Article/34418/0
14. Reduce File Sizes
It’s generally a good practice to squeeze extra white space and other unwanted characters from your web pages, script, and style sheets to minimize response size. You can also compress the rendered response to reduce network bandwidth and improve performance using IIS compression. Although there is a slight performance penalty for using IIS compression (compression requires extra processing), it’s still a good practice, because the performance penalty is negligible compared to the huge benefit you get from it; compression can reduce network bandwidth by nearly 50 percent! This article provides more information on file size reduction and IIS HTTP compression.
REF MSDN
Friday, December 18, 2009
Deployment Element - force the ‘debug’ flag in the web.config to be false
To disables ASP.NET certain configuration settings such as trace output, custom errors, and debug capabilities.
Set retail=”true” in your machine.config in the production server
<configuration>
<system.web>
<deployment retail=”true”/>
</system.web>
</configuration>
It will force the ‘debug’ flag in the web.config to be false, disable page output tracing, and
also force the custom error page to be shown to remote users rather than the actual exception or error message
Configurable Locations Machine.config Requirements IIS 6.0 .NET Framework 2.0 Visual Studio 2005
Note: Important
This value can only be set at the machine level, not at the application level, so do it only Production server.
REF MSDN
Set retail=”true” in your machine.config in the production server
<configuration>
<system.web>
<deployment retail=”true”/>
</system.web>
</configuration>
It will force the ‘debug’ flag in the web.config to be false, disable page output tracing, and
also force the custom error page to be shown to remote users rather than the actual exception or error message
Configurable Locations Machine.config Requirements IIS 6.0 .NET Framework 2.0 Visual Studio 2005
Note: Important
This value can only be set at the machine level, not at the application level, so do it only Production server.
REF MSDN
Monday, December 14, 2009
Attach JavaScript Events to Grid View Bound Field
I have an <asp:gridview>, can I attach a JavaScript function to the OnKeyPress event of the text boxes (visible while you in Edit mode)?
To achieve that, most of the forums and blog suggested a Template Field instead of a Bound Field where you need to do something custom like that.. (It’s a good solution, for me I implemented grid view with all columns as Bound Field, to modify it’s took more time)
Then I tried with many ways and after that I got solution for attach JavaScript with Bound Field.
Solution
Add “OnRowEditing” event in Grid view
When RowEditing Event
Example using c#
protected void grdView_RowEditing(object sender, GridViewEditEventArgs e)
{
GridView oGridView = (GridView)sender;
oGridView.EditIndex = e.NewEditIndex;
TextBox textbox = new TextBox();
textbox = (TextBox)oGridView.Rows[e.NewEditIndex].Cells[4].Controls[0];
textbox.Attributes.Add("onKeyPress", "return numericCheck(event);");
BindData();
}
1. Create an TextBox Object : TextBox textbox = new TextBox();
2. For this example I am going to attach the javascript with 4th column of the current row.oGridView.Rows[e.NewEditIndex].Cells[4].Controls[0]
3. Then type cast the Control as TextBox (TextBox)oGridView.Rows[e.NewEditIndex].Cells[4].Controls[0];
4. Then attach the onKeyPress event - textbox.Attributes.Add("onKeyPress", "return numericCheck(event);");
JavaScript
function numericCheck()
{
if(!(event.keyCode==45event.keyCode==46event.keyCode==48event.keyCode==49event.keyCode==50event.keyCode==51event.keyCode==52event.keyCode==53event.keyCode==54event.keyCode==55event.keyCode==56event.keyCode==57 event.keyCode == 8 event.keyCode == 190 event.keyCode == 37 event.keyCode == 39 event.keyCode == 16))
{
alert("Please Enter Nemeric Values");
event.returnValue=false;
}
}
To achieve that, most of the forums and blog suggested a Template Field instead of a Bound Field where you need to do something custom like that.. (It’s a good solution, for me I implemented grid view with all columns as Bound Field, to modify it’s took more time)
Then I tried with many ways and after that I got solution for attach JavaScript with Bound Field.
Solution
Add “OnRowEditing” event in Grid view
When RowEditing Event
Example using c#
protected void grdView_RowEditing(object sender, GridViewEditEventArgs e)
{
GridView oGridView = (GridView)sender;
oGridView.EditIndex = e.NewEditIndex;
TextBox textbox = new TextBox();
textbox = (TextBox)oGridView.Rows[e.NewEditIndex].Cells[4].Controls[0];
textbox.Attributes.Add("onKeyPress", "return numericCheck(event);");
BindData();
}
1. Create an TextBox Object : TextBox textbox = new TextBox();
2. For this example I am going to attach the javascript with 4th column of the current row.oGridView.Rows[e.NewEditIndex].Cells[4].Controls[0]
3. Then type cast the Control as TextBox (TextBox)oGridView.Rows[e.NewEditIndex].Cells[4].Controls[0];
4. Then attach the onKeyPress event - textbox.Attributes.Add("onKeyPress", "return numericCheck(event);");
JavaScript
function numericCheck()
{
if(!(event.keyCode==45event.keyCode==46event.keyCode==48event.keyCode==49event.keyCode==50event.keyCode==51event.keyCode==52event.keyCode==53event.keyCode==54event.keyCode==55event.keyCode==56event.keyCode==57 event.keyCode == 8 event.keyCode == 190 event.keyCode == 37 event.keyCode == 39 event.keyCode == 16))
{
alert("Please Enter Nemeric Values");
event.returnValue=false;
}
}
Feature Installation Error - STSADM: The farm is unavailable
We have created a new feature and try to install in the sharepoint server using stsadm command, it throws an error called STSADM: The farm is unavailable Error.
The solution for this error is that the installing user does not having rights in SQL server.ie.the Principal running the command does not have access to the SQL Server for the current farm.
The solution for this error is that the installing user does not having rights in SQL server.ie.the Principal running the command does not have access to the SQL Server for the current farm.
Thursday, December 10, 2009
WIF - Windows Identity Foundation
Identity Challenges
Most developers are not security experts and many feel uncomfortable being given the job of authenticating, authorizing, and personalizing experiences for users. It’s not a subject that has been traditionally taught in computer science curriculum, and these features tend to be ignored until late in the software development lifecycle.
It’s not surprising nowadays to see a single company with tens or hundreds of Web applications and services, many of which have their own private silo for user identities, and most of which are hardwired to use one particular means of authentication. Developers know how tedious it is to build identity support into each application, and IT professionals know how expensive it is to manage the resulting set of applications.
One very useful step toward solving the problem has been to centralize user accounts into an enterprise directory. Commonly it’s the IT professional that knows the most effective and efficient way to query the directory, but today the task is typically left up to the developer. And in the face of mergers, acquisitions, and partnerships, the developer might be faced with accessing more than one directory, using more than one API.
In the Microsoft .NET Framework, there are lots of different ways of building identity support into an application, and each communication framework treats identity differently, with different object models, different storage models, and so on. Even in ASP.NET, developers can get confused about where they should look for identity: should they look at the HttpContext.User property? What about Thread.CurrentPrincipal?
The rampant use of passwords has lead to a cottage industry for phishers1. And with so many applications doing their own thing, it’s difficult for a company to upgrade to stronger authentication techniques.
A Better Solution
One step toward solving these problems is to stop building custom identity plumbing and user account databases into every new application that comes along. But even developers who rely on a central enterprise directory still feel the pain of mergers, acquisitions, and external partnerships, and may even be blamed for poor performance that is actually due to another application bogging down the directory with inefficient queries. The claims-based solution described in this paper does not require developers to connect to any particular enterprise directory in order to look up identity details for users. Instead, the user’s request arrives with all of the identity details the application needs to do its job. By the time the user arrives with these claims, the user has already been authenticated, and the application can go about its business without worrying about managing or finding user accounts.
Factoring authentication out of applications leads to many benefits for developers, IT professionals, and users. Simply put, there are less user accounts for everyone to manage, and the resulting centralization of authentication makes it easier to upgrade to stronger authentication methods as they evolve, and even federate identity with other platforms and organizations.
This paper will help you, as a developer, to understand the claims-based identity model and take advantage of it using Windows Identity Foundation (WIF), the new framework from Microsoft that is focused on identity.
What is Windows Identity Foundation?
Windows Identity Foundation (WIF) is a set of .NET Framework classes. It is a framework for implementing claims-based identity in your applications. By using it, you’ll more easily reap the benefits of the claims-based identity model described in this paper. Windows Identity Foundation can be used in any Web application or Web service that uses the .NET Framework version 3.5 SP1.
WIF is just one part of Microsoft’s Identity and Access Platform software family that implements the shared industry vision for an interoperable Identity Metasystem. Active Directory Federation Services (ADFS) 2.0 (previously known as “Geneva” Server), Windows CardSpace 2.0, and Windows Identity Foundation (previously known as “Geneva” Framework) form the core of Microsoft’s new claims based access strategy. You can refer to the Identity and Access Management web site for more information about AD FS and CardSpace components. Also, the white paper “Claims-based Identity for Windows“ provides an overview of these three components. As of this writing, the RTW of Windows Identity Foundation and Beta 2 releases of the other two products are available for download.
Tuesday, December 1, 2009
Monday, November 30, 2009
WSP Installation and Feature Activation & DeActivation Steps in MOSS 2007
1. Add the solutionstsadm -o addsolution -filename
2. Deploy the solutionstsadm -o deploysolution -name -url
3. Install the featurestsadm -o installfeature -filename\feature.xml
4. Activate the featurestsadm -o activatefeature -id -url -force
5. Deactive the featureStsadm.exe -o deactivatefeature -filename “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ViewFormPagesLockDown\feature.xml” -ur http://servername/6.Uninstall the featurestsadm -o uninstallfeature -filename
7.Retract Solutionstsadm -o retractsolution -name [-url] [-allcontenturls] [-time] [-immediate]
8.Delete Solutionstsadm -o deletesolution -name
Reference
2. Deploy the solutionstsadm -o deploysolution -name
3. Install the featurestsadm -o installfeature -filename
4. Activate the featurestsadm -o activatefeature -id
5. Deactive the featureStsadm.exe -o deactivatefeature -filename “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ViewFormPagesLockDown\feature.xml” -ur http://servername/6.Uninstall the featurestsadm -o uninstallfeature -filename
7.Retract Solutionstsadm -o retractsolution -name [-url] [-allcontenturls] [-time] [-immediate]
8.Delete Solutionstsadm -o deletesolution -name
Reference
SharePoint 2010 Public Beta now available for Download
Sharepoint 2010 Beta - [REF MSDN]
Microsoft SharePoint Server 2010 Beta is the business collaboration platform for the Enterprise and the Web that enables you to connect and empower people through an integrated set of rich features. Whether deployed on-premise or as a hosted service, SharePoint Server 2010 helps you cut costs with a unified infrastructure while allowing you to rapidly respond to your business needs.
The SharePoint Server 2010 Beta software is available in the following languages:
Chinese (Simplified), English, French, German, Japanese, Russian and Spanish
There are two versions of SharePoint Server 2010 Beta:
SharePoint Server 2010 (Enterprise Client Access License features)For organizations looking to expand their business collaboration platform to enable advanced scenarios. Use the Enterprise capabilities of SharePoint to fully interoperate with external line-of-business applications, web services, and Microsoft Office client applications; make better decisions with rich data visualization, dashboards, and advanced analytics; and build robust forms and workflow-based solutions.
SharePoint Server 2010 for Internet Sites, EnterpriseFor organizations looking to create customer-facing public internet sites and private extranets using the full enterprise capabilities of SharePoint. This provides full SharePoint Enterprise functionality and no other technical limits.
Download Here
Steps to Download Evaluation
Review system requirements
Register for evaluation
Download software
Check email for resources
System requirements for SharePoint Server 2010
System Requirements
Microsoft SharePoint Server 2010 (Beta) provides for a number of installation scenarios. Currently, these installations include stand-alone and single server installations and multiple server farm installation.
Microsoft SharePoint Server 2010 Beta is the business collaboration platform for the Enterprise and the Web that enables you to connect and empower people through an integrated set of rich features. Whether deployed on-premise or as a hosted service, SharePoint Server 2010 helps you cut costs with a unified infrastructure while allowing you to rapidly respond to your business needs.
The SharePoint Server 2010 Beta software is available in the following languages:
Chinese (Simplified), English, French, German, Japanese, Russian and Spanish
There are two versions of SharePoint Server 2010 Beta:
SharePoint Server 2010 (Enterprise Client Access License features)For organizations looking to expand their business collaboration platform to enable advanced scenarios. Use the Enterprise capabilities of SharePoint to fully interoperate with external line-of-business applications, web services, and Microsoft Office client applications; make better decisions with rich data visualization, dashboards, and advanced analytics; and build robust forms and workflow-based solutions.
SharePoint Server 2010 for Internet Sites, EnterpriseFor organizations looking to create customer-facing public internet sites and private extranets using the full enterprise capabilities of SharePoint. This provides full SharePoint Enterprise functionality and no other technical limits.
Download Here
Steps to Download Evaluation
Review system requirements
Register for evaluation
Download software
Check email for resources
System requirements for SharePoint Server 2010
System Requirements
Microsoft SharePoint Server 2010 (Beta) provides for a number of installation scenarios. Currently, these installations include stand-alone and single server installations and multiple server farm installation.
What’s New in SharePoint 2010 Compare with MOSS 2007
What’s New in SharePoint 2010 Compare with MOSS 2007
- Access Services
- Business Connectivity Services
- Central Administration (Redesigned)
- Digital Asset Management
- Enterprise Search
- Excel Services
- Health Monitoring
- Managed Metadata
- PerformancePoint Services
- Records Management
- Sandboxed Solutions
- Social Computing
- Visio Services
- Upgrade
- Windows PowerShell (STSADM moved to PowerShell)
- Removed SSP and Added WCF Services using Rest Protocol for Services
- Web Services removed and Added WCF Services using Rest Protocol
Access Services
Use Access Services in Microsoft SharePoint Server 2010 to edit, update, and create linked Microsoft Access 2010 databases that can be viewed and manipulated by using an Internet browser, the Access client, or a linked HTML page.
Business Connectivity Services
SharePoint Server 2010 and the Microsoft Office 2010 suites include Microsoft Business Connectivity Services, which is a set of services and features that provide a way to connect SharePoint-based solutions to sources of external data and to define external content types based on that external data.
Central Administration (Redesigned)
Central Administration has been redesigned in SharePoint Server 2010 to provide a more familiar experience and make it easier for users to find what they are looking for.
Digital Asset Management
SharePoint Server 2010 includes a new asset library specially designed for managing and sharing digital assets such as audio, video, and other rich media files.
Enterprise Search
With the new capabilities in SharePoint Server 2010, search administrators can configure an optimal search infrastructure that helps end users find information in the enterprise quickly and efficiently.
Excel Services
Excel Services in Microsoft SharePoint Server 2010 can be used to publish Excel client workbooks on SharePoint Server 2010.
What’s new for Excel Services (SharePoint Server 2010)
Managed Metadata
Managed metadata is a hierarchical collection of centrally managed terms that you can define, and then use as attributes for items in SharePoint Server 2010. The Managed Metadata Service supports the use of managed metadata, as well as the sharing of content types across the enterprise.
PerformancePoint Services
PerformancePoint Services in Microsoft SharePoint Server 2010 provides flexible, easy-to-use tools for building dashboards, scorecards, and key performance indicators (KPIs).
Records Management
In SharePoint Server 2010, you can manage records in an archive, or you can manage records in the same document repository as active documents.
Sandboxed Solutions
You can deploy sandboxed solutions to quickly and more securely solve business problems. Sandboxed solutions are like farm solutions except in the following ways: they are rights-restricted and have a more permissive deployment policy than farm solutions; they are limited to the site collection to which they are deployed; and their server resource usage is monitored against an administrator-controlled quota for the site collection.
Social Computing
SharePoint Server 2010 includes social networking tools such as My Site Web sites and social content technologies such as blogs, wikis, and really simple syndication (RSS). These features are built upon a database of properties that integrates information about people from many kinds of business applications and directory services. You can adapt content to each user while enabling administrators to set policies to protect privacy.
Visio Services
The Visio Graphics Service is a service on the SharePoint Server 2010 platform that enables users to share and view Visio diagrams and enables data-connected Microsoft Visio 2010 diagrams to be refreshed and updated from a variety of data sources.
Upgrade
Review upgrade requirements and find out about new upgrade tools and options, including information about the pre-upgrade checker, Visual Upgrade, and the test-spcontentdatabase Windows PowerShell cmdlet.
What’s new in upgrade (SharePoint Server 2010)
Windows PowerShell
Windows PowerShell is the new command-line interface and scripting language specifically designed for system administrators.
Windows PowerShell for SharePoint Foundation 2010
Windows PowerShell a command-line scripting tool that provides an administrator full access to the Microsoft Office SharePoint Server Application Programming Interface (API), along with the ability to unlock the capability to interact directly with SharePoint 2010 Products to manipulate Web applications, site collections, sites, lists and much more. In addition, the administrator has the ability to script cmdlets (pronounced, “command-lets”), which makes for an improved experience in administering SharePoint 2010 Products.
Also the old Stsadm command-line tool is included to support compatibility across product versions
By default, Windows PowerShell is located at the following path: <%SystemRoot%>\System32\WindowsPowerShell\v1.0\PowerShell.exe.
We recommend that you use Windows PowerShell to perform bulk administrative tasks. The use of SharePoint 2010 Products cmdlets is available in the SharePoint 2010 Management Shell. By using a management shell, this eliminates the step to register the snap-in that contains the cmdlets using the Add-PSSnapin cmdlet.
To access the SharePoint 2010 Management Shell
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
Once the SharePoint 2010 Management Shell is running, there are several cmdlets you can run to get you started. In order to use the cmdlets, verify that you meet the following minimum requirements: You are a member of the SharePoint_Shell_Access role on the configuration database and a member of the WSS_ADMIN_WPG local group on the computer where SharePoint 2010 Products is installed.
For Beta, use the Add-SPShellAdmin cmdlet to add a user to the SharePoint_Shell_Access role on the configuration database. You must run the Add-SPShellAdmin cmdlet for all databases to which you want to grant access. If no database is specified, the farm configuration database is used. If you do specify a database, the farm content database will be included in addition to the farm configuration database you specify.
REST Protocol
The REST protocol is a simple HTTP-based protocol that enables you to contact the message broker through a Web browser. You can contact the message broker by navigating to appropriately formatted URLs or by posting HTML forms.
The FUSE Message Broker’s REST protocol is based on a subset of the HTTP protocol. Hence, HTTP is the only supported transport.
REST supports the following client types:
Web forms—use conventional HTML forms to POST a message to a destination (queue or topic) or to GET a message from a destination—see Example of posting a message .
Ajax clients—an Asynchronous JavaScript And Xml (Ajax) library that enables you to communicate with a REST endpoint using JavaScript in a DHTML Web page. For details of how to program an Ajax client, see the Cross Language Client Development Guide.
Monday, November 23, 2009
WSP Installation and Feature Activation & DeActivation Steps in MOSS 2007
1. Add the solution
stsadm -o addsolution -filename
2. Deploy the solution
stsadm -o deploysolution -name -url
3. Install the feature
stsadm -o installfeature -filename\feature.xml
4. Activate the feature
stsadm -o activatefeature -id -url -force
5. Deactive the feature
Stsadm.exe -o deactivatefeature -filename “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ViewFormPagesLockDown\feature.xml” -url http://servername/
6.Uninstall the feature
stsadm -o uninstallfeature -filename
7.Retract Solution
stsadm -o retractsolution -name [-url] [-allcontenturls] [-time] [-immediate]
8.Delete Solution
stsadm -o deletesolution -name
Reference
stsadm -o addsolution -filename
2. Deploy the solution
stsadm -o deploysolution -name
3. Install the feature
stsadm -o installfeature -filename
4. Activate the feature
stsadm -o activatefeature -id
5. Deactive the feature
Stsadm.exe -o deactivatefeature -filename “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ViewFormPagesLockDown\feature.xml” -url http://servername/
6.Uninstall the feature
stsadm -o uninstallfeature -filename
7.Retract Solution
stsadm -o retractsolution -name [-url] [-allcontenturls] [-time] [-immediate]
8.Delete Solution
stsadm -o deletesolution -name
Reference
Thursday, August 20, 2009
webpart to a XSLT dataview using SharepointDesigner - Error When move dev to Prod environment
I moved MOSS dev site to prod environment, its shows error where ever having XSLT dataview.
Error Messages
In your Web browser:
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
In SharePoint Designer:
The server returned a non-specific error when trying to get data from the data source. Check the format and content of your query and try again. If the problem persists, contact the server administrator.
I searched in google and msdn, i didn’t get any solution.
After that i find the fix.
I opened both dev and prod in Sharepoint Designer, Check the GUIDs for DataSource its same in both dev and prod, but the list guid not same.
Fix:
I find the dev list guid in sharepoint designer page and replace the prod guid. Saved and open the page in Browser its working fine.
Note:
When you convert a webpart to a XSLT dataview with Sharepoint Designer it creates a datasource which points to the list used. The reference to the datasource is given using the ‘GUID’ of the list. So, when we do a backup/restore (SPD) or export/import (stsadm), or Site template the new list created will have a GUID different from that of the original list. However, the restore does not update the original links with the new GUID. So, the View is unable to fetch data from the datasource and can’t show the list.
Error Messages
In your Web browser:
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
In SharePoint Designer:
The server returned a non-specific error when trying to get data from the data source. Check the format and content of your query and try again. If the problem persists, contact the server administrator.
I searched in google and msdn, i didn’t get any solution.
After that i find the fix.
I opened both dev and prod in Sharepoint Designer, Check the GUIDs for DataSource its same in both dev and prod, but the list guid not same.
Fix:
I find the dev list guid in sharepoint designer page and replace the prod guid. Saved and open the page in Browser its working fine.
Note:
When you convert a webpart to a XSLT dataview with Sharepoint Designer it creates a datasource which points to the list used. The reference to the datasource is given using the ‘GUID’ of the list. So, when we do a backup/restore (SPD) or export/import (stsadm), or Site template the new list created will have a GUID different from that of the original list. However, the restore does not update the original links with the new GUID. So, the View is unable to fetch data from the datasource and can’t show the list.
Tuesday, August 18, 2009
We are in MOSS 2007(SharePoint 12) Microsoft Planning to release SharePoint 2010 (formerly codenamed SharePoint 14) and WSS 4.0
MOSS 2007 - 32 bit , SharePoint 14 - 64 bit
System Requirements
SharePoint Server 2010 will be 64-bit only.
SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
Internet Explorer 6 and later and Firefox, and Safri
Designer – SharePoint Designer 14 /2020
New Features in SharePoint 14
1. A new user interface
An intuitive and contextual web user interface that makes users more effective, provides better performance
2. Web Edit and Rich Theming
Web Edit allows users to easily customize a site. Rich Theming allows user to skin their SharePoint site using their favorite office client themes.
3. Silverlight Web Part
The Silverlight Web Part lets you quickly and securely integrate Silverlight applications and rich media into your site taking the user experience to another level.
4. Visio Services
Visio Services lets you share data linked diagrams in real time with interactive experience. It is not required to have Visio.
5. Business Connectivity Services
Business Connectivity Services (BCS) allows connecting to Line-of-Business applications, web services and databases enabling users to interact and update it easily in the web and in the office client.
6. SharePoint Workspace
SharePoint Workspace lets you take your SharePoint lists and libraries offline including the ability to update content and sync it back in when you are re-connected.
7. Streamlined Central Administration
Everything is at your fingertips within Central Administration. It makes configuring and managing your server farm quicker and easier.
8. Best Practices Analyzer
Best Practices Analyzer provides extensible rules based engine that monitors farm health, and can automatically fix many common configuration and performance issues right out-of-the box.
9. Usage Reporting and Logging
The database schema gives the power and flexibility of writing our own reports in addition to the ones provided already. Insight into server usage and performance becomes easier.
10. Visual Studio 2010 tools
Includes new tools for creating, packaging and debugging SharePoint solutions.
11. LINQ for SharePoint
Offers SharePoint developers to access and join the SharePoint list data easily.
12. Developer Dashboard
Developer Dashboard can be enabled on any SharePoint page for development and debugging purposes. It helps developers write better code by providing diagnostic information.
13. Client Object Model
Client Object Model is a new programming interface where code runs on a user's client machine against a local object model and interacts with data on the SharePoint server.
14. Large List Resource Throttling
Gives granular control over the server performance impact of large list and libraries that contain several thousand to millions of items.
15. Deploy and debug from Visual Studio
You should be able to build, deploy and debug SharePoint applications directly from Visual Studio! If this is true, it will save us a lot of time!
System Requirements
SharePoint Server 2010 will be 64-bit only.
SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
Internet Explorer 6 and later and Firefox, and Safri
Designer – SharePoint Designer 14 /2020
New Features in SharePoint 14
1. A new user interface
An intuitive and contextual web user interface that makes users more effective, provides better performance
2. Web Edit and Rich Theming
Web Edit allows users to easily customize a site. Rich Theming allows user to skin their SharePoint site using their favorite office client themes.
3. Silverlight Web Part
The Silverlight Web Part lets you quickly and securely integrate Silverlight applications and rich media into your site taking the user experience to another level.
4. Visio Services
Visio Services lets you share data linked diagrams in real time with interactive experience. It is not required to have Visio.
5. Business Connectivity Services
Business Connectivity Services (BCS) allows connecting to Line-of-Business applications, web services and databases enabling users to interact and update it easily in the web and in the office client.
6. SharePoint Workspace
SharePoint Workspace lets you take your SharePoint lists and libraries offline including the ability to update content and sync it back in when you are re-connected.
7. Streamlined Central Administration
Everything is at your fingertips within Central Administration. It makes configuring and managing your server farm quicker and easier.
8. Best Practices Analyzer
Best Practices Analyzer provides extensible rules based engine that monitors farm health, and can automatically fix many common configuration and performance issues right out-of-the box.
9. Usage Reporting and Logging
The database schema gives the power and flexibility of writing our own reports in addition to the ones provided already. Insight into server usage and performance becomes easier.
10. Visual Studio 2010 tools
Includes new tools for creating, packaging and debugging SharePoint solutions.
11. LINQ for SharePoint
Offers SharePoint developers to access and join the SharePoint list data easily.
12. Developer Dashboard
Developer Dashboard can be enabled on any SharePoint page for development and debugging purposes. It helps developers write better code by providing diagnostic information.
13. Client Object Model
Client Object Model is a new programming interface where code runs on a user's client machine against a local object model and interacts with data on the SharePoint server.
14. Large List Resource Throttling
Gives granular control over the server performance impact of large list and libraries that contain several thousand to millions of items.
15. Deploy and debug from Visual Studio
You should be able to build, deploy and debug SharePoint applications directly from Visual Studio! If this is true, it will save us a lot of time!
Monday, July 27, 2009
Delete Sharepoint ListItems using c# - Issue with microsoft sample code
Below is the Code to Delete List Item used by Microsoft Sample
spListCollection = spWeb.Lists["ActualAmounttrack"].Items; int itemCount = spListCollection.Count;
for (int k = 0; k < itemCount; k++)
{
SPListItem item = spListCollection[k];
if (IdeaId == item["Title"].ToString())
{
spListCollection.Delete(k);
}
}
Its not Working.
Why the above code is not working - If you need to loop through the ListItemCollection to delete multiple ListItems, your code will not work. When you attempt to delete the last ListItem, you will receive a boundary exceeded exception.
The index to the ListItemCollection should always = 0.
Solution:
Working code
spListCollection = spWeb.Lists["ActualAmounttrack"].Items;
int itemCount = spListCollection.Count;
for (int k = itemCount; k > 0; k - -)
{
int id = k - 1; SPListItem item = spListCollection[id];
if (IdeaId == item["Title"].ToString())
{ spListCollection.Delete(id); }
}
spListCollection = spWeb.Lists["ActualAmounttrack"].Items; int itemCount = spListCollection.Count;
for (int k = 0; k < itemCount; k++)
{
SPListItem item = spListCollection[k];
if (IdeaId == item["Title"].ToString())
{
spListCollection.Delete(k);
}
}
Its not Working.
Why the above code is not working - If you need to loop through the ListItemCollection to delete multiple ListItems, your code will not work. When you attempt to delete the last ListItem, you will receive a boundary exceeded exception.
The index to the ListItemCollection should always = 0.
Solution:
Working code
spListCollection = spWeb.Lists["ActualAmounttrack"].Items;
int itemCount = spListCollection.Count;
for (int k = itemCount; k > 0; k - -)
{
int id = k - 1; SPListItem item = spListCollection[id];
if (IdeaId == item["Title"].ToString())
{ spListCollection.Delete(id); }
}
Sunday, February 8, 2009
MOSS 2007 Web Services - Easier Way to Populate the Sharepoint Information
Using this below Web Services,
Easier way to populate all information to your Webparts or Windows Applications.
- Administration Service - http:///_vti_adm/admin.asmx
- Alerts Service - http:///_vti_bin/alerts.asmx
- Document Workspace Service - http:///_vti_bin/dws.asmx
- Forms Service - http:///_vti_bin/forms.asmx
- Imaging Service - http:///_vti_bin/imaging.asmx
- List Data Retrieval Service - http://_/_vti_bin/dspsts.asmx
- Lists Service - http:///_vti_bin/lists.asmx
- Meetings Service - http://_vti_bin/meetings.asmx
- Permissions Service - http://_/_vti_bin/permissions.asmx
- Site Data Service - http:///_vti_bin/sitedata.asmx
- Site Service - http:///_vti_bin/sites.asmx
- Users and Groups Service - http://_/_vti_bin/usergroup.asmx
- Versions Service - http:///_vti_bin/versions.asmx
- Views Service - http:///_vti_bin/views.asmx
- Web Part Pages Service - http:///_vti_bin/webpartpages.asmx
- Webs Service - http:///_vti_bin/webs.asmx
This is my first blog here
Subscribe to:
Posts (Atom)